The trajectory inside is ATIF, the format of the Harbor framework we already use to deliver agent runs on our tasks. Harbor can already convert and hand off the sessions it runs itself in a sandbox. easy_harbor does the same for everyday sessions on a laptop, with real repos, long histories, subagents and secrets.
Workflows / 04 Hand off
easy_harbor
Hand a Claude Code session to a teammate.
A long agent session holds more than its final diff: the plan, the decisions, the dead ends, the commands that worked. easy_harbor turns any Claude Code session into one standard bundle that another person can read in a browser, reproduce from the same repo state, or continue in their own Claude Code.
- One file per session
- Trajectory, summary, viewer, repo patch and the original log.
- Two modes
- Replicate what happened, or continue where it stopped.
- ATIF inside
- The trajectory format of the Harbor framework.
- Reviewed before it leaves
- Nothing is packed until the sender approves the redaction.
How it works
-
easy_harbor reads one session: the log with its subagents and compactions, the plan and notes you opt in, and the repo's start and end commits with the uncommitted diff.
-
Keys, tokens, emails and home paths become typed placeholders such as
${HOME}, which the receiver fills back in. The sender reviews the report; nothing is packed before that. -
Every action becomes one ATIF step, with tool definitions, compactions and nested subagents. The redacted original log is kept as well, for an exact resume.
-
A summary for the person picking it up and a continuation brief for their agent. Files, diffs and cost come from code; the narrative cites the steps it draws on.
-
An offline viewer is rendered, and everything goes into one
.harborfile that can be sent like any other file. -
On the receiver's machine,
inspectchecks the Claude Code version, tools and MCP servers, the commits, and what resuming would cost, before anything is changed. -
Replicate rebuilds the repo state and steps through the run. Continue resumes the session in their own checkout under a fresh id, or starts a new one from the brief.
What you get
- Replicate
- Rebuild the repo at the session's starting commit, apply the end state and check it against recorded file hashes, then step through every message, tool call and diff in the viewer. A session can also be emitted as a Harbor task and re-run by an agent.
- Continue
- After checking the receiver's setup, easy_harbor picks the best of three: an exact resume with paths rewritten to their checkout, a trimmed resume, or a new session that starts from the continuation brief.
- Redacted first
- Secrets become typed placeholders and paths become
${PROJECT_ROOT}or${HOME}. Thinking blocks are dropped, never edited. The bundle carries a report of everything removed. - Readable by people
- A summary for whoever picks it up: the goal, what was decided and why, the current state, open work and how to test it. The raw log stays the source of truth.
The bundle
fix-loader.harbor/ manifest.json # source, versions, repo, commits, placeholders, requirements trajectory.json # ATIF: steps, tool definitions, compactions, subagents summary.md # goal, decisions, current state, open work, how to test brief.md # a continuation brief, ready to start a new session native/ # the redacted original session, for an exact resume repo/ # commits, end.patch, hashes of touched files viewer/index.html # timeline, tool calls, diffs, subagent tree redaction/ # what was removed, and why easy_harbor pack --current -o fix-loader.harbor # redact, summarise, rendereasy_harbor view fix-loader.harbor # open the viewereasy_harbor inspect fix-loader.harbor # versions, tools, cost to resumeeasy_harbor continue fix-loader.harbor # resume, or start from the briefeasy_harbor replicate fix-loader.harbor # rebuild the repo, step throughOpen questions
- Claude Code's session format is internal and changes between versions, so the reader is versioned per release and passes unknown records through untouched.
- Exact resume across accounts is not yet verified. Thinking blocks are dropped rather than edited, and the brief is always there as a fallback.
- Redaction is best-effort, which is why a person reviews every report before a bundle is packed.
- Changes outside the repo, such as databases or cloud resources, cannot be replicated. The bundle lists them instead of hiding them.
Plan
- First: pack, redact and view a session.
- Then: summaries and continuation briefs.
- Then: exact resume on another person's machine.