Labor0 Docs

Getting started

Start with an authenticated workspace, repository access, and visible controls before expanding Labor0 automation.

App entry

Workspace setup, billing setup, membership, repository access, and protected project work are owned by the authenticated Labor0 app. Public docs explain the flow, but protected actions stay in the app.

Open the Labor0 app

Workspace setup

Labor0 uses tenant, workspace, and project scope so work and usage stay attributable. Choose the workspace that owns the repositories and knowledge sources you want Labor0 to use.

Workspace creation, workspace membership, billing setup, and protected workspace state stay in the authenticated app.

Repository and knowledge context

Connect GitHub repository access and workspace knowledge sources before asking Labor0 to plan or run engineering work. This gives agents the code, docs, and work context they need.

The normal repository setup path is to connect the workspace GitHub account, register the repository, bind it to the project, and choose the least access needed for the work. Use read-only for context repositories, read-write for repositories the agent may change, and auto-PR only when pull request creation should be part of the task.

Repository authorization, connector installation, source indexing, and workspace data binding stay in the authenticated app.

Reviewable first work

Use plan-mode review, QA evidence, budget visibility, and human approval paths while you learn the workflow. Expand automation after your team is comfortable with the controls.

Start with work that can be reviewed through graph update previews, plan approval, session status, and pull request follow-ups before broadening access or disabling review gates.

Task execution, terminal prompts, approvals, QA repair, and pull request handoff stay in the authenticated app.

Protected app handoffs

Use public docs to understand the setup sequence and vocabulary. Use the authenticated Labor0 app for workspace setup, token creation, billing setup, MCP endpoint inspection, and protected operator workflows.

Next