announce_title replaces ask_title; no question, no waiting. D-0006 reverses point 1 of D-0005. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
1.9 KiB
1.9 KiB
| type | tldr | status | decided_on | decided_by | supersedes | affects | confidence | quality | last_updated | freshness_window_days | retention |
|---|---|---|---|---|---|---|---|---|---|---|---|
| decision | The agent names a new session itself from the first message and states the title in one line of its first reply; the user is never asked and can rename at any time. Reverses point 1 of D-0005. | accepted | 2026-10-24 | Michał Kopeć | docs/decisions/0005-session-titles-and-routines.md | AGENTS.md, ckb.yaml, .agents/skills/ckb-add-conversation/, docs/MANUAL.md | 0.85 | 0.8 | 2026-10-24 | 365 | high |
D-0006 — The agent chooses the session title and only announces it
Status: Accepted · Decided: 2026-10-24 · Deciders: Michał Kopeć · Reverses: point 1 of D-0005
Context
D-0005 made the first reply of every session a question, "What should this conversation be called?", with no work until it was answered. In use the extra round-trip on every session outweighed the benefit: most titles are obvious from the first message anyway.
Decision
- The agent derives a short title (three to six words) from the first
message, or takes one the message names, stores it with
save_conversation.py --set-title, and proceeds with the request in the same turn. - The first reply opens with one line stating the title and that "rename this conversation to …" changes it. That line is the only reminder; it is said once per session.
conversations.ask_titleis replaced byconversations.announce_title(defaulttrue). Off, the title is still set, only the line goes. No KB ever shipped withask_titleother than the template itself, so no migration is written.
Consequences
- Storage, precedence and renaming from D-0005 are unchanged: the saved transcript, its index row and the workload block follow the stored title.
- A poor derived title costs the user one sentence to fix, rather than costing every user one round-trip per session.