Labor0 Docs

Getting started

Open the Labor0 app, create the right workspace, connect repositories, and start reviewable project work.

Labor0 setup starts in the authenticated app. Use these docs to understand the order of work, then use the app for workspace-specific values, private settings, tokens, billing setup, repository access, and task execution.

Open the app

  1. Open l0.theaiplatform.app.
  2. Sign in or sign up.
  3. Choose an existing workspace, or create a workspace from the start screen.
  4. If your account has no tenant yet, create the tenant first and return to workspace setup.

The app root is the product entry point, not a marketing page. Signed-in users land in workspace selection, recent workspace recovery, or the workspace creation path.

Create the workspace

A workspace is where Labor0 keeps projects, repository access, MCP setup, runners, usage visibility, and team settings. Choose a clear workspace name and slug so teammates can recognize the environment they are entering.

After the workspace exists, check billing readiness before starting billable work. Billing managers can create a billing profile or start payment setup from the app when required. Other workspace members see guidance to contact the billing owner.

Create a project

Projects keep engineering work scoped. Create a project from the workspace project area, then review project settings before asking agents to run:

  • Details: project name and description.
  • Agent defaults: runtime, model, reasoning effort, and fast mode.
  • Runners: hosted runner profile and project setup commands.
  • Plan mode: default review behavior for coding sessions.
  • GitHub review bots: which bot-authored pull request feedback can trigger follow-up work.

Use a small first project while you learn the review and approval loop.

Connect repositories

Open the workspace repository area before starting agent work:

  1. Link your personal GitHub account when the app asks for it.
  2. Connect the GitHub App installation for the user or organization that owns the repository.
  3. Register the repository in the workspace catalog.
  4. Bind the repository to the project with the intended access mode and auto-PR policy.

The app blocks repository setup when the GitHub connection is missing, stale, or does not cover the selected repository. Fix that connection in the app, then retry the repository action.

Add context

Use the L0 Nexus area when agents need workspace knowledge beyond the repository checkout. Connectors, sources, indexing status, and data bindings are administered from the app. The public docs describe what those surfaces are for, but the app owns workspace-specific setup and health.

Start reviewable work

Start with a small task that can be inspected easily. Good first tasks are:

  • summarize a repository area and propose a cleanup plan
  • create a small code change behind plan review
  • run QA against a narrow route or feature
  • investigate a failing check and propose the next action

Use the project graph, Kanban, sessions, terminal, task detail, and pull request links to inspect progress. When Labor0 asks for approval or user input, respond from the app so the task can continue with the right workspace and project context.

Expand automation

After the first reviewable task succeeds, expand gradually:

  • use project automation for signed custom webhooks, GitHub signals, or Sentry signals
  • connect messenger bridges when a team wants to invoke Labor0 from Slack, Discord, Microsoft Teams, or Mattermost
  • add local runners only when hosted runners are not enough for the project
  • tighten budget and usage controls before increasing task volume

Next