Yonder
hypothetical-money-machine/yonder
Despache agentes de código para remotes; seu laptop é o plano de controle
Ver no GitHubAgent de despacho headless que executa trabalhos de codificação em máquinas remotas (SSH, containers, cloud, local) sob controle nativo do Claude Code. Implementa um protocolo robusto com invariante único: toda conclusão de tarefa deixa assinatura on-disk em events.jsonl, eliminando falhas silenciosas.
Instalação
npx convez-ai hypothetical-money-machine/yonder1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Executar tarefas de codificação em servidores remotos via SSH
- Coordenar múltiplos harnesses (Claude Code, cursor-agent, codex) em N máquinas
- Garantir rastreabilidade e recuperação de falhas em jobs distribuídos
- Automatizar pipelines de desenvolvimento sem backend hospedado
Veredito

Projeto ambicioso em fase inicial (Phase 0) que resolve problema real: coordenar agentes de IA headless em infraestrutura heterogênea. Protocolo bem pensado com invariante forte (terminal record em events.jsonl), mas ainda requer harnesses e remotes reais. Para equipes que controlam sua própria infraestrutura e buscam orquestração de código distribuído.
README
A tradução para o português deste README ainda está na fila.
Yonder
Work runs over yonder, on machines you own.
Yonder dispatches headless coding-agent jobs to N remotes (SSH hosts, local subprocesses, cloud VMs, containers/WSL) running N harnesses (Claude Code,
cursor-agent,codex,gemini, …), driven as natively as possible from inside Claude Code. Your laptop is the control plane; the work runs elsewhere.
Open source. No hosted backend required. Ships under the hypothetical-money-machine
org. ccdispatch / claude-dispatch are legacy names for the same tool.
Status: Phase 0 complete. The frozen protocol core (
internal/protocol), the four adapter seams, and the runner that owns the one invariant are built and tested (go test -race ./...green), proven end-to-end with a null harness — including SIGKILL recovery. Real remotes, harnesses, and git sync land in Phase 1. Seeplanning/00-architecture.mdfor the shape.
The one invariant
A job is finished iff its terminal record exists in events.jsonl.
Silence is never success — a dropped pipe, a killed process, or a hung agent
cannot fake completion, because completion has a positive, on-disk signature anyone
(you, a script, another agent) can check.
Everything else — which machine, which agent, how source moves — is an adapter around that spine.
Docs
specs/00-protocol-abi.md— the frozen contract: job-dir layout, theevents.jsonlevent model, the terminal record, exit semantics. Start here.specs/01-remote-adapter.md— the Remote interface (SSH / local / container / cloud) + bootstrap.specs/02-harness-adapter.md— the Harness interface + per-harness normalization + headless auth.specs/03-sync-adapter.md— git-branch spine + local-worktree fast path.specs/04-plugin-integration.md— MCP tools, the/dispatchskill, monitors.specs/05-model-router-mode.md— the optional, documented-only model-routing mode.specs/06-security-model.md— auth, secrets, permission scoping, supply-chain.planning/00-architecture.md— the single-binary subcommand model, package layout, how the adapter seams compose.docs/landing-page.md— the landing/README hero copy (used once there's a shippable product).
License
Apache-2.0 (planned — LICENSE lands with the first code drop).