> For the complete documentation index, see [llms.txt](https://docs.bito.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bito.ai/ai-architect/installation/install-ai-architect-self-hosted/cli-command-reference.md).

# CLI command reference

CLI commands for installing, operating, and maintaining Bito's AI Architect.

Complete reference for the `bitoarch` command-line interface used to manage a self-hosted deployment. Run `bitoarch <command> --help` for command-specific options.

{% hint style="info" %}
Commands marked **Standalone-only** exist only on Standalone deployments. They are hidden and refuse to run on Enterprise.
{% endhint %}

## Status

| `status`                             | Show the status of all services                                                 |
| ------------------------------------ | ------------------------------------------------------------------------------- |
| `health [--verbose]`                 | Check health of all services (per-service detail)                               |
| `info`                               | Show platform information (version, ports)                                      |
| `diagnose [--verbose]`               | Diagnostic sweep, pass/warn/fail per section                                    |
| `diagnose --section <name>`          | One section: prereqs, install, filesystem, config, services, connectivity, cert |
| `diagnose --bundle [--output <dir>]` | Redacted `.tar.gz` for support (→ `~/.bitoarch/diagnostics/`)                   |

## Lifecycle

<table data-header-hidden data-search="false"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><code>start</code></td><td>Start stopped services (idempotent)</td></tr><tr><td><code>stop</code></td><td>Stop all services (keeps data)</td></tr><tr><td><code>restart [--force]</code></td><td>Restart services (<code>--force</code> reloads env and recreates containers)</td></tr><tr><td><code>logs [service]</code></td><td>Tail service logs (<code>-f</code> to follow, all services if omitted)</td></tr><tr><td><code>upgrade [--version=&#x3C;ver>]</code></td><td>Upgrade the platform, blue/green (latest by default, data preserved)</td></tr><tr><td><code>reset</code></td><td>Remove services, volumes, and configuration (keeps the install directory)</td></tr><tr><td><code>uninstall</code></td><td>Full removal (services + install directory)</td></tr></tbody></table>

## Repositories

| `add-repo <ns>` / `remove-repo <ns>` | Add / remove a repository by namespace                                |
| ------------------------------------ | --------------------------------------------------------------------- |
| `add-repos` / `update-repos`         | Apply / update the repository list (edit it with `config edit repos`) |
| `repo-info <name>`                   | Show repository details                                               |
| `fetch-repo-list [--force-load]`     | Sync the repository list from the Git provider                        |

## Indexing

| `show-config [--raw]`                               | Show current indexing configuration (`--raw` = full resolved config) |
| --------------------------------------------------- | -------------------------------------------------------------------- |
| `index-repos [--only-new-repos]`                    | Trigger workspace repository indexing                                |
| `index-status`                                      | Check indexing status (`--raw` for full payload)                     |
| `index-repo-list`                                   | List all indexed repositories                                        |
| `stop-indexing`                                     | Stop indexing completely                                             |
| `create-index-scheduler` / `update-index-scheduler` | Manage scheduled indexing                                            |

## Configuration

| `update-api-key`                 | Update the Bito API key                                 |
| -------------------------------- | ------------------------------------------------------- |
| `update-git-creds`               | Update Git provider credentials                         |
| `update-llm-config`              | Update custom LLM provider configuration                |
| `rotate-mcp-token [<new-token>]` | Rotate the MCP access token (auto-generates if omitted) |
| `config path [env\|repos\|llm]`  | Print a configuration file path                         |
| `config edit [env\|repos\|llm]`  | Open a configuration file in `$EDITOR`                  |

## MCP

| `mcp-info`                           | Show MCP configuration (URL, token, auth mode) |
| ------------------------------------ | ---------------------------------------------- |
| `mcp-test`                           | Test the MCP connection end-to-end             |
| `mcp-tools` / `mcp-tool-info <name>` | List tools / show a tool's details             |
| `mcp-capabilities`                   | Show MCP server capabilities                   |

## SSO (Enterprise only)

| `sso setup`                  | Configure SSO (Enterprise IdP or Bito)   |
| ---------------------------- | ---------------------------------------- |
| `sso status`                 | Check SSO configuration and verification |
| `sso enable` / `sso disable` | Re-enable / disable SSO                  |
| `sso rotate-key`             | Rotate SSO keys                          |

## Insights (optional)

| `insights config` / `insights status`                  | Show configuration / workflow status     |
| ------------------------------------------------------ | ---------------------------------------- |
| `insights run [--force]`                               | Run analysis (`--force` re-analyzes all) |
| `insights enable\|disable [git\|ticket-tracker\|docs]` | Toggle an insights feature               |
| `insights tracker-projects [action] [KEY …]`           | Manage project keys                      |
| `insights set-lookback [git\|ticket-tracker]`          | Set lookback days                        |

## Standalone-only

| `mcp-install [--email <addr>]` | Register the local MCP with detected AI coding agents                  |
| ------------------------------ | ---------------------------------------------------------------------- |
| `mcp-uninstall`                | Deregister MCP from AI coding agents                                   |
| `mcp-cert status`              | Certificate verdict, days remaining, scheduler state                   |
| `mcp-cert renew [--check]`     | Re-issue the certificate (`--check` = only if expiring within 60 days) |
| `mcp-cert schedule [HH:MM]`    | Show or set the daily auto-renew time                                  |


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.bito.ai/ai-architect/installation/install-ai-architect-self-hosted/cli-command-reference.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.