Available commands
CLI commands for installing, operating, and maintaining Bito's AI Architect.
Quick reference for bitoarch CLI commands used to configure and manage Bito's AI Architect.
Lifecycle
Commands used to control the lifecycle of AI Architect.
bitoarch start
For recovery if AI Architect services stopped/killed due to system issues
bitoarch stop
Stop all services (keeps data)
bitoarch restart [--force]
Restart services. --force reloads env and recreates containers
bitoarch logs [service]
Tail service logs (-f). All services if service omitted
bitoarch update
Refresh service images per versions/service-versions.json
bitoarch reset
Remove services, volumes, and config. Keeps install directory
bitoarch uninstall
Full removal (services + install directory)
Examples:
bitoarch restart --force # reload env + recreate containers
bitoarch logs cis-provider # tail one serviceAI Architect management commands
Use these bitoarch commands to manage AI Architect.
Core operations
bitoarch index-repos [--only-new-repos]
Trigger workspace repository indexing. Use --only-new-repos to index only newly added repositories
bitoarch index-repos --only-new-repos
bitoarch index-status [--raw] [--output json]
Check indexing status. --raw dumps the full API response; --output json emits machine-readable JSON
View progress and state
bitoarch pause-indexing
Pause ongoing indexing process
bitoarch pause-indexing
bitoarch resume-indexing
Resume paused indexing process
bitoarch resume-indexing
bitoarch stop-indexing
Stop indexing completely
bitoarch stop-indexing
bitoarch index-repo-list [--status <active\|all>] [--limit <N>]
List indexed repositories
bitoarch index-repo-list --status active
bitoarch show-config
Show current indexing configuration
bitoarch show-config --raw
bitoarch create-index-scheduler
Create scheduled indexing tasks
bitoarch update-index-scheduler
Update existing scheduled indexing tasks
Examples:
Repository management
bitoarch add-repo <namespace>
Add single repository
bitoarch add-repo myorg/myrepo
bitoarch remove-repo <namespace>
Remove repository
bitoarch remove-repo myorg/myrepo
bitoarch add-repos [file]
Load repos from YAML. Uses .bitoarch-config.yaml if file omitted
bitoarch add-repos
bitoarch update-repos [file]
Update repos from YAML. Uses .bitoarch-config.yaml if file omitted
bitoarch update-repos
bitoarch repo-info <name> [--dependencies]
Show repository details (add --dependencies to include incoming/outgoing deps)
bitoarch repo-info myrepo --dependencies
bitoarch fetch-repo-list [--force-load]
Sync repo list from your git provider. --force-load ignores local cache
bitoarch fetch-repo-list
Examples:
Service operations
bitoarch status
View all services status
Docker ps-like output
bitoarch health
Check health of all services
bitoarch health --verbose
bitoarch info
Get platform information
Version, ports, resources
Examples:
Configuration
bitoarch update-api-key
Update Bito API key
Interactive or with --api-key [--restart] flag
bitoarch update-git-creds
Update Git provider credentials
Interactive or with --provider <p> --token <t> [--restart] flags
bitoarch update-llm-keys
Update LLM API keys
Interactive prompt
bitoarch rotate-mcp-token [<new-token>]
Rotate MCP access token. Omit <new-token> to auto-generate
bitoarch rotate-mcp-token <new-token>
bitoarch config path [env\|repos\|llm]
Print the absolute path of a config file (default: env)
bitoarch config edit [env\|repos\|llm]
Open a config file in $EDITOR (default: env)
Config file types:
env
.env-bitoarch
Main environment config (ports, credentials, secrets)
repos
.bitoarch-config.yaml
Repository list
llm
.env-llm-bitoarch
Custom LLM provider configuration
Examples:
MCP operations
bitoarch mcp-test
End-to-end MCP connectivity check
Verify server connectivity
bitoarch mcp-tools [--details] [--summary] [--output <file>]
List available MCP tools
bitoarch mcp-tools --details
bitoarch mcp-capabilities [--output <file>]
Show MCP server capabilities
bitoarch mcp-capabilities --output caps.json
bitoarch mcp-info
Show MCP configuration
Show MCP URL, access token, and active auth mode
bitoarch mcp-tool-info <name>
Show details for one MCP tool
bitoarch mcp-tool-info search_code
Examples:
SSO authentication
SSO is optional and disabled by default (bearer-token auth). When enabled, bitoarch mcp-info reflects the active auth mode.
bitoarch sso setup
This command will guide you through the SSO configuration process, including choosing between Enterprise IdP and Bito authentication
bitoarch sso status
Displays the current SSO configuration and IdP connection status
bitoarch sso enable
Re-enable SSO after it has been temporarily disabled
bitoarch sso disable
You can disable SSO either temporarily or permanently. Choose temporary to turn off SSO authentication but preserve IdP configuration (can re-enable with bitoarch sso enable), or permanent to remove IdP configuration entirely (requires bitoarch sso setup to reconfigure)
bitoarch sso rotate-key
Rotate SSO management key for security purposes. Important: After rotating the key, SSO services will restart automatically. Active sessions may need to re-authenticate
Auth modes:
Bearer Token
Default — static MCP access token (SSO disabled)
Bito
SSO via Bito — no external IdP required
Enterprise IdP
SSO via your SAML/OIDC provider (Okta, Azure AD, etc.)
Diagnostics
bitoarch diagnose
Run a live health sweep across all services
bitoarch diagnose --verbose
bitoarch diagnose --bundle
Collect a full diagnostics bundle into a .tar.gz to share with support
bitoarch diagnose --bundle
Flags:
--verbose, -v
Show URLs, ports, and detail on failures (live sweep only)
--section <name>
Run one section only: prereqs, install, filesystem, config, services, connectivity, cert
--bundle
Produce a shareable .tar.gz support bundle
Examples:
Output options
Add these flags to any command:
--format json
JSON output
For automation/scripts
--raw
Show full API response
For debugging
--output json
Filtered JSON output
For index-status
--help
Show command help
Get usage information
Common workflows
Initial setup
Daily operations
Adding new repositories
Credential rotation
Tear-down
Troubleshooting
Getting help
bitoarch --help | -h
Top-level help with all commands
bitoarch <command> --help
Command-specific usage and flags
Examples:
Environment
Configuration is loaded from .env-bitoarch file. (path: bitoarch config path env)
Key variables:
BITO_API_KEY
Bito authentication key
GIT_PROVIDER
Git provider (github, gitlab, bitbucket)
GIT_ACCESS_TOKEN
Git personal access token
BITO_MCP_ACCESS_TOKEN
MCP server access token
CIS_PROVIDER_EXTERNAL_PORT
MCP server port (default 8080 for k8s)
CIS_MANAGER_EXTERNAL_PORT
Manager API port
CIS_CONFIG_EXTERNAL_PORT
Config API port
CIS_TRACKER_EXTERNAL_PORT
Tracker API port
MYSQL_EXTERNAL_PORT
MySQL external port
Version
Check CLI version:
Last updated