North — Lander de Agentes para Git
tompassarelli/lodestar
Orquestração segura de commits de agentes IA em Git, com validação e revert automático
Ver no GitHubMCP server que automatiza o landing de mudanças de agentes de IA em repositórios Git sem intervenção humana. Implementa sandboxing, gates de validação determinísticos e rebase automático com segurança, permitindo que múltiplos agentes trabalhem em paralelo em suas próprias lanes. Reduz tempo de integração em ~75% comparado a fluxos manuais.
Instalação
npx convez-ai tompassarelli/lodestar1 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
- Automatizar landing de pull requests geradas por agentes de código (Claude Code, OpenCode)
- Paralelizar trabalho de múltiplos agentes com isolamento seguro por worktree
- Implementar CI/CD sem intervenção humana com validação pré-queue e pós-landing
- Monitorar e reverter automaticamente mudanças que quebram testes após push
Veredito

Ferramenta de produção para equipes que confiam em agentes de IA para desenvolvimento. Exige infraestrutura Linux/Nix e conhecimento profundo de Git; valor está em paralelização segura de agentes com overhead mínimo. Leitura obrigatória: docs/landing.md e docs/terms.md para entender modelo de fleet e policy.
README
A tradução para o português deste README ainda está na fila.
North checks and lands changes from coding agents on main, with no person in the loop. An agent works in its own lane worktree inside the worker sandbox, checks its change against the repository's deterministic gates and public-repo scans, and hands it in; the lander rebases the lane onto main, runs a one-shot security read when ring-0 paths or dependencies change, pushes, and reverts a lane whose after-landing checks fail. It wraps the command-line clients you already use (Claude Code, OpenCode and Pi), adding the sandbox, the policy switches and the lander.
Measured result
On small tasks north lands a change in 12 s against T3 Code's 16 s at one worker and 13 s against 21 s at five at once, at about 0.3 of the cost (15 pairs per cell; method and every row on the comparison page).
Quickstart
You need x86_64 Linux with Nix and flakes, git, and Claude Code installed and signed in. The command
clones and builds north, makes an account profile from the Claude Code login, has one agent land one
change on a scratch repository and exits 0 when it is on main (the onboarding page).
nix run github:tompassarelli/north#setup
Then put ~/code/north/main/target/debug on your PATH and run north --help to list its commands.
How a change lands
- Box. An issue's box carries a
Done when:line with a command, the check that closes it. - Work. A worker session runs in its own worktree. Confined workers stay out of the main checkout, other lanes, secrets and ring-0 paths.
- Hand-in. The session checks the lane against the repository's pre-queue gates, commits only the named paths and queues a ticket for the lander.
- Landing. The lander rebases the lane on main, runs the checks the change touches and pushes it, then runs the after-landing tests the batch reaches, every test when it reaches every crate, and reverts a lane that breaks main (docs/landing.md).
The words follow docs/terms.md: a model is the weights, the harness turns a model into an agent, and a fleet is many agents with roles, staffing and policy.
Where things live
- src/: the
northcommand, one file per command - crates/: the libraries behind it, one crate per responsibility in seven layers (ARCHITECTURE.md)
- harness/: the hooks, skills, policy and defaults north installs into each agent
- docs/: concept pages, one record per feature, and the rationale for each choice
- evals/: the runners that measure north against other harnesses
- examples/: a working operator repository with synthetic values
Finding a fact
- AGENTS.md: the rules for working in this repository
- docs/README.md: every page, in reading order
- docs/features/: what each command is for
- docs/rationale/: why it is built this way
License
MIT or Apache-2.0, at your choice: LICENSE-MIT, LICENSE-APACHE.