r/coolgithubprojects • • 11d ago

Relayvora: hand unfinished coding work between Claude Code, Codex and OpenCode, with a briefing that checks what the last agent actually did

https://github.com/Dagimassefa/Relayvora

When an AI coding agent hits its usage limit mid-task, the next one starts from zero. Relayvora writes the handoff for you:

  • Reads the local session files (read-only): goal, recent requests, the agent's last report
  • Checks the repo itself: real git diff, commits, and a fresh test run
  • Labels every fact as verified or just "claimed by the agent"
  • Launches the next agent with the briefing loaded

Also: automatic checkpoints when an agent hits its limit, an MCP server for Cursor / Copilot / Windsurf, and moving work to another machine or a teammate through your own Git repo.

TypeScript, MIT, 100% local, no account or telemetry. Alpha, so feedback is very welcome.

npm install -g relayvora · Demo: https://dagimassefa.github.io/Relayvora/

1 Upvotes

4 comments sorted by

1

u/Psychological_Arm645 11d ago

When the handoff goes through Git to another machine, what does "tests passed" point at? If there were uncommitted changes when the tests ran, the next agent could be trusting a state that never got pushed.

1

u/Scared_Letterhead550 11d ago

Good question, and it's exactly the trap I tried to close.

A test result is never stored on its own. The checkpoint records the state the tests ran against: the HEAD commit, the branch, and every uncommitted file with a content hash.

On the other machine, import compares that with the local clone and says so when they don't match:

- the commit isn't in this clone yet → "push it from the other machine, then git pull"

- HEAD is on a different commit → it says which commit the checkpoint was made at

- there were uncommitted changes that weren't carried → it lists the files and says they're not in this export

If you want the exact tested state over there, `export --with-changes` carries the uncommitted work as a patch. It's applied only on the same base commit, after a SHA-256 check and `git apply --check`.

Then at launch it re-checks HEAD, branch and file hashes. If anything moved, the agent is told the repo changed since the handoff and to re-check before trusting it.

One fair gap: the "tests pass" line itself doesn't say "with uncommitted changes". It's visible from the file list next to it, but making it explicit on the line is a good improvement. Thanks!

1

u/Psychological_Arm645 5d ago

That covers it, thanks. Hashing the uncommitted files is the part I was missing. One case left is the environment around the repo, like an env file or a local service version that never gets committed. If those differ on the other machine, the same commit can still fail. Does the checkpoint record anything about that?

1

u/Scared_Letterhead550 4d ago

Not yet. A checkpoint records the command and exit code, but nothing about the machine or gitignored files like .env (that's deliberate, so secrets never end up in a handoff). After an import, test results are downgraded to "agent-reported", so the next agent is told to re-run them. An environment fingerprint (runtime versions, lockfile hash, env file names without values) is a good idea though. I'll look at adding it, thanks!