Skip to content

request: ability to disable title generation (opencode run) #1237

Closed

Description

@rekram1-node

2 use cases here:

  1. When using opencode run I hardly ever want a title (I would say basically never), in these cases I'd prefer a truncated version of the prompt I sent to be used as title instead (of course it could just be New Session .... too << Not suggesting to disable title gen for this just saying I would at least like a flag to disable it
  2. Some people may want to save $ on tokens, so they may just want to disable title generation across the board

Activity

  1. changed the title [-]request: ability to disable title generation[/-] [+]request: ability to disable title generation (`opencode run`)[/+] on Jul 23, 2025
  2. Explosion-Scratch commented on Jul 23, 2025

    @Explosion-Scratch

    I second this - Not sure why this isn't already a thing.

  3. Explosion-Scratch commented on Jul 23, 2025

    @Explosion-Scratch

    Might be related to #992

  4. self-assigned this
    on Jul 23, 2025
  5. thdxr commented on Jul 23, 2025

    @thdxr
    Member

    these sessions still end up in your session list when running opencode normally. but we can probably add a flag. these use small models so the $ cost is very small

  6. rekram1-node commented on Jul 30, 2025

    @rekram1-node
    ContributorAuthor

    made pr: #1299

  7. timoclsn commented on Aug 8, 2025

    @timoclsn
    Contributor

    Or not just a flag to disable the title generation, but also the ability to add a custom title via the flag.

    This way, one could use the custom title in plugins. My use case would be to skip desktop notifications for non-interactive runs (filter them out with a custom title).

  8. rekram1-node commented on Aug 8, 2025

    @rekram1-node
    ContributorAuthor

    interesting use case, maybe the flag is --title and it defaults to your prompt if no argument provided

    I think the team will probably have an opinion on that but I get what you are saying

  9. rohitpaulk commented on Oct 27, 2025

    @rohitpaulk

    --title seems like a good option here. Our use-case: we're running super short tasks that have long prompts (fix a syntax in this 20 line file, but with tons of rules), and we're using small models for the task too. The time it takes a small model to generate a title is comparable to the actual work that needs to be done, and we really don't need the title since this is a programmatic use-case.

  10. rekram1-node commented on Oct 28, 2025

    @rekram1-node
    ContributorAuthor

    ill add it

  11. rekram1-node commented on Oct 28, 2025

    @rekram1-node
    ContributorAuthor

    will be in next release

  12. rohitpaulk commented on Oct 28, 2025

    @rohitpaulk

    @rekram1-node thanks for the quick fix!

  13. rekram1-node commented on Oct 29, 2025

    @rekram1-node
    ContributorAuthor

    no problem!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions