Repository navigation
Title sessions in the Claude and Codex apps by item ID and title - #237
Merged
Merged
Conversation
The coordinator sends each spawn the item's title, t<n> · <title> (p<n>
for a planner); the host cleans it, records it in run.json and expands it
as the launch line's {title}. Claude's status finds a session by that title
or the window's name, else by its worktree. The Codex labeller titles a
joined thread with it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Objective
Sessions show a readable title in the Claude and Codex apps:
t<n> · <task title>, orp<n> · <plan title>for a planner. Today a Claude session shows as<repo>-<task>, and a Codex thread's title holds only IDs (p12 > t63).{name}still means<repo>-<task>(the tmux window, branch and run ID).Gates
./dev test(every required lane)internal/session/title_test.go: the title format, whitespace and control characters folded, the 60-character cut, and the fallback to the nameinternal/harness/claude/agents_test.goTestFindAgent: a session is found by its window name or title, else by its worktree (so a rename in the app still finds it)internal/hosts/launch_test.go:{title}is quoted for the shell and falls back to the nameinternal/hostops/spawn_test.go: spawn cleans the title, records it in run.json and launches with itinternal/controlrun/coordinator_test.go: the planner's dispatch carriesp<n> · <title>internal/harness/codex/label_test.go: the labeller uses the run's titleRulings
None.
Review
Verdict: APPROVEDTitleis a new field. The coordinator already posts a notice and retries until the host is upgraded, andengine upgradeupgrades every host in one run.-n: not added.docs/harnesses.mdis at its word budget, and thefindAgentdoc comment already says it.t<n>assertion in a task-dispatch test: not added. Tasks and planners go through the samelaunchcall, andsession.Titlehas its own unit tests.internal/harness/claude/claude.go(findAgent, the status lookup now that the name changes),internal/hostops/spawn.go(the title cleaned again on the host)Deviations
None. Operator follow-up after merge: run
engine upgrade, then change the Claude launch line inhosts.tomlto-n {title} --remote-control {title}and copy the file to every host. A host still on the old engine rejects{title}, so upgrade first.🤖 Generated with Claude Code