RelayKit

Harness augmentation for multi-tool, human-in-the-loop parallel execution.

RelayKit augments existing harnesses like Codex, Claude Code, Gemini CLI, and Antigravity so one operator can run parallel lanes, assign deliberate roles, and keep the human in charge of coordination instead of treating every tool as a generic assistant.

Task intake, lane recommendation, onboarding, checkpoints, handoffs, and learning are the main mechanisms. They exist to make existing harnesses behave like one operator-directed system.

RelayKit now also keeps lightweight issue state for critique-driven work, so old review docs do not have to act like permanent backlog forever.

Install RelayKit:

pipx install "git+https://github.com/pavelalbawork/RelayKit.git"
pipx ensurepath

That is the normal install path. It does not require cloning the repo first.

If you are developing locally or want an editable install from a checkout, clone the repo and install from the working tree instead:

git clone git@github.com:pavelalbawork/RelayKit.git
cd RelayKit
pipx install -e .
pipx ensurepath

Wire your host:

relaykit setup --host codex

If your shell still says command not found: relaykit, reload it once:

exec zsh

If you want to continue immediately without reloading the shell, use the direct pipx app path once:

~/.local/bin/relaykit setup --host codex

Swap codex for claude-code, gemini-cli, or antigravity.

Supported hosts:

• codex
• claude-code
• gemini-cli
• antigravity

Run setup once per host you actually want RelayKit available in. To wire all supported hosts in one pass:

relaykit setup --all-hosts

Then restart your host and say:

Use RelayKit MCP tools directly.

When the host starts using RelayKit, the operator rhythm should stay explicit:

• confirm the task before real work starts
• checkpoint after the first concrete artifact, blocker, or verified fin