Syncs docs to parent release **v2026.831.1** (cumulative from
`v2026.824.1`, via merge-base `664052f`). Authored fresh against the
release tag; every claim verified at the tag.
## What changed
**New**
- **Kimi Code adapter** (`kimi_local`) — new reference page, wired into
the adapters overview, nav, and anchor-map source mapping.
**Reference**
- **Env vars** — `PAPERCLIP_WORKSPACE_REAPER_COOLDOWN_DAYS`, opt-in
`SENTRY_DSN`, and the operator controls `PAPERCLIP_HIDDEN_SETTINGS` /
`PAPERCLIP_SETTING_DEFAULTS`.
- **Instance Settings** — new "operator controls for hosted deployments"
section (hide surfaces / override defaults).
- **Node.js floor → 24.11.0** across installation, setup,
local-development, plugin dev, Modal, and the getting-started/terminal
guides.
- **Grok adapter** — `permissionMode` no longer defaults to `dontAsk`;
when unset no flag is passed, and `--always-approve` is the unattended
policy.
- **CLI `agent`** — Kimi skills install path (`~/.kimi-code/skills`) +
`KIMI_CODE_HOME`.
**Guides**
- **Onboarding** — rebuilt around a single-card wizard that opens on
creating your agent; the mission step is gone, the goal is set
afterward.
- **Settings unification** — Invites folded into a Members tab, one
shared settings nav, and the company brand color + per-company
attachment size limit removed (also reflected in the Companies and Cases
APIs).
- **Governance behavior** — silent-run detection and stranded-task
recovery no longer act on their own; agent thought text is excluded from
automatic comments; invalid agent credentials now return `401`.
**Changelog** — entry added for v2026.831.1.
## Gates
- `docs:build`, SEO metadata, crawlable-links, sitemap-lastmod
(194/194), lint-links, verify-nav — all pass.
- **Edit verification:** every new high-confidence claim verified at the
tag.
- **Tag-accuracy gate:** 31 files checked, **0 post-tag leaks**, 30
clean, 1 review (below).
## ⚠ Drift (Verify before acting — not auto-resolved)
Medium-confidence REST-route drift in `docs/reference/api/companies.md`
— the import-transfer routes may no longer exist at these paths (likely
a false negative from prefix/dynamic registration; confirm before
editing):
- `POST /api/companies/import/transfers`
- `PUT /api/companies/import/transfers/{transferId}/parts/{partIndex}`
- `GET /api/companies/import/transfers/{transferId}`
- `POST /api/companies/import/transfers/{transferId}/preview`
- `POST /api/companies/import/transfers/{transferId}/apply`
## ⚠ Review
- `docs/reference/adapters/kimi-local.md` — new page; the only flagged
claim is the `secret-id` JSON **example placeholder** (not a real
identifier). Authored directly from the adapter's config surface at the
tag.
## Screenshots (deferred)
288 of 342 registered screenshots are stale (org-wide rename +
settings/onboarding rewrites), tracked in `SCREENSHOTS_PENDING.md`.
Recapture is a follow-up pass — **the merged pages describe the new
onboarding/settings UI while screenshots still show the old flow until
then.**
---------
Co-authored-by: Claude Opus 4.8 <[email protected]>
6.8 KiB
paperclip_version, seo_title, seo_description
| paperclip_version | seo_title | seo_description |
|---|---|---|
| v2026.831.1 | Kimi Code Adapter | Run Moonshot's Kimi Code CLI on the Paperclip host as a local coding agent, on the shared ACP engine by default with an automatic headless-CLI fallback. |
Kimi Code
kimi_local runs Moonshot's Kimi Code CLI (kimi) on the same machine as Paperclip. Use it when you want a local coding agent that streams a structured live transcript, resumes sessions across heartbeats, and gets your Paperclip skills injected without polluting your own Kimi skills home.
Kimi Code runs on the same shared ACP engine as Claude, Codex, and Gemini by default, and falls back to a headless CLI lane when ACP prerequisites are missing.
When To Use
- You already run the Kimi Code CLI on the host machine.
- You want session continuity across heartbeats (
-r <session_id>). - You want Paperclip skills injected into the Kimi skills home without touching the agent workspace.
When Not To Use
- The runtime lives behind a webhook or remote API. Use HTTP or OpenClaw Gateway.
- You only need a shell command or script. Use Process.
- Kimi Code CLI is not installed or cannot be executed from the Paperclip host.
Common Fields
| Field | Required | Notes |
|---|---|---|
cwd |
no | Default absolute working directory for the agent process. Paperclip creates the path when permissions allow; if omitted, it falls back to the current process working directory. |
engine |
no | Which lane runs Kimi: the adapter defaults to the ACP engine (kimi acp) and falls back to the headless CLI when ACP prerequisites are unavailable. Set acp or cli to require a specific lane. See ACP Engine. |
model |
no | Kimi model alias (provider/model). Defaults to kimi-code/kimi-for-coding. See Models. |
effort |
no | Thinking effort (low, medium, high, max). CLI lane only. See Thinking Effort. |
promptTemplate |
no | Prompt template used for the run. |
instructionsFilePath |
no | Absolute path to a markdown instructions file prepended to the run prompt. Sibling files in the same directory (HEARTBEAT.md, SOUL.md, TOOLS.md) are made readable via --add-dir for local runs. |
command |
no | Defaults to kimi. |
extraArgs |
no | Additional CLI arguments appended to the Kimi invocation. |
env |
no | KEY=VALUE environment variables passed to the runtime. Secret refs are supported. |
timeoutSec |
no | Run timeout in seconds. |
graceSec |
no | SIGTERM grace period in seconds before a forced stop. |
Note: The adapter sets a headless-safe environment (
CI=1,NO_COLOR=1,KIMI_CODE_NO_AUTO_UPDATE=1) so unattended runs never wait on an interactive prompt or an update preflight.
ACP Engine
Kimi Code runs through one of two lanes, selected by the engine field:
- ACP (the default). Paperclip runs Kimi through the Agent Client Protocol (
kimi acp), giving you a structured live transcript — session identity, status with context-window usage, assistant and thinking token deltas, and tool-call updates that fold into a single card as they progress. This is the same machinery Claude, Codex, and Gemini use. - CLI (the fallback). When ACP prerequisites are unavailable, the adapter automatically falls back to the headless CLI lane. It runs
kimi -pwith--output-format stream-jsonfor non-interactive execution; the prompt is passed as an argument, not on stdin.
Leave engine unset to get ACP with automatic CLI fallback. Set engine: "acp" to require ACP (a failed prerequisite stops the run), or engine: "cli" to always use the headless CLI lane.
Models
Pick a Kimi model alias in the model field. The known options are:
kimi-code/kimi-for-coding— K2.7 Coding (the adapter default)kimi-code/kimi-for-coding-highspeed— K2.7 Coding Highspeedkimi-code/k3— K3
You can also type a model alias that is not in this list; Paperclip passes an unrecognized value straight through to the Kimi CLI.
Thinking Effort
The effort field maps a Paperclip effort value onto Kimi's supported thinking-effort tiers. Kimi exposes low, high, and max — there is no medium tier, so medium maps onto high.
Effort is honored on the CLI lane only (engine: cli, or the automatic CLI fallback), where it is forwarded as KIMI_MODEL_THINKING_EFFORT for effort-capable models — currently only kimi-code/k3. It is ignored for models that do not advertise effort support, and it is not forwarded on the default ACP engine lane. If you need effort control, pin engine: "cli".
Session Persistence
Kimi sessions resume with -r <session_id> when the stored session's working directory matches the current cwd. The session id is captured from the trailing session.resume_hint meta event.
The session codec also preserves these location hints when present:
cwdworkspaceIdrepoUrlrepoRef
If the working directory changes, the adapter starts a fresh session instead of reusing the old one.
Skills Injection
For local runs, Paperclip delivers the desired skills through --skills-dir pointing at a per-run managed directory, so skills load reliably without polluting your own ~/.kimi-code/skills home. Remote runs sync skills into the remote skills home instead.
The Kimi skills home defaults to ~/.kimi-code/skills, or $KIMI_CODE_HOME/skills when you set KIMI_CODE_HOME. When you install Paperclip skills through the CLI for manual use, that is the directory they land in.
Authentication
Kimi Code authenticates in one of three ways:
kimi login— the OAuth device flow, the same login you use for Kimi Code outside Paperclip.- Providers configured in Kimi's
config.toml. - The
KIMI_MODEL_NAME+KIMI_MODEL_API_KEYenvironment pair — set these in the adapter'senvto run against a specific model and key directly.
Environment Test
The Test Environment button checks that the Kimi Code CLI is installed and executable, that the working directory is usable, and that authentication is ready before you try a real heartbeat. Fix the command or auth path if the probe fails.
Example
{
"adapterType": "kimi_local",
"adapterConfig": {
"cwd": "/Users/me/projects/paperclip-workspace",
"model": "kimi-code/kimi-for-coding",
"instructionsFilePath": "/Users/me/projects/paperclip-workspace/INSTRUCTIONS.md",
"env": {
"KIMI_MODEL_API_KEY": {
"type": "secret_ref",
"secretId": "secret-id",
"version": "latest"
}
},
"timeoutSec": 300,
"graceSec": 15
}
}