Skip to main content
The outlit onboard command is the first command for coding agents. It bootstraps CLI auth, installs the outlit skill for the selected agent, checks integration setup readiness, and prints next actions. outlit setup remains available when you only want to install skills. It does not configure MCP clients. If you want Cursor, VS Code, Claude, or another MCP client, use the direct MCP Integration guide instead.

Supported Agents

Run onboard for the agent you use, or run outlit setup --yes to detect installed agents automatically when you only need skills.

Onboarding

If no API key is available, onboard starts the browser approval flow outside CI and stores the approved CLI key. It then validates the key, installs the Outlit skill, checks integration capabilities/status, and returns next commands such as outlit integrations setup <provider> --json. onboard does not connect third-party integrations by itself. Use outlit integrations capabilities --json, then outlit integrations setup <provider> --json for auth or credentials, and follow-up commands like outlit integrations setup hubspot mappings --json or outlit integrations setup pylon webhooks --json when capabilities list required post-connect steps.

Auto-Setup

Detect installed coding agents and install outlit for all of them:
Without --yes, the CLI lists detected agents before installing.

JSON Output

Interactive Skills Installer

Use this when you want to pick agents manually or optionally add outlit-sdk:
This opens the interactive skills add flow scoped to github.com/OutlitAI/outlit-agent-skills.

Diagnostics

The doctor command checks your CLI auth plus coding-agent skill installs:

Checks Performed

Example Output

JSON Output

Filter for failures:

Exit Code

doctor exits with code 1 if any check fails, which makes it useful in CI: