Skip to main content

Global Options

Authentication

login

Authenticate with CodeAnt AI via browser-based OAuth.

logout

Sign out and remove stored credentials.

set-token

Store an authentication token for an SCM platform.
Supported remotes: github, gitlab, bitbucket, azure Examples:

set-codeant-api-key

Manually set the CodeAnt AI API key (alternative to codeant login).

get-codeant-api-key

Display the currently stored CodeAnt API key (masked - shows first and last 4 characters).

set-telemetry

Enable or disable usage analytics (PostHog). Events are tied to your CodeAnt API token.

get-telemetry

Show current telemetry status.

Code Scanning

All scanning commands share a common set of options for controlling scan scope and file filtering.

Common Scan Options

These options apply to secrets: Glob Pattern Syntax:
  • * matches any characters except /
  • ** matches any characters including /
  • *.{js,ts} matches multiple extensions (brace expansion is supported)
  • Multiple patterns: --exclude 'test/**,dist/**'

secrets

Scan code for exposed secrets, API keys, and credentials.
Secrets-Specific Options: Confidence Levels: Exit Codes:
  • 0 - No blocking secrets found (or only false positives)
  • 1 - Secrets detected that match the --fail-on threshold
Examples:
Example Output: Secrets found (blocking):
Only false positives (non-blocking):
No secrets:

Findings and application APIs

findings

Query findings available in the CodeAnt AI app, including repository SAST/SCA/IaC results, organization Hotlist findings, anti-patterns, AWS/Azure/GCP cloud-security findings, and pentest reports.
Common entry points:
See Findings for every subcommand, filter, provider-specific scope field, output format, and agent workflow.

hotlist

The existing Hotlist commands remain available for backward compatibility:
codeant findings list/get exposes the same data through the unified namespace.

api request

Call an authenticated CodeAnt application API using a relative endpoint path:
Absolute URLs are rejected, and authentication or X-CodeAnt-CLI-* headers cannot be overridden. Prefer a first-class findings command when one exists.

Analytics

track

Send an analytics event to CodeAnt. Primarily used by integrations (Claude Code skills, CI systems, etc.) to record usage events.
Example:

Agent integration

mcp

Run the CodeAnt MCP server over stdio. MCP clients such as Claude Code, Claude Desktop, Cursor, and VS Code start this command themselves. You don’t normally run it by hand.
The server is read-only by default. Set CODEANT_READ_ONLY=0 in its environment to add the write tools. See MCP Server for client setup and the MCP tool reference for every tool.

Configuration

set-base-url

Set a custom API base URL for self-hosted CodeAnt deployments.
Example:

get-base-url

Display the current API base URL and where it’s configured.

set-dashboard-url

Set the dashboard URL (the address of your CodeAnt AI web app) that codeant login and the MCP codeant_login tool open. On a self-hosted instance, set it if sign-in fails with Could not determine the dashboard URL.
Example:

get-dashboard-url

Display the dashboard URL that sign-in will use and where it comes from: the CODEANT_DASHBOARD_URL environment variable, the saved setting, or auto-detection from the API base URL.

remove-dashboard-url

Remove the saved dashboard URL. The next sign-in detects it from the API base URL again.

Configuration File

All configuration is stored in ~/.codeant/config.json. Configuration Keys: Environment Variables: Priority Order:
  1. Environment variables (highest)
  2. Platform CLI tools (gh, glab)
  3. Config file (~/.codeant/config.json)
  4. Default values