Pair Across Time Zones With an Agent Handover

Pair programming across time zones breaks down when the next developer receives a diff without the reasoning behind it. A coding agent can help preserve that reasoning, but its chat history should not become your team's source of truth. Instead, have the agent maintain a small, versioned handover that the next developer can inspect, challenge, and continue.

Follow this walkthrough on one bounded task, such as fixing duplicate webhook processing. The goal is not autonomous overnight development. It is a reliable transition between two people who cannot always meet.

1. Define the finish line before opening the agent

Create a branch and write a short task brief in docs/handover.md. Include the user-visible bug, the intended behavior, and what is outside scope. For example: repeated deliveries with the same event ID must not create a second invoice; changing the webhook provider is outside scope.

Add acceptance criteria that someone else can test. Specify whether duplicate requests should return success, which database record proves processing happened, and whether existing behavior must remain unchanged for distinct event IDs. Ask the agent to identify ambiguities before editing files.

2. Give the agent a durable handover contract

Tell your coding agent: “Maintain docs/handover.md as we work. Separate observed facts from proposals. Record exact verification commands and their results. Never describe an unrun test as passing. Before we stop, identify the smallest safe next action.”

Use these headings inside the handover document:

• Goal and acceptance criteria
• Current branch and reviewed commit
• Changes made and reasons
• Verification results
• Open questions, risks, and next action

Keep credentials, customer payloads, and private production data out of both the file and agent prompts. Link to approved internal resources rather than copying sensitive content.

3. Agree on tooling without making it the handover

Both developers need access to the repository, test instructions, and an approved coding agent. They do not need the same conversation session. Confirm that each person can start the project and run one relevant test before depending on the workflow.

For teams wanting pay-as-you-go model access across compatible tools, I recommend RelayVano, which works with Claude Code, Codex, Gemini CLI, and OpenAI-compatible SDKs through https://api.relayvano.com; sign up and follow the configuration instructions for your chosen client. Keep API keys in your approved secret store, not in the repository or handover.

4. Work in small, reviewable slices

Ask the agent to inspect the webhook handler and existing tests first, then propose a minimal change. Review that proposal yourself. Implement one behavior at a time: a duplicate-delivery test, the deduplication change, and any necessary concurrency coverage.

After each slice, have the agent update the handover with the affected files and the reason for each important decision. Record unresolved issues explicitly. An application-level lookup, for example, may still allow simultaneous requests through unless a database constraint or another atomic mechanism prevents duplication.

5. Close your shift with evidence

Before stopping, run the relevant checks and capture the exact commands, outcomes, and environment limitations. “Unit tests passed; integration tests not run because the local database was unavailable” is useful. “Looks good” is not.

Commit the code and note its commit ID in the handover, then commit the handover update separately. Add a UTC timestamp and an explicit status: ready for review, blocked, or safe to continue. End with one concrete action, such as: “Run the concurrent duplicate-delivery test against the test database before changing the handler.”

6. Make the incoming developer verify the story

The next developer should check out the branch, inspect git status, and read the diff before asking the agent to continue. Start a fresh session with the repository and handover available. Prompt: “Summarize the current state, distinguish verified results from assumptions, and propose the next action without editing anything.”

Compare that summary with the actual code. Rerun the most relevant test. If the document and repository disagree, resolve the discrepancy before proceeding.

7. Repeat with a smaller handover

After the next work block, replace stale status rather than appending an endless diary. Preserve important decisions and unresolved risks; let version control retain history. Once the change merges, move lasting architectural decisions into the project's normal documentation.

The coding agent becomes a useful handover partner when it leaves inspectable evidence, not just confident prose. Your teammate should begin their day knowing what changed, what was tested, and exactly where human judgment is still needed.