AXME CODE
Hand off mid-session work to a fresh Claude Code session — with full context intact
When a Claude Code session hits its context limit or you switch machines, you lose everything. Starting over wastes hours and introduces inconsistencies.
AXME Code packages active session state, open tasks, recent decisions, and file changes into a handoff bundle that lets a new session pick up exactly where you left off.
When a Claude Code session hits its context limit or you switch machines, you lose everything. Starting over wastes hours.
The next session starts where you stopped
Context limits, laptop switches, and end-of-day closes erase in-flight reasoning. Teammates cannot pick up your agent thread without a lengthy verbal transfer.
AXME Code handoff captures active state, open tasks, recent decisions, changed files, and blockers in plans/handoff-*.md. axme_begin_close provides a checklist; axme_finalize_close commits updates atomically.
CAPABILITIES
How it works.
Active state
Current task and branch.
Open tasks
Todo list for next session.
Recent decisions
What was decided today.
File changes
Diff since last handoff.
DEEP DIVE
Production patterns.
Cross-machine
Handoff between laptops.
Team handoff
Pass work to a teammate.
Formal close vs abrupt exit
Run begin_close before long breaks — extract memories and decisions, write handoff, finalize. If the IDE closes abruptly, Claude Code may run a background auditor on the transcript; on Cursor, save during work with axme_save_* so nothing critical lives only in chat.
Team handoff passes the same bundle to the next engineer — same .axme-code/, same oracle, new session.
Common questions
- What should handoff include?
- Stop point, open PRs, blockers, next steps, and any decisions made this session — the close checklist prompts for these.
- Can handoff work across machines?
- Yes — commit or sync .axme-code/ per your security model, or use shared storage for team KB.
- How does handoff relate to persistent memory?
- Memory is long-term knowledge; handoff is the latest chapter — both appear in axme_context.
Related reading
Deeper dives from the AXME blog.
I Went on Vacation. My Agent Came Back to an Empty Project.
Five days off. Session handoff gone. Half a week of decisions forgotten. Here's the 'what was I doing yesterday' problem and why session close is a ritual that matters.
Read post →Subagents Without Context: Claude Code's Silent Bug
When Claude Code spawns a subagent to run a task in parallel, the subagent starts fresh. It doesn't inherit the parent's memory. Work gets done, but context is lost. Here's the fix, and why it's fragile.
Read post →
Related
Related links
Ship your first durable agent — in under 10 minutes.
Free tier. No credit card. Self-host or hosted — your choice.