> For the complete documentation index, see [llms.txt](https://docs.locusai.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.locusai.dev/core-strengths/overview.md).

# Built-In Orchestration Tools

Locus adds an operational toolchain on top of provider CLIs (Claude/Codex): planning, GitHub-native execution, review loops, status visibility, logging, sandbox lifecycle management, and package extensibility.

## Why Built-In Tools (vs Raw Provider CLIs)

Raw provider CLIs can generate code, but they do not natively manage your GitHub workflow end to end.

Locus built-in tools add:

* GitHub task lifecycle control (`issue`, `sprint`, `plan`, `run`)
* Delivery automation (`autoLabel`, `autoPR`, `run --resume`)
* Structured quality loops (`review`, `iterate`)
* Operational visibility (`status`, `logs`, `artifacts`)

## Tool Inventory

### 1) Setup and Configuration

| Tool                                         | Purpose                                                             | Example                                   |
| -------------------------------------------- | ------------------------------------------------------------------- | ----------------------------------------- |
| [`locus init`](/cli-reference/init.md)       | Initialize `.locus/`, verify `gh`, and seed label schema            | `locus init`                              |
| [`locus config`](/cli-reference/config.md)   | Read/write project settings (model, automation, execution behavior) | `locus config set ai.model gpt-5.3-codex` |
| [`locus upgrade`](/cli-reference/upgrade.md) | Check and install newer CLI versions                                | `locus upgrade --check`                   |

### 2) Work Modeling in GitHub

| Tool                                       | Purpose                                                     | Example                                                                                            |
| ------------------------------------------ | ----------------------------------------------------------- | -------------------------------------------------------------------------------------------------- |
| [`locus issue`](/cli-reference/issue.md)   | Create/manage GitHub issues as execution units              | `locus issue create "Add webhook signature validation" --sprint "Sprint 8"`                        |
| [`locus sprint`](/cli-reference/sprint.md) | Create/activate/manage sprint milestones                    | `locus sprint active "Sprint 8"`                                                                   |
| [`locus plan`](/cli-reference/plan.md)     | Generate plan files, review, and approve into GitHub issues | `locus plan "Build billing retries" --sprint "Sprint 8"` then `locus plan approve <id> "Sprint 8"` |

### 3) Execution, Review, and Iteration

| Tool                                         | Purpose                                          | Example                 |
| -------------------------------------------- | ------------------------------------------------ | ----------------------- |
| [`locus run`](/cli-reference/run.md)         | Execute active sprint or standalone issue set    | `locus run --resume`    |
| [`locus review`](/cli-reference/review.md)   | AI review for open `agent:managed` PRs           | `locus review`          |
| [`locus iterate`](/cli-reference/iterate.md) | Apply PR feedback in loop                        | `locus iterate --pr 42` |
| [`locus status`](/cli-reference/status.md)   | Operational dashboard for sprint/issues/PRs      | `locus status`          |
| [`locus logs`](/cli-reference/logs.md)       | Tail and inspect run logs for failures/debugging | `locus logs --follow`   |

### 4) Interactive and Analysis Tools

| Tool                                         | Purpose                                                           | Example                                                                   |
| -------------------------------------------- | ----------------------------------------------------------------- | ------------------------------------------------------------------------- |
| [`locus exec`](/cli-reference/exec.md)       | Interactive or one-shot coding session                            | `locus exec "Add retry guard to webhook handler"`                         |
| [`locus discuss`](/cli-reference/discuss.md) | Architecture discussion and planning prompts                      | `locus discuss "Should we split webhook processing into a queue worker?"` |
| [`locus memory`](/cli-reference/memory.md)   | List, search, and manage structured project memory                | `locus memory list --category architecture`                               |
| [`locus commit`](/cli-reference/commit.md)   | AI-powered commit message generation from staged changes          | `locus commit --dry-run`                                                  |
| `locus artifacts`                            | Inspect and convert AI-generated artifacts in `.locus/artifacts/` | `locus artifacts plan webhook-reliability-prd`                            |

### 5) Skills

| Tool                   | Purpose                                     | Example                            |
| ---------------------- | ------------------------------------------- | ---------------------------------- |
| `locus skills list`    | List available agent skills from registry   | `locus skills list`                |
| `locus skills search`  | Search skills by name, description, or tags | `locus skills search "deploy"`     |
| `locus skills install` | Install a skill from the registry           | `locus skills install code-review` |
| `locus skills remove`  | Remove an installed skill                   | `locus skills remove code-review`  |
| `locus skills update`  | Update installed skill(s) from registry     | `locus skills update`              |
| `locus skills info`    | Show skill metadata and install status      | `locus skills info code-review`    |

### 6) MCP Server Management

| Tool                                            | Purpose                                  | Example                                                                             |
| ----------------------------------------------- | ---------------------------------------- | ----------------------------------------------------------------------------------- |
| [`locus mcp add`](/cli-reference/mcp.md)        | Add a server from a built-in template    | `locus mcp add github`                                                              |
| [`locus mcp add-custom`](/cli-reference/mcp.md) | Add a custom MCP server                  | `locus mcp add-custom --name api --transport stdio --command node --args server.js` |
| [`locus mcp remove`](/cli-reference/mcp.md)     | Remove an MCP server                     | `locus mcp remove mydb`                                                             |
| [`locus mcp list`](/cli-reference/mcp.md)       | List configured servers                  | `locus mcp list --json`                                                             |
| [`locus mcp sync`](/cli-reference/mcp.md)       | Sync config to provider-specific formats | `locus mcp sync --provider claude`                                                  |
| [`locus mcp test`](/cli-reference/mcp.md)       | Test an MCP server connection            | `locus mcp test mydb`                                                               |
| [`locus mcp status`](/cli-reference/mcp.md)     | Show config and provider sync status     | `locus mcp status`                                                                  |
| [`locus mcp enable`](/cli-reference/mcp.md)     | Enable a server                          | `locus mcp enable mydb`                                                             |
| [`locus mcp disable`](/cli-reference/mcp.md)    | Disable a server                         | `locus mcp disable mydb`                                                            |

### 7) Package Ecosystem Tools

| Tool              | Purpose                                  | Example                    |
| ----------------- | ---------------------------------------- | -------------------------- |
| `locus install`   | Install community package from npm       | `locus install telegram`   |
| `locus uninstall` | Remove installed package                 | `locus uninstall telegram` |
| `locus packages`  | List installed packages / check outdated | `locus packages outdated`  |
| `locus pkg`       | Run package-provided commands            | `locus pkg telegram start` |

### 8) Sandbox Management Tools

| Tool                                         | Purpose                                                                                   | Example                                      |
| -------------------------------------------- | ----------------------------------------------------------------------------------------- | -------------------------------------------- |
| [`locus sandbox`](/cli-reference/sandbox.md) | Create/manage provider sandboxes, auth sessions, package installs, shell access, and logs | `locus sandbox install bun --provider codex` |

## Practical Workflows Where Built-In Tools Win

### Workflow A: Issue-to-PR Delivery with Recovery

```bash
locus sprint active "Sprint 8"
locus run
locus review
locus iterate --sprint
locus run --resume
```

Why this beats raw provider CLI usage:

* Keeps task state in GitHub labels/issues/PRs
* Recovers from interruption without re-running completed tasks
* Preserves one team workflow across Claude/Codex model switching

### Workflow B: Plan Approval Before Execution

```bash
locus plan "Add SSO login and role-based access"
locus plan list
locus plan show <id>
locus plan approve <id> "Sprint 9"
locus run
```

Why this beats raw provider CLI usage:

* Separates planning from execution with an approval gate
* Converts approved plan into ordered GitHub work automatically
* Keeps execution order explicit via `order:N` labels

## Related Docs

* [Auto-Approval Mode](/core-strengths/auto-approval-mode.md)
* [Execution Model (Technical)](/workflow-deep-dives/execution-model.md)
* [GitHub-Native Workflows](/workflow-deep-dives/github-native-workflows.md)
* [Sandboxing Setup (Docker-First)](/getting-started/sandboxing-setup.md)
* [Unified Interface Across AI Clients](/core-strengths/unified-interface.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.locusai.dev/core-strengths/overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.