Quickstart

Goal#

The first-session goal is simple: AgentLint is installed in one real repo, AgentChute receives a safe verification event, and the dashboard shows agent, decision, rule or policy source, and delivery status.

One-command setup#

Use the CLI onboarding flow from the repo you want to observe. It detects supported coding agents, installs or repairs hooks, persists the AgentChute key, and sends a safe test event.

agentlint login
agentlint onboard --yes
agentlint test --flush

Expected result#

• 01Codex, Claude Code, Cursor, Gemini, or another connected agent appears in the dashboard.
• 02The recent-events table shows a safe test event.
• 03The setup-health panel reports automatic uploads and queue health.
• 04AgentLint hooks keep working even if AgentChute is unavailable.

Manual fallback#

If browser pairing is unavailable, create a key in the dashboard and pass it directly to the onboarding command.

agentlint onboard --team-key "$AGENTCHUTE_LICENSE_KEY" --api-url "$AGENTCHUTE_API_URL" --yes
agentlint test --flush