clavue-v1 weekly downloads statistics

Clavue v1 (clavue-v1)

clavue-v1 is an execution-first AI coding CLI built on the stable v8.9.1 engine with a lightweight four-slot multi-model combo layer (main / light / plan / review). It keeps the terminal as the control surface, uses direct repo tools for inspection/editing/verification, treats API providers as configurable routes, and passes slot models through verbatim — no allowlist, no family filter. Combo is opt-in via CLAVUE_COMBO_* env vars; with combo off, behavior is byte-identical to v8.9.1.

Product Philosophy

Clavue is built around a simple operating model: the user owns the workflow, the CLI owns the execution loop, and providers are replaceable routes.

• Execution first: every feature should help inspect, edit, run, verify, or recover real software work.
• Terminal-owned workflow: Clavue stays close to files, commands, diffs, permissions, and project state instead of becoming a detached chat surface.
• Provider control, not provider identity: official login, custom API profiles, and compatible gateways are routing choices. The product identity remains Clavue.
• Native coding workflows: direct file tools, shell execution, task tracking, worktrees, skills, and MCP resources are part of the runtime loop.
• Fast first run: install, choose an API configuration mode, paste URL/key or token, set model slots if needed, then start coding.
• Visible configuration: /provider and clavue-v1 provider expose the active route, saved profiles, credential mode, model slots, validation, repair, and current environment state.
• Practical autonomy: permission setup should make development smoother while still being explicit about trust boundaries.
• Continuity over spectacle: long-context recovery, compaction, /team, and /retro exist to keep work moving, not to add noise.

What Clavue Is

• An execution-first AI coding CLI for inspecting, editing, running, verifying, and delivering code from the terminal.
• A native coding runtime with direct repo tools, shell execution, permissions, tasks, worktrees, skills, MCP resources, and resumable sessions.
• A provider control center for custom API URLs, API keys, auth tokens, model slots, route validation, and repair.
• A fast onboarding path for users who want official login, custom API configuration, CCR-compatible proxy routing, or manual setup later.
• A runtime that can use compatible providers and gateways without pretending those providers are the product.
• A set of native workflows for coding, review, recovery, team inspection, and retrospective improvement.

Core Surfaces

Base contract (tool loop, evidence-gated /goal, multi-worker, print admit, session phases, permissions) vs what skills extend: study/00-capability-scope.md. Recipes: study/08-best-practices.md. Installed surface: clavue-v1 capabilities (--json for machines).

Canonical primary command surfaces:

• /help: browse available commands and custom command sources.
• /init: create or refresh generated project rule files: clavue.md, AGENTS.md, and compatibility CLAUDE.md.
• /provider: configure, switch, validate, repair, copy, edit, delete, or save provider profiles.
• /permissions (/approvals compatibility alias): set the default permission mode so trusted development environments can run with less friction; use /permissions autonomous for an opt-in high-autonomy local development lane.
• /team: inspect local team readiness, active team config, and capability state.
• /goal: run a durable, evidence-gated goal loop with a persistent ledger and a bounded auto-continuation budget.
• /retro: run a multi-round repo retrospective and upgrade loop.
• /tasks: inspect task-board state for long-running work.
• /resume: continue saved sessions.
• /doctor, /login, /logout, /mcp, /model, /plugin, and /status: primary setup, routing, and diagnostics flows.
• clavue land (shell, not a slash command): re-run tests on matching worktree tips, then serially fast-forward or rebase+fast-forward them onto main. --push runs only after every selected tip landed. Holds the main task lease; tip leases do not block it.

Secondary surfaces such as /review, /compact, /config, /memory, /theme, /usage, /cost, /vim, and /parallel remain available for focused workflows. /parallel launches Agent workers only when you type it. Saying 「多开几个 clavue」 does not run it; the lead session spawns Agent and Team workers instead. /usage and /cost show this session's tokens and, on official cloud after the first request, membership points. USD on official SKUs is an estimate — billing is in points. Compatibility aliases are documented only when they are part of a canonical flow; internal, hidden, disabled stub, and experimental commands are not public defaults. Long-context recovery includes proactive compaction plus reactive overflow recovery for long-running work.

Study Guide

For full user-facing usage, start in study/README.md: 00 capability scope through 08 best practices. After an upgrade, run clavue-v1 capabilities (or --json) before reading release notes.

For provider and model routing setup, see Clavue Provider And Model Best Practices. For which Grok id is chat versus coding on ttqq/ttgg, see ttgg / ttqq Grok 模型用法.

Host integration (imux, tmux, IDE, Agent Chat)

Other software should spawn clavue-v1, not embed a second agent loop. Full contract: Host integration. Third-party discovery, acpx recipes, and the ACP/MCP/A2A/PTY split: ACP / acpx interoperability.…