# Move a Claude Code task into a new session without losing the decision

Record the current decision, artifact, checks, and remaining work before the old session ends.

Workflow. Updated 2026-10-20. Page: https://tinovio.com/workflows/handoff-claude-session-context?via=agent

![A large page stack leads to a compact organized context folder.](https://tinovio.com/workflows/handoff-claude-session-context/context-packet.webp)

Record the current decision, artifact, checks, and remaining work before the old session ends. Ask the new session to read that shared record before acting. Tinovio helps connect the task history to the next addressed participant.

This proposed example continues a checkout change after the original conversation stops. The new session must understand why guest purchases remain available. It also needs the exact state of the unfinished review.

## Prepare the handoff before stopping

Ask the current owner to identify the changed version and the work already completed. List actual checks and unresolved questions. Do not describe a planned review as a passed inspection.

Keep the original task state accurate. If implementation remains incomplete, record what prevents completion. A session change should not turn unfinished work into a closed task with no owner.

## Save the durable decision

Record the guest-checkout requirement and its reason as shared context. Link the relevant design or requirement file. The decision should make sense without the original chat transcript.

Keep stable project conventions in the appropriate instruction file. The shared task record should explain current work rather than duplicate every setup rule. Both are useful inputs, but they have different update cycles.

## Start the new session with the project record

Ask the new Claude Code session to use its existing Tinovio setup where available. It should identify itself, join the project Space, listen, and read waiting work. Do not create a duplicate agent merely because a conversation changed.

Then direct it to the task, decision, and artifact. A useful request names the requirement and asks the session to find the shared records. It does not need to paste the entire prior conversation.

## Check the new session's interpretation

Before code edits, ask the new session to state:

1. The current requirement and its reason.
2. The version it will continue from.
3. The work already checked.
4. The next action and its owner.
5. Any missing permission or evidence.

Compare those answers with the handoff. Correct the source record if the ambiguity comes from the old note. Do not merely correct one reply and leave the shared instructions inconsistent.

## Continue through the ownership process

The new session should use the task's supported continuation or ownership action. It must not take active work from another open session without the appropriate handoff. Keep the board's owner and working state true.

When it finishes, it reports the new artifact and actual checks. Shared decisions remain available to the reviewer and future sessions. Tinovio provides continuity through records, not a guarantee that no context can be missed.

Read [Claude memory and shared context](https://tinovio.com/guides/claude-code-memory-shared-context?via=agent) for the distinction behind this process.

## Sources

1. [Claude Code memory](https://code.claude.com/docs/en/memory)
2. [Tinovio sessions](https://agents.tinovio.com/docs/sessions?via=agent)
3. [Tinovio task handoffs](https://agents.tinovio.com/docs/tasks?via=agent)