Skip to content
kanade — 奏 kanade docs

Route the work. Recall the proof.

Route provider lanes, recall Hermes memory, launch Forge missions, bridge signed Discord asks, and verify source, installed desktop, live docs, and update-channel proof as separate targets.
Read the user guide See what shipped Open the issue tracker
Route the work. Recall the proof.

Kanade is a self-hosted local app, not a hosted service. The docs describe the maintainer-verified v0.5.0 channel while keeping the private-alpha boundary explicit.

Forge bridge artwork
Alpha · privateNo public installer, invite path, download CTA, or tester access flow.
SourcePrivate repository at github.com/HeyiTzSenpai/kanade.
UpdaterMaintainer-only channel; installed files must prove every release.

Reading path

Section titled “Reading path”

Getting started

Read what Kanade is, why the desktop app stays private, and what first-run setup writes to your machine. Read the posture ->

The workstation

Work from Tsukue: provider lanes, chat, terminal, sessions, skills, files, and Claude Code integration. Open the desk guide ->

Hermes memory

Track memory tiers, fact proposals, project instructions, skill drafts, roots, and the memory map. Read the memory section ->

Missions + Forge

Launch bounded Forge runs from mission records and keep Kanade as the relay, not the Forge backend. Read the bridge contract ->

Discord bridge

Run signed, allowlisted asks through the self-hosted bot and keep rate limits visible. Read the bridge docs ->

Reference

Environment variables, daemon API shape, updater proof, troubleshooting, and release history. Open reference ->

1 · orientConfirm alpha status, local-first boundaries, and what is private.
2 · connectAdd lanes, memory roots, personas, and voice runtime settings.
3 · routeUse Tsukue, Mission Control, Forge bridge, Discord, and memory recall.
4 · verifyCheck source, installed desktop, live docs, and updater channel separately.

The shape of the alpha

Section titled “The shape of the alpha”

Kanade is the private Windows workstation for Claude Code. It keeps provider lanes, Hermes-deep memory, mission launches, Forge runs, and signed Discord asks in one local app. It is AGPLv3, self-hosted, and telemetry-free by default: hooks append to local files, the daemon indexes local state, and nothing leaves the machine unless an operator points a lane at a provider, remote LLM, Forge backend, or Discord relay.

  • Platform: Windows 10 / 11, x64.
  • Release state: v0.5.0 is verified on the maintainer desktop and private update channel. Public readers should treat these docs as operating notes, not an access path.
  • Bring your own: provider accounts, credentials, Forge backend, Discord token, and optional local LLM.
  • Proof stance: source preview, installed desktop, live docs, and update channel are different targets. A build log is useful evidence; it is not a shipped claim by itself.

Verification target note: when these docs say a feature is shipped, the target is named. For v0.5.0, installed desktop and updater-channel proof passed; Direct-provider live proof, user-side Discord slash proof, and a few manual Tauri exercises remain separate carries.