Name local agent sessions after the issue branch and resume them #2
No reviewers
Labels
No labels
ai::retry
ai::retry_once
ai::retry_until_green
ai::validate_plan
status::blocked
status::done
status::functional_analysis
status::in_ci
status::in_development
status::in_review
status::technical_analysis
status::waiting_info
status::waiting_validation
type::analysis
type::bug
type::question
type::task
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Alchemic.Studio/Alfred!2
Loading…
Reference in a new issue
No description provided.
Delete branch "agent/issue-1-add-a-name-on-client-and-resume-from-it"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Updates
docs/specification.mdso a local coding-agent CLI keeps one continuous memory per issue. The session is named after the issue's branch, and each later run of the same issue tries to resume it.Changes by section
finallyblock.SessionRefadded toLlmRequest.sessionId,resumedandresumeFallbackadded toLlmResult.resumableSessionsandsessionStatePathcapabilities.llm_sessions, aresumable_sessionscolumn onagent_installations, and a note onmailboxes.branch_name.AGENT_SESSION_RESUME, defaulttrue, at organization and project scope.Validation
The repository holds only the specification. A script confirmed that every Markdown table has a consistent column count, and the cross-references were reviewed by reading. The edited Mermaid diagram (§13.1) was not rendered.
🤖 Generated with Claude Code
Closes #1
Specify named, resumable sessions for local coding-agent CLIs (claude-code, codex, opencode, copilot, grok-build when verified): - the session name is the issue's branch name, fixed at the first run of the issue mailbox and stored in mailboxes.branch_name (§7.3) - every run of the same issue mailbox resumes the previous session of the same adapter, using the native id stored in llm_sessions - silent fallback to a fresh session with a recorded reason; it never fails the run, never counts as an LLM retry and never comments - session state lives in {base}/.agent-sessions/, scoped per mailbox and adapter; only the CLI's sessions subdirectory is mounted, and it is removed when the issue is done or cancelled, on a 404 and by the orphan sweep - new capability resumableSessions/sessionStatePath, SessionRef in LlmRequest, session fields in LlmResult and llm_sessions - new runtime setting AGENT_SESSION_RESUME (default true) - accepted risk documented in §17.5 and §24.3; testing contract rows added; non-goal 3 reworded Refs: #1WIP: Name local agent sessions after the issue branch and resume themto Name local agent sessions after the issue branch and resume them