Skip to content

feat(summary): AI-chosen project names, kept once chosen - #9

Merged
MilosMosovsky merged 1 commit into
mainfrom
feat/summary-project-names
Nov 6, 2026
Merged

MilosMosovsky merged 1 commit into
mainfrom
feat/summary-project-names

Conversation

@MilosMosovsky

@MilosMosovsky MilosMosovsky commented Nov 6, 2026 •

Copy link
Copy Markdown
Owner

Summary projects were titled with their key, so a git repo outside the code folder showed as a full path (~/Documents/Claude/Projects/AI Adoption Onboarding task).

Each project now gets a display name from the model, once:

  • The first summary run that sees a project asks the summary model for a short name (one batched call, up to 12 projects) and saves it to names.json in the summary state folder. Later runs reuse the saved name, so it never changes, and topics stay keyed by the project path.
  • A second checkout of the same repository gets its owner folder appended ("Portal · acme"). The model is no longer asked to tell checkouts apart, because in a live run it named them after their current work (for example "Portal Plan Review").
  • Empty, too-long (over 40 characters) or duplicate answers are dropped. A failed call only logs, the path shows, and the next run tries again.
  • On the page, the project list and headings show the name, with the path in small grey text on the right of the heading. Saved runs from before this change have no name and render as before.
  • get_summary returns name and filters by name or path.

Testing:

  • go vet and go test ./... pass.
  • New tests in summary_names_test.go: names are kept and only new projects are asked about; bad answers are rejected; duplicates get the owner suffix; a failed call names nothing.
  • A live run with a dev build on real sessions named 15 projects, including a folder outside the code folder that had shown as its full path.

🤖 Generated with Claude Code

https://claude.ai/code/session_01NtvhFvhWywmqE7ZEmKxLJy

The first summary that sees a project asks the model for a short display
name and saves it in names.json; later runs reuse it, so the name never
changes and topics stay keyed by the project path. A second checkout of the
same repository gets its owner folder appended. Naming failures only log,
and the path shows until a later run names the project.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NtvhFvhWywmqE7ZEmKxLJy
@MilosMosovsky
MilosMosovsky merged commit 32f1591 into main Nov 6, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant