Legba Sign in
How it works

A structured execution system around AI agents.

Agents do the work. Legba plans it, routes it, isolates it, verifies it and remembers it. Humans set the objectives and keep the final word.

01 / Architecture

Three layers, one division of responsibility.

AI agents perform work, propose solutions, and generate evidence. The orchestration system manages execution policies, dependencies, task states, and verification procedures. Humans establish objectives, approve important decisions, resolve escalations, and retain authority over the system.

HUMANS Web console Mobile chat Define objectives · approve decisions · resolve escalations
↓ objectives, approvals↑ plans, evidence, escalations
LEGBA · CONTROL PLANEdeterministic
Planner
Turns an objective into steps with dependencies.
Lifecycle & policies
Task states, lane routing, permissions, approvals.
Judge
Independent verification of every result.
Knowledge
Persistent context for planning and verification.
↓ tasks, routed by lane↑ results, evidence
EXECUTION LAYER · REMOTE DAEMONSprobabilistic
container · CODE
branch task/mobile-sidebar
harness: replaceable
container · OPS
env staging · policy-gated
harness: replaceable
container · KNOWLEDGE
repo read · decision log
harness: replaceable
02 / Orchestration

Every task has a lifecycle. Every plan is a chain of tasks.

Legba decomposes an objective into steps. Each step is a task with its own description, expected outcome and lane. Steps chain behind each other: the next one waits in the queue until the previous one passes verification, then a daemon picks it up on its next poll.

blocked
Waiting in the queue behind a previous step. Still editable.
pending
Ready. The daemon for its lane picks it up.
in_progress
An agent works in an isolated container.
done
The Judge passed it. The next step unblocks.
blocked_review
Verification could not resolve it. Escalated for human review.
paused
A human set "pause after" on the previous step. The loop holds until someone resumes it.
Lanes route the work
The lane is the daemon routing key. Changing a step's lane changes which machine executes it.
Plans stay editable
Steps can be inserted, removed or appended. Appending to a finished plan reopens it and queues the new step.
Humans set the brakes
Pause points, approvals and escalations are part of the lifecycle, not exceptions to it.
03 / The Judge

An agent saying "done" is not evidence.

Generating software is relatively easy. Establishing that the software actually satisfies its requirements is considerably harder. Legba separates execution from evaluation: a dedicated verification process compares outcomes against specifications, tests, and other available evidence.

Execution produces results. Verification establishes confidence.

EXPECTED OUTCOME
At ≤768px the drawer contains only Projects, the username and Sign Out. At ≥769px every nav item renders as today. `npm run build` exits 0.
EVIDENCE
Sidebar.jsx changed only · secondary nav gated behind !isMobile · build exit 0
PASS
accepted
FAIL
returned for correction
ESCALATE
human review
04 / Remote execution

Your agents work remotely. Your machine doesn't have to.

Legba separates its control interface from the environments where work actually happens. Tasks run on remote infrastructure inside isolated containers, each with a dedicated branch and working environment.

That enables concurrent execution, reduces interference between tasks, and lets you supervise software production without keeping a local development machine running. The execution layer supports different coding harnesses and agent tools; Legba keeps responsibility for orchestration and verification.

1 task
= 1 container
No shared state between concurrent tasks.
1 task
= 1 branch
Every change reviewable on its own.
N harnesses
1 orchestrator
Swap the agent tool, keep the workflow.

The agent is replaceable. The orchestration system is not.

05 / Persistent knowledge

Software projects should remember what they learn.

Traditional AI coding sessions are temporary. Context is reconstructed, decisions are repeated, and architectural knowledge fragments across conversations and repositories. Legba treats knowledge as a persistent engineering asset: the Knowledge lane keeps an evolving understanding of the system that every later plan, task and verification draws on.

Agents can be temporary. Project knowledge should not be.

WHAT LEGBA KEEPS
System architecturecomponents, boundaries
Implementation decisionswhat was chosen, and why
Repository structurewhere things live
Project historytasks, results, summaries
results → knowledge → planning · execution · verification
06 / Mobile-first control

Run your software factory from anywhere.

Legba gives you a conversational interface for projects, tasks, progress and agents. Move between project-level discussions, task-specific conversations, execution histories and operational status. When a conversation turns into work, Legba proposes the task and you dispatch it with one tap.

The development environment lives on remote infrastructure. The control plane travels with you.

Your phone becomes a command center for software production.

Legba· project chat
the chat modal is unusable on my phone, fix it I can open a task for that. Here is the proposal:
create_task · lane code ChatModal full-screen on mobile + task-kickoff cards tap-usable Outcome: at 390px the modal fills the screen, no horizontal scroll, Dispatch creates a task.
DispatchDismiss
Ask Legba

Humans govern. Agents execute. The system verifies.

Read the philosophy → Request a demo