Skip to content

Instantly share code, notes, and snippets.

@brentkirby
Last active June 20, 2026 17:14
Show Gist options
  • Select an option

  • Save brentkirby/ac6a4295136e71fb35c2ad9c460513b4 to your computer and use it in GitHub Desktop.

Select an option

Save brentkirby/ac6a4295136e71fb35c2ad9c460513b4 to your computer and use it in GitHub Desktop.

Agent Handoff Bridge - Working with a second agent

This project intentionally keeps a mixed agent setup and can be worked by multiple agents:

  • CLAUDE.md is the Claude Code behavior file.
  • AGENTS.md is the Codex / OpenCode etc behavior file.
  • CHANGES.log is the shared handoff log between tools.

They stay in sync through one shared file: CHANGES.log.

CHANGES.log is mandatory after every task - no exceptions, no matter how small. CHANGES.log is local-only handoff state and must never be committed. Do not stage it, include it in PRs, or treat it as a source-controlled artifact.

Rules:

  • Before you start any task: read only the most recent entry (last block) of CHANGES.log — do not load the entire file.
  • After EVERY task that touches any file (including single-line CSS fixes): append a CHANGES.log entry BEFORE ending your turn. Append means add to the END of the file — new entries go after all existing content, not before.
  • Do not skip this step for "small" changes. A one-line fix still requires a log entry.
  • Treat writing to CHANGES.log as the final local step of every task, the same way you would run tests before handing off. Do not commit it.

Each entry must include:

  • timestamp and agent
  • GitHub issue(s) and milestone addressed (e.g. <repo>#12 — Task Name)
  • status
  • what is done
  • files modified
  • remaining work
  • next-agent pickup instruction — if the next issue or milestone is known, name it explicitly (e.g. "pick up #13, M3 relay design, next")
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment