[Feature]: Custom Thread Title Generation

[clayliddell]

Before submitting

• I searched existing issues and did not find a duplicate.
• I am describing a concrete problem or use case, not just a vague idea.

Area

apps/desktop

Problem or use case

The T3 Code titles generated by default are rather verbose. Like reading through statements or sentences.

This may be to the liking of some, but I would love to be able to provide a prompt with a few concrete examples of how I want T3Code thread title gen to work so that it actually title's threads in the same way that I personally would.

Proposed solution

Allow T3Code to learn from thread title renames by keeping a log of all:
- original names
- new user provided names
- original prompt the was used to generate the original names.

Why this matters

Better UX: This would make thread titles align more with how a user thinks about their work.

Smallest useful scope

Allow users to modify the prompt used for thread title gen the same way you allow custom prompting for source control writing style.

Alternatives considered

No response

Risks or tradeoffs

No response

Examples or references

No response

Contribution

• I would be open to helping implement this.

[michidk]

Additional use case: please expose the prompt used for automatic thread-title generation as a user-editable setting.

Ideally, the configured prompt should apply consistently to both initial title generation and Regenerate title, with a Reset to default action. This would let users enforce their preferred style—such as shorter titles, ticket IDs, or a specific language—without modifying T3 Code itself.

A single global prompt override would be a useful smallest scope; per-project overrides could be added later.

[Radu028]

Opened a PR for the minimum scope described here and in #7298: #11717

• One threadTitleInstructions setting under General > Text generation, empty by default, with reset.
• Applied to both the first title and Regenerate title, appended after the built-in prompt and JSON requirements.
• Because the key sits in the existing project-scoped settings list, the same row also works as a per-project override with no extra machinery. Tested end to end with Codex: a request naming compass-4437 produced [COMPASS 4437] SSO Redirect Loop.

+173 / -15 across contracts, server, web and docs, with focused tests. Happy to drop the per-project part if you want it strictly global first.

[AspireOne]

I literally need this feature. I need to be able to provide a small instruction to the title-generating model so that it formats my titles properly and consistently.

For example, I work on tasks in tandem with a Project Manager (Plane.so, Linear, whatever). It's my primary workflow. I always supply the task ID (e.g. VK-43) in the first message. I want the thread tittle to be prefixed with that ID, so that I can keep track of what feature is being worked on in each tab when I have 6 simultaneous tabs (e.g. "VK-43: Merge Upstream Changes").

[Hezaerd]

Would be perfect as a project setting and not just an environment setting to be able to customize per project