--- type: decision tldr: 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. status: accepted decided_on: 2026-10-24 decided_by: Michał Kopeć supersedes: docs/decisions/0005-session-titles-and-routines.md affects: AGENTS.md, ckb.yaml, .agents/skills/ckb-add-conversation/, docs/MANUAL.md confidence: 0.85 quality: 0.8 last_updated: 2026-10-24 freshness_window_days: 365 retention: 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](0005-session-titles-and-routines.md) ## 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 1. 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. 2. 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. 3. `conversations.ask_title` is replaced by `conversations.announce_title` (default `true`). Off, the title is still set, only the line goes. No KB ever shipped with `ask_title` other 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.