Scope and navigation
Labor0 keeps tenant, workspace, and project scope visible so work, usage, repositories, and settings stay attached to the right place.
Public documentation
Labor0 Docs
Use Labor0 Docs to set up the authenticated app, connect workspace tools, and understand how app workflows stay reviewable.
Open the app to sign in, choose or create a workspace, and set up the repositories, tokens, billing controls, and runners that make these guides actionable. The authenticated app domain is l0.theaiplatform.app.
Guides
Find the right setup path.
Getting started
Open the Labor0 app, create the right workspace, connect repositories, and start reviewable project work.
Concepts
Understand the app model for scope, navigation, task graphs, assistants, sessions, approvals, QA, and credentials.
MCP
Connect Claude Code, Codex, OpenCode, L0 Nexus, and L0 Tools with app-supplied endpoints and tokens.
Local runners
Install, register, run, and troubleshoot a Labor0 local runner for workspace-owned task execution.
Pricing and credits
Understand Labor0 plans, credits, usage, billing behavior, and protected app handoffs.
Onboarding
Start with governed workspace setup.
Open the app
Sign in at l0.theaiplatform.app, then choose an existing workspace or create the tenant and workspace for your first project.
Prepare a project
Create a project, connect GitHub access, register repositories, and bind the repository your agent work should use.
Start reviewable work
Submit a small task with plan review, visible budget context, QA evidence, and approval controls before expanding automation.
Concepts
The model before workspace work begins.
Task graphs and Kanban
Project requests become task graphs with reviewable plans, Kanban status, sessions, terminals, pull request links, and follow-up actions.
Assistants and sessions
Workspace and project assistants can use text, voice, progress updates, and mediated tools while sessions preserve terminals and approvals.
Review and QA
Approvals, user-input pauses, QA reports, and task diagnosis help teams inspect work before changes move forward.
Messenger bridges
Slack, Discord, Microsoft Teams, and Mattermost bridges connect chat channels to projects after installation and actor linking.
Credentials and tokens
User API tokens, runner tokens, MCP endpoints, and runtime credentials are created or managed from authenticated app settings.
MCP
Connect clients with workspace-scoped endpoints.
- Labor0 tokenCreate a user API token from workspace token settings and reference it through LABOR0_TOKEN in local MCP clients.
- L0 NexusCopy the active workspace endpoint and client snippets from the L0 Nexus endpoint guide in the app.
- Runner MCP serversConfigure project-level Runner MCP servers from Project Settings > Runners when future hosted or local runner sessions should start with shared public HTTPS MCP endpoints.
Runners
Operate local execution deliberately.
Choose execution
Use hosted runners for ordinary work and local runners when work needs private network access, local caches, or a specific machine.
Register in settings
Open workspace Settings > Runners, register the machine, and copy the one-time l0r_ token before leaving the result screen.
Run the daemon
Start labor0-runner daemon with a saved config or LABOR0_RUNNER_TOKEN so the machine can receive workspace work.
Operate safely
Keep runner tokens secret, choose a private work directory, install required tools locally, and troubleshoot with sanitized logs.
Reachability matters
Project Runner MCP settings work only for public HTTPS endpoints; keep localhost, stdio, and private-network MCP servers in machine-local runner setup instead.