DEV Community

George O'Nair
George O'Nair

Posted on Originally published at senrelay.com Fully Autonomous

Continue a Claude Code Task in Codex or Cursor: A Local Handoff Workflow

Claude Code reaches a usage limit while you are debugging. Your next assistant needs the failing command, the approaches you rejected, and the project directory where the work happened.

This walkthrough uses an illustrative debugging session. I maintain Senrelay, the free MIT-licensed tool described below.

Prepare a handoff before switching

Record the working directory and branch, the exact failing test command and its output, attempted fixes, uncommitted changes, and the next step to verify. Repository instructions such as AGENTS.md and CLAUDE.md provide conventions. The session record provides the progress of this particular task.

If you can still use the outgoing assistant, ask it to write those details into a HANDOFF.md file. If a hard usage limit prevents another response, inspect your existing local session history and working tree.

Relay a local session with Senrelay

Senrelay runs on a single Apple Silicon Mac with macOS 14.0 or later. It supports conversation relay for Claude Code, Codex, Cursor, Antigravity, OMP, and OpenCode. Its nine additional configuration hosts have configuration support only.

  1. Install and start Senrelay using the setup guide. Connect both hosts to the local MCP service under the contextcore key.
  2. In the receiving host, enter /contextcore or ask it to relay a conversation.
  3. Check the candidate title, brief summary, source agent, timestamp, conversation ID, and directory. For parallel worktrees, check the exact path before selecting.
  4. Select the conversation. The receiving assistant reads the original messages in bounded pages and then compacts them into its context.
  5. Review the reported stopping point. A number-only selection loads the conversation and waits. Add a concrete instruction when you want the assistant to act.

Example receiving-host conversation:

You: /contextcore
Assistant: 1. Claude Code — webhook retry debugging
           One timeout test remains; retry backoff was already ruled out.
           Project: ~/work/payment-service-fix
           Conversation ID: <session-id>
You: 1
Assistant: [Reads the full conversation, summarizes progress, and waits.]
You: Run the remaining timeout test and investigate its failure.
~~~

## If the new assistant reads only the last few messages

Ask it to check whether transcript_paging.complete is false or messages were omitted. It should call read_conversation_messages from offset=0 and follow each returned next_offset until it is null. Each page can return fewer messages than requested, so adding 30 to the offset blindly can skip messages.

Ask the assistant to report the total number of messages read before summarizing. If it keeps stopping at the preview, update the receiving host's ContextCore skill or command. This matters because restarting the local service alone does not update an installed host skill.

## Verify the working tree before editing

Conversation history can describe an earlier checkout. Confirm the current directory, branch, uncommitted diff, and failing test in the receiving environment. Imported history gives the assistant evidence to inspect. Test results establish the current state.

Senrelay currently supports Apple Silicon macOS on one machine. Windows, Linux, Intel Macs, and cloud device sync fall outside this release's scope. The [installation guide](https://senrelay.com/guide.html) covers the beta setup requirements.

The [complete relay workflow](https://senrelay.com/relay-workflow.html) includes the protocol, execution modes, and platform limits.
Enter fullscreen mode Exit fullscreen mode

Top comments (0)