Labor0 Docs

Concepts

Understand the app model for scope, navigation, task graphs, assistants, sessions, approvals, QA, and credentials.

Labor0 is organized around authenticated product work. The app keeps the important boundaries visible so teams can see where work belongs, who can act, and what needs review.

Scope

Labor0 work is scoped as tenant, workspace, and project.

  • A tenant groups the organization context used to create workspaces.
  • A workspace owns projects, members, repositories, runners, MCP setup, usage views, and settings.
  • A project owns task graphs, Kanban work, project chat, sessions, QA, automation, repositories, and project settings.

The app shows the selected workspace and project in navigation so actions stay attached to the right place.

After you choose a workspace, the primary app areas are:

  • Chat for workspace-level assistant conversations.
  • Projects for browsing projects and creating a project.
  • Repositories for GitHub access, repository registration, and workspace repository inventory.
  • L0 Nexus for knowledge sources, connectors, data bindings, endpoints, and indexing.
  • L0 Tools for workspace authoring-tool MCP connection guidance.
  • Settings for billing, messengers, notifications, members, user groups, tokens, runners, and security.

When you open a project, the project navigation adds Graph, Kanban, Chat, Sessions, Quality, Automation, Repositories, and Settings.

Task graphs and Kanban

A project request can become a task graph. The graph shows planned work, dependencies, waiting states, failures, and follow-up actions. Kanban gives the same active work a list-first view for scanning.

Plan review is the normal way to inspect proposed work before it runs. If a task is blocked, use the app-provided diagnosis, terminal, transcript, retry, reconcile, pull request, or follow-up actions instead of copying raw logs into shared channels.

Assistants and voice

Workspace chat is useful for broad questions across the workspace. Project chat is better when the answer or action should stay tied to one project.

Voice sessions use the same review model as text conversations. The app shows assistant progress, interruptions, and transcript state without requiring users to handle low-level provider details.

Sessions and approvals

Sessions are the execution view for agent work. They can include terminal output, plan review, pending requests, approvals, transcript links, and pull request state.

Some work pauses for human input. Answer those prompts from the app so Labor0 can preserve actor, workspace, project, and task context. For sensitive responses, the app may ask for fresh verification before submitting the answer.

Quality and automation

The Quality area shows QA run history and report detail when a project has QA evidence. Reports can link to artifacts through authorized app flows.

The Automation area lets project owners configure durable event intake. Start with outcome-focused routing prompts: describe what should create work, what should be ignored, and what context a task needs. Keep secrets and private payloads out of prompts.

Messenger bridges

Slack, Discord, Microsoft Teams, and Mattermost bridges let teams invoke Labor0 from collaboration tools. Setup happens in workspace messenger settings:

  1. Install the provider bridge.
  2. Link the provider actor to a Labor0 user.
  3. Bind provider channels to projects.
  4. Use app approvals for graph previews and sensitive follow-up work.

Unlinked users or unbound channels receive guidance instead of silently creating project work.

Credentials and settings

The app separates credential types:

  • User API tokens are created from token settings and are useful for MCP clients and user-scoped API calls.
  • Runner tokens register or run local machines from workspace runner settings.
  • Runtime credentials are write-only workspace runtime credential settings used by agent runtimes.
  • MCP endpoints and setup snippets are copied from L0 Nexus or L0 Tools screens.

Do not store token values in docs, issue comments, screenshots, or checked-in config. Use the app for creation, rotation, and revocation.

Next