Replies: 1 comment
|
Consolidating into #6836. Its minimum scope and follow-up already cover a global title-instructions setting for initial titles and Regenerate title, with reset to defaults. Closing this duplicate, not marking the feature implemented. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Problem
T3 Code generates thread titles using built-in prompts, but users cannot discover or customize that behavior in Settings. Different users need different title styles—for example shorter titles, ticket IDs, a preferred language, or organization-specific terminology.
The current source defines
threadTitleInstructionsinTextGenerationPolicy, and the prompt builder supports appending it. However, there is no settings UI for it, and the initial-title and regeneration call sites do not pass a policy, so the capability is not currently usable.Proposed solution
Add a discoverable Thread title generation setting that lets users provide custom instructions for automatic titles.
The smallest useful scope would be:
Per-project overrides could be added later.
Discoverability
This should be visible alongside the existing text-generation/source-control writing settings rather than requiring users to know about an internal policy field or configuration file.
Relationship to #6836
Discussion #6836 proposes learning title style from manual renames and retaining rename history. This request is intentionally narrower: it does not require learning, history storage, or examples inferred from prior threads. It asks for an explicit, discoverable configuration surface for instructions that users write themselves.
#6836
Why this matters
Thread titles are navigation metadata that users scan repeatedly. A visible configuration makes title behavior predictable and gives users direct control without modifying T3 Code source.
All reactions