CLI Reference
Copy page
Complete reference for the Inkeep CLI commands
Overview
The Inkeep CLI is the primary tool for interacting with the Inkeep Agent Framework. It allows you to push Agent configurations and interact with your multi-agent system.
Installation
Global Options
All commands support the following global options:
--version- Display CLI version--help- Display help for a command
Commands
inkeep add
Add a new template to the project
Add project templates or MCP server templates to your Inkeep project. Templates provide pre-configured setups for common use cases.
Arguments:
template- Template name to add
Options:
--project <template>- Project template to add--mcp <template>- MCP template to add--target-path <path>- Target path to add the template to--local-prefix <path_prefix>- Use local templates from the given path prefix--config <path>- Path to configuration file
Examples:
Add a project template
Add an MCP server template
Add template to specific path
See also: init
inkeep config
Manage Inkeep configuration
Manage your Inkeep configuration file. Get, set, or list configuration values.
Subcommands:
inkeep config getinkeep config setinkeep config list
inkeep config get
Get configuration value(s)
Get a specific configuration value or all values if no key is provided.
Arguments:
key- Configuration key to get (optional, shows all if omitted)
Options:
--config <path>- Path to configuration file
Examples:
Get all config values
Get specific config value
inkeep config set
Set a configuration value
Set a configuration value in the config file.
Arguments:
key(required) - Configuration key to setvalue(required) - Value to set
Options:
--config <path>- Path to configuration file
Examples:
Set tenant ID
inkeep config list
List all configuration values
Display all configuration values from the config file.
Options:
--config <path>- Path to configuration file
Examples:
List all config values
See also: init, profile
inkeep dev
Start the Inkeep dashboard server
Start the Inkeep dashboard server for local development. The dashboard provides a visual interface for testing and debugging your agents.
Options:
--port <port>- Port to run the server on (default: 3000)--host <host>- Host to bind the server to (default: localhost)--build- Build the Dashboard UI for production--export- Export the Next.js project source files--output-dir <dir>- Output directory for build files (default: ./inkeep-dev)--path- Output the path to the Dashboard UI--open-browser- Open the browser
Examples:
Start dashboard on default port
Start on custom port
Build for production
Start and open browser
See also: push, pull
inkeep init
Initialize a new Inkeep project (runs cloud onboarding wizard by default)
Initialize a new Inkeep configuration file in your project. By default, runs the cloud onboarding wizard. Use --local for self-hosted mode.
Arguments:
path- Directory path to initialize the project in
Options:
--local- Use local/self-hosted mode instead of cloud onboarding--no-interactive- Skip interactive prompts (default: true)--config <path>- Path to use as template for new configuration
Examples:
Interactive initialization
Initialize in specific directory
Non-interactive mode
Use specific config as template
Local/self-hosted mode
See also: push, pull, config
inkeep list-agent
List all available agents for a specific project
List all agents configured for a specific project. Requires a project ID to be specified.
Options:
--project <project-id>(required) - Project ID to list agents for--tenant-id <tenant-id>- Tenant ID--agents-manage-api-url <url>- Agents manage API URL--config <path>- Path to configuration file
Examples:
List agents for a project
See also: push, pull
inkeep login
Authenticate with Inkeep Cloud
Authenticate with Inkeep Cloud using browser-based OAuth. Credentials are stored securely in your profile.
Options:
--profile <name>- Profile to authenticate (defaults to active profile)
Examples:
Login to active profile
Login to specific profile
See also: logout, status, profile
inkeep logout
Log out of Inkeep Cloud
Log out of Inkeep Cloud and remove stored credentials from your profile.
Options:
--profile <name>- Profile to log out (defaults to active profile)
Examples:
Logout from active profile
Logout from specific profile
See also: login, status, profile
inkeep profile
Manage CLI profiles for connecting to different remotes
Manage named CLI profiles for multiple remotes, credentials, and environments. Profiles are stored in ~/.inkeep/profiles.yaml. A default 'cloud' profile points to hosted endpoints.
Examples:
Create a local profile and switch to it
Subcommands:
inkeep profile listinkeep profile addinkeep profile useinkeep profile currentinkeep profile remove
inkeep profile list
List all profiles
Display all configured profiles and indicate the currently active profile.
Examples:
List all profiles
inkeep profile add
Add a new profile
Add a new named profile. If no name is provided, you will be prompted to enter one.
Arguments:
name- Name for the new profile
Examples:
Add a new profile interactively
Add a named profile
inkeep profile use
Set the active profile
Set a profile as the currently active profile. All subsequent commands will use this profile.
Arguments:
name(required) - Profile name to activate
Examples:
Switch to staging profile
inkeep profile current
Display the active profile details
Display detailed information about the currently active profile including remote URLs and authentication state.
Examples:
Show current profile
inkeep profile remove
Remove a profile
Remove a named profile. Cannot remove the currently active profile.
Arguments:
name(required) - Profile name to remove
Examples:
Remove staging profile
See also: login, logout, status
inkeep pull
Pull project configuration with clean, efficient code generation
Pull project configuration from the server and generate local TypeScript files. This command fetches your Agent configurations and creates well-structured code that can be edited and pushed back.
Options:
--project <project-id>- Project ID to pull (or path to project directory). If in project directory, validates against local project ID.--config <path>- Path to configuration file--profile <name>- Profile to use for remote URLs and authentication--env <environment>- Environment file to generate (development, staging, production). Defaults to development--json- Output project data as JSON instead of generating files--debug- Enable debug logging--verbose- Enable verbose logging--force- Force regeneration even if no changes detected--introspect- Completely regenerate all files from scratch (no comparison needed)--all- Pull all projects for current tenant--tag <tag>- Use tagged config file (e.g., --tag prod loads prod.__inkeep.config.ts__)--quiet- Suppress profile/config logging
Examples:
Pull current project
Pull specific project
Pull all projects for tenant
Force regeneration of all files
Output as JSON
See also: push, init
inkeep push
Push a project configuration to the backend
Push a project containing Agent configurations to your server. This command deploys your entire multi-agent project, including all Agents, Sub Agents, and tools. The most common workflow is to run `inkeep push` from inside a project directory. A project directory is identified by having an `index.ts` file that exports a project object (with `__type = "project"`).
Options:
--project <project-id>- Project ID or path to project directory--config <path>- Path to configuration file--profile <name>- Profile to use for remote URLs and authentication--tenant-id <id>- Override tenant ID--agents-manage-api-url <url>- Override agents manage API URL--agents-run-api-url <url>- Override agents run API URL--env <environment>- Environment to use for credential resolution (e.g., development, production)--json- Generate project data JSON file instead of pushing to backend--all- Push all projects found in current directory tree--tag <tag>- Use tagged config file (e.g., --tag prod loads prod.__inkeep.config.ts__)--quiet- Suppress profile/config logging
Examples:
Push project from current directory
Push specific project directory
Push all projects in current directory tree
Push with development environment credentials
Generate project JSON without pushing
Use a named profile
See also: pull, init, config
inkeep status
Show current profile, authentication state, and remote URLs
Display the current profile configuration including authentication state, remote API URLs, and tenant information.
Options:
--profile <name>- Profile to show status for (defaults to active profile)
Examples:
Show status for active profile
Show status for specific profile
See also: login, logout, profile, whoami
inkeep update
Update @inkeep/agents-cli to the latest version
Check for and install updates to the Inkeep CLI. Use --check to see if updates are available without installing.
Options:
--check- Check for updates without installing--force- Force update even if already on latest version
Examples:
Update to latest version
Check for updates
Force reinstall
inkeep whoami
Display current authentication status (alias for status)
Display current authentication status. This is an alias for the status command.
Examples:
Show current auth status
See also: status, login, profile
Configuration File
The CLI uses a configuration file (typically inkeep.config.ts) to store settings:
Configuration Priority
Effective resolution order:
- Command-line flags (highest)
- Environment variables (override config values)
inkeep.config.tsvalues
Environment Variables
The CLI and SDK respect the following environment variables:
| Variable | Description |
|---|---|
INKEEP_TENANT_ID | Tenant identifier |
INKEEP_AGENTS_MANAGE_API_URL | Management API base URL |
INKEEP_AGENTS_RUN_API_URL | Run API base URL |
INKEEP_ENV | Environment name for credentials loading during inkeep push |
INKEEP_AGENTS_MANAGE_API_BYPASS_SECRET | Optional bearer for Manage API (advanced) |
INKEEP_AGENTS_RUN_API_BYPASS_SECRET | Optional bearer for Run API (advanced) |
Troubleshooting
Project Not Found
- Projects are automatically managed based on your tenantId
inkeep pushwill create resources as needed
Getting Help
For additional help with any command:
For issues or feature requests, visit: GitHub Issues