Alimenter votre agent
La commande propre à l'éditeur. Ce n'est pas un endpoint PlugMCP.
Host a copy with our keys and logs.
npx -y [email protected]Claude Code n'a pas de lien d'installation pour une commande locale. Copiez la commande ci-dessous et exécutez-la dans un terminal.
claude mcp add landrace -- npx -y landrace@2.1.0À exécuter dans un terminal.
{ "mcpServers": { "landrace": { "command": "npx", "args": [ "-y", "[email protected]" ] } }}claude_desktop_config.json
URL distante ou commande sur votre machine ? Ce qui distingue les deux installations
Exécuter sur PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LancerDe l'éditeur
Landrace takes issues from your issue tracker; each one it works on is an item.
workflow.yaml routes on it. landrace validate checks that every loop has a bound before anything runs. When two rules match, the item stops instead of guessing. An item stopped for a person, for this or for a failure, is a ().Local-first orchestration for coding agents, defined inside your project.
.landrace/ folder: its workflows live there and can be reviewed like code. One landrace start runs several side by side (this repository runs two: full-cycle, which starts with a written spec, and fastlane, for small changes), and each item is worked by one of them only: an item two would take stops for a person (Several workflows).landrace_pair over MCP (the operator tools). It works with Claude Code and Codex; Codex can only carry on a step its agent has already run.Landrace watches your issue tracker. Each issue it works on is an item, and a workflow moves the item through stages: spec, build, review, fix, CI and merge. At some stages a coding agent, such as Claude Code or Codex, does one piece of work, called a step. It writes the spec, the code, the review or the fix.
The agent never chooses what happens next. It answers with a value, and a rule in the workflow routes on that value. A deterministic state machine decides every step, and a person decides at the gates you choose. This repository ships two workflows: full-cycle starts with a written spec, and fastlane, for small changes, starts at the build.
stateDiagram-v2
direction LR
state "A person approves the spec" as approve
state "Merge: a person, or fastlane by itself" as merge
[*] --> spec: full-cycle
[*] --> build: fastlane
spec --> approve
approve --> build
build --> review
review --> fix: findings
fix --> review
review --> merge: clean, full-cycle
review --> ci: clean, fastlane
ci --> build: checks failed
ci --> merge: checks passed
merge --> [*]
You need Node 22 or newer, a GitHub repository and a classic token with the repo scope, and Claude Code or Codex installed.
In your repository's root:
npm install -g landrace
landrace init main
init writes .landrace/: a commented landrace.yaml, and a workflow named main that takes issues labelled lr:main. It also adds .landrace/.env to .gitignore. Before you start it, connect it to GitHub and Claude Code.
Create .landrace/hooks/project.ts. A hook is a TypeScript module that connects Landrace to a tracker, a forge (where pull requests live) or a coding agent:
import { compose } from "landrace/kit";
import { GitHubForge, GitHubIssues, GitHubPages } from "landrace/integrations/github";
import { Claude } from "landrace/integrations/claude";
export const { preflight, source, operator, pre, post, spec } = compose({
tracker: new GitHubIssues(), forge: new GitHubForge({ closingRefs: true }), docs: new GitHubPages(),
});
export const claude = new Claude();
Replace .landrace/landrace.yaml with this, naming your own repository:
version: 1
agent:
adapter: claude
tracker:
repo: your-org/your-repo # your GitHub repository, as owner/name
secrets:
githubToken: $GITHUB_TOKEN
log:
redact: [githubToken]
In .landrace/workflows/main/workflow.yaml, uncomment hooks: and list ../../hooks/project.ts under it.
Put your token in .landrace/.env, as GITHUB_TOKEN= followed by the token.
Using Codex instead? Its hook and settings are in Integrations. Then start Landrace:
landrace start
start checks the token's permissions, then opens the board at http://127.0.0.1:4545/ in your browser. Every 60 seconds it runs a tick: one pass over the tracker's issues.
To give it work, label an issue lr:main. On the next tick the issue enters the todo stage, and the board lists it under Waiting. The workflow init wrote runs no agent yet, so the issue stays there. To run one, give todo a step, as Workflows shows. A step that changes files reaches only the hosts listed under agent.sandbox.hosts, so list your forge and package registry there: see A write step's sandbox. Each step is a paid agent run, and a cap in the workflow bounds how many times each step runs.
Both shipped workflows are examples. Their hooks, step prompts and protected paths are this repository's own, so a copy needs them changed. Each open item is claimed by exactly one workflow, decided by its labels.
Both also stop for a person at a halt: a step whose output was broken, a push the forge refused, or a blocker that was dropped. Fastlane's protected paths are .landrace/, CI, pnpm's dependency files and the agents' instructions. Every stage, cap and protected path is in Workflows.
landrace start serves the board on 127.0.0.1 only. It shows:
From the board, a person can reply on an item, ask the step that last ran a question, then hand the item back to its workflow. They can retry a failed step, or send an item back to an earlier step. They can also pair on a step. Browser notifications say when an item needs you.
A Claude Code plugin shows the same board in a pane beside the chat: see The board in a Claude Code pane.
landrace mcp is Landrace's operator server: an MCP server over stdio, whose tools read and drive items as the board does, and also open and edit them. Claude Code, Codex or Cursor use it from a chat, where you type requests such as:
The agent answers them with tools such as landrace_waiting, landrace_create_item, landrace_reply, landrace_goto, and landrace_update_item, whose relate field links one item to another. Every tool is in the operator tools. How this repository connects Claude Code and Codex is in Connecting an editor.
The Chat entries in an item's ⋯ menu on the board open a chat about it over this server, with the prompt filled in. A step allowed to create sub-items gets the engine's own server instead, a separate one bound to its item, with exactly one tool, landrace_create_child: see Workflows.
"Blocked by" on the tracker holds an item until its blockers are done. It is a relationship, a typed link from one item to another: GitHub's issue dependencies, or Jira's "Blocks" links. Both workflows hold a blocked item before it builds, and the board shows it under Waiting with a note such as waiting on #55, #56, #57. A blocker that was dropped, cannot be read, or sits on a cycle sends the item to a person instead. See Waiting on blockers.
flowchart LR
tracker[("Tracker")] -->|items, labels, comments| engine["Landrace engine"]
engine -->|a step's prompt| agent["Coding agent"]
agent -->|commits on the item's branch| forge[("Forge")]
forge -->|pull requests, reviews, checks| engine
Landrace develops itself on GitHub, Claude Code and Slack. The others pass their tests offline, but nobody has checked them against the live service yet.
GitHub, GitLab, Jira and Notion each have a script that checks the integration against a live account. To connect something else, see Writing an integration.
127.0.0.1. Landrace reaches the outside only through your hooks, through telemetry when you turn it on, and through npm's registry, which start asks whether a newer version is out (turned off with LANDRACE_NO_UPDATE_CHECK=1).Contributions are welcome. CONTRIBUTING.md says what a change needs to be merged: the gate, tests first, and the boundaries the code keeps.
Landrace is released under the MIT License.
Local-first orchestration for coding agents, defined inside your project.
{ "mcpServers": { "landrace": { "command": "npx", "args": [ "-y", "[email protected]" ] } }}Outils
Pas encore de liste d'outils. Les serveurs distants en obtiennent une après le premier contrôle d'état.
FAQ
Copiez sur cette page la configuration stdio pour Cursor, Claude Desktop, Claude Code ou VS Code. Elle utilise l'installation de l'éditeur, pas un proxy PlugMCP.
Aucune variable d'environnement requise n'est indiquée sur cette fiche.
Landrace s'exécute en local via stdio.
Dernière vérification : 2026-11-13. Local-first orchestration for coding agents, defined inside your project.