clink-cliDocsGitHub
Browse documentation
Use Clink / Reference

Reference

Look up the two entry points, operation-specific agent support, tool groups and configuration precedence.

Commands

clink generation-capabilities --json
Inspect generation schemas and family support locally. Add --cli NAME --executable /absolute/path to inspect a specific executable’s identity.
clink allow PATH --cli NAME
Approve an existing directory for the specified CLI. An explicit --yes grants it non-interactively. Native agent trust is managed separately.
clink generate --request-json -
Read one generation request from stdin and return one terminal JSON result.
clink-mcp-server --project PATH
Serve MCP tools over stdio for an explicitly bound workspace.

Agent compatibility

The recorded checks cover exact macOS arm64 binaries, launch recipes and parsers. A different build can be installed and signed in while still being refused. Release evidence and limits.

AgentConsultationNative taskGeneration
Codex 0.166.0AdmittedDisabledExplicit model, schema 2 or 3
Claude Code 2.1.304UnavailableAdmittedExplicit full model ID, schema 2 or 3
Grok Build 1.0.70UnverifiedAdmittedNative default, schema 3
Antigravity 1.4.12UnverifiedAdmittedUnverified, refused
GeminiUnverifiedUnimplementedUnimplemented

MCP tools

All 18 tools are enabled by default. DISABLED_TOOLS can hide optional tools. version and listmodels stay available.

  • Consultation and delegation. chat and clink. The latter also accepts native task actions.
  • Investigation. thinkdeep, codereview, precommit, debug, secaudit, analyze, refactor, testgen.
  • Consultations and search. consensus and apilookup.
  • Local guidance. planner, docgen, tracer, challenge.
  • Discovery. listmodels and version.

Configuration

Clink loads client manifests in the order below. A later definition replaces the entire named client.

  1. Bundled client defaults
  2. Legacy ~/.pal/cli_clients/
  3. User ~/.clink/cli_clients/
  4. Explicitly bound project .clink/cli_clients/
  5. CLI_CLIENTS_CONFIG_PATH

Generation loads operator configuration independently of the request’s project path. See CLI configuration and generation setup.

Results and permissions

An agent’s reported model can be unknown even when its requested model is explicit. Completion confirms final response transport. Check the answer and any file changes independently. Approved roots constrain project and context selection. Native tools retain their configured permissions, and cancellation cannot undo earlier changes.

Read the schema 2 contract, schema 3 contract and security policy for full details.