You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit b4c5599
Browse filesBrowse the repository at this point in the historyBrowse files
fix(server): generated thread titles leave out the project name
The title prompts ask the model to avoid project names already visible in
the UI, but never say what the project is called, so titles often repeat
it ("FireForge Source Mode vs Patches" under the FireForge project).
Pass the project title into thread title generation and name it in the
rule for initial and regenerated titles.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Add an entry to `cases.ts` with an `id`, a `source`, the thread `messages`, the `previousTitle`, and a `rubric` that says what a good title names.
19
+
Add an entry to `cases.ts` with an `id`, a `source`, the thread `messages`, the `previousTitle`, an optional `projectTitle`, and a `rubric` that says what a good title names.
return`Generate a title that will help the user recognize this T3 Code thread weeks later.
370
380
Return JSON with keys title and needsRefinement.
371
381
Set needsRefinement to true only if the subject is still unknown, such as an unresolved link, "fix this", or an unexplained attachment. Otherwise set it to false.
372
382
@@ -387,13 +397,17 @@ Editorial rules:
387
397
- For research, name the question domain rather than the requested research process.
388
398
- Do not claim the work is complete.
389
399
- Do not copy and truncate the user's message.
390
-
- Avoid project names already visible in the UI, quotes, labels, filler, and trailing punctuation.
400
+
${avoidRule(projectTitle,"quotes, labels, filler, and trailing punctuation")}
391
401
- Use attached images as primary context for UI issues.
392
402
- When a URL or attachment is the only source of the subject, use available tools to inspect it directly.
393
403
- Local git history is not evidence of what a linked PR or issue is about. Never title the thread after branch names, commit messages, or merged commits found in the checkout.
394
404
- If a linked PR or issue cannot be read, fall back to the user's stated action plus its number, such as "Take Over PR 8588". This is the one case where a PR or issue number belongs in the title.`;
return`Regenerate the title for an existing T3 Code thread so the user can recognize it weeks later.
398
412
The previous title was ${JSON.stringify(previousTitle)}.
399
413
Return JSON with keys title and needsRefinement. Set needsRefinement to false.
@@ -416,7 +430,7 @@ Editorial rules:
416
430
- For research, name the question domain rather than the research process.
417
431
- Do not claim the work is complete.
418
432
- Do not copy and truncate a thread message.
419
-
- Avoid project names already visible in the UI, PR numbers, quotes, labels, filler, and trailing punctuation.
433
+
${avoidRule(projectTitle,"PR numbers, quotes, labels, filler, and trailing punctuation")}
420
434
- Use attached images as primary context for UI issues.
421
435
- When a URL or attachment is the only source of the subject, use available tools to inspect it directly.
422
436
- Local git history is not evidence of what a linked PR or issue is about. Never title the thread after branch names, commit messages, or merged commits found in the checkout.
@@ -472,12 +486,12 @@ export function buildThreadTitlePrompt(input: ThreadTitlePromptInput) {
0 commit comments