Step-by-step setup for Anthropic's CLI with KaKeKiKoKu via MCP
This guide walks you through configuring Claude Code so it works with KaKeKiKoKu.
Claude Code is Anthropic's command-line tool for AI-assisted development. It is the most complete integration with KaKeKiKoKu today thanks to channels: a feature that lets KaKeKiKoKu send messages to the AI in real time (automatic sync requests, drift alerts, "Talk to AI" buttons). Other AI clients work in Precise mode, copying prompts to the clipboard for you to paste — but with Claude Code the integration is bidirectional and seamless.
Important: Claude Code is NOT Claude Desktop. They are different Anthropic products. Claude Code is a CLI (command line); Claude Desktop is a desktop app. When you finish setup, make sure a console window opens, not a desktop app window. If a graphical app appears, you launched the wrong product.
Before you start the KaKeKiKoKu integration flow, you need these regardless of OS:
Plus the OS-specific tools below:
sudo apt install git, Fedora/RHEL: sudo dnf install git, Alpine: sudo apk add git).sudo apt install curlsudo dnf install curlsudo apk add curlIf Claude Code is already installed, verify the version before continuing. If it is missing, use the OS-specific installer below.
powershell -ExecutionPolicy Bypass -Command "irm https://claude.ai/install.ps1 | iex"claude --versionclaude --version doesn't respond, some Claude Code installs don't add .local\bin to the user PATH correctly. Paste this in PowerShell, close it and reopen:
[Environment]::SetEnvironmentVariable("Path", [Environment]::GetEnvironmentVariable("Path","User") + ";$env:USERPROFILE\.local\bin", "User")C:\Users\<your-user>\.local\bin\claude.exeIf you installed via npm instead of the native installer, it might also live at %APPDATA%\npm\claude.cmd. Anthropic now recommends the native binary for most users.
curl -fsSL https://claude.ai/install.sh | bashThis downloads a self-contained binary — you do not need Node.js or npm.
claude --versionclaude, it will prompt you to log in with your Anthropic account.Other Linux installation methods. Anthropic also publishes signed APT (Debian/Ubuntu), DNF (Fedora/RHEL), and APK (Alpine) repositories at
downloads.claude.ai— useful for managed fleets or distros where you prefer your package manager. See the official installation docs for repository details and GPG verification.
↑ Back to topKeep Claude Code up to date. Native installations update in the background. Run
claude updatewhen you want an immediate update, or choose thestableorlatestchannel in/config. Package-manager installs such as WinGet, Homebrew, APT, DNF, and APK use their own update flow.
Register KaKeKiKoKu with Claude Code's built-in MCP command. Choose your operating system and run the command shown there:
claude mcp add --transport stdio --scope user wuniq -- wuniq-mcp.exeImportant. Use the alias name
wuniq-mcp.exe. Never substitute an absolute path to a binary underC:\Program Files\WindowsApps\...— Windows ACLs cause Permission denied errors at launch.
claude mcp add --transport stdio --scope user wuniq -- /snap/bin/wuniq.wuniq-mcpThis edits your Claude Code config file automatically and leaves any other registered MCP servers intact.
The
--scope userflag matters. It makes the KaKeKiKoKu registration visible from any folder. Without it, the entry stays local to the folder where you ran the command — Claude Code won't find KaKeKiKoKu if you start it elsewhere.
claude mcp listIt should show wuniq among the configured servers.
Only if you decide to stop using KaKeKiKoKu with Claude Code, remove the MCP registration with:
claude mcp remove wuniq↑ Back to topWhere this is stored. User-scoped servers live in
~/.claude.jsonand load in every project for that OS user. Claude Code also supports local scope (private to one project, stored under that project's entry in~/.claude.json) and project scope (shared through.mcp.json). KaKeKiKoKu uses user scope here because one local KaKeKiKoKu engine can serve several projects.
This is the second of the two pieces every integration needs (the first was registering KaKeKiKoKu as an MCP server in step 1). A small file in your working directory tells Claude Code to use KaKeKiKoKu from the start of every session — without it, Claude Code starts "neutral" and you have to ask for open list manually each conversation.
.claude/rules/The path is the same on Windows and Linux — it's relative to the working directory, not to your home folder.
wuniq.md with this content:
# KaKeKiKoKu Studio (Knowledge Engine)
At the start of every session, run `open list` using the KaKeKiKoKu MCP tool. If it returns projects, `open` each one. If the list is empty, proceed normally — the user may open projects later from the KaKeKiKoKu UI. Never assume the working directory is a KaKeKiKoKu project; the working directory may be a container folder holding multiple projects. Only open paths that `open list` explicitly returns.
Before working on any code file, `read` its KaKeKiKoKu sidecar for context. After changing code, run `sync`..claude/rules/*.md at the start of each session.Why don't we put this inside
CLAUDE.md?Your
CLAUDE.md(if you have one) is yours. KaKeKiKoKu prefers not to touch it so it doesn't overwrite content you wrote..claude/rules/wuniq.mdis an independent file KaKeKiKoKu controls and you can delete freely without losing anything of your own.
If this repository already uses
AGENTS.md. Claude Code does not loadAGENTS.mddirectly. Keep the dedicated KaKeKiKoKu rule above, or create aCLAUDE.mdcontaining@AGENTS.mdso Claude can import shared cross-client instructions without duplicating them. On Windows, the import is simpler than a symlink.
↑ Back to topWhat if I skip this step?
KaKeKiKoKu still works, but Claude Code won't open your projects automatically. You'll have to ask it to run
open listthe first time in every conversation. If the list is empty, open the project manually from KaKeKiKoKu or tell Claude Code the project path.
Open a terminal in your working directory and run:
claude --dangerously-load-development-channels server:wuniq--dangerously-load-development-channels server:wuniq opts the explicitly named KaKeKiKoKu MCP server into Claude Code's channels research preview. Channels let KaKeKiKoKu push messages into the running session. Without the flag KaKeKiKoKu still works, but in Precise mode: sync is not pushed automatically and "Talk to AI" buttons copy to the clipboard.
The flag includes dangerously because it bypasses Anthropic's research-preview allowlist for the specific development channel named after server:. It does not mean "disable every permission", but it should still be used only with a local server you trust. KaKeKiKoKu names the exact server instead of enabling unknown channels. If you prefer not to use a preview feature, see "No-channels mode" below.
Organization policy. Personal Pro and Max accounts can opt in per session. Team and Enterprise organizations must also enable Channels in their Claude Code admin settings; otherwise KaKeKiKoKu's MCP tools still work, but pushed channel messages do not arrive.
claude --continue --dangerously-load-development-channels server:wuniqclaude --model opus[1m] --dangerously-load-development-channels server:wuniqTo avoid typing the command every time, you can create a launcher script in your working directory. KaKeKiKoKu does not generate it for you — you control the flags and any extra steps before or after.
Create a file called KaKeKiKoKu Run.cmd (or any name you prefer) in your working directory with this content:
@echo off
set "PATH=%USERPROFILE%\.local\bin;%PATH%"
cd /d "%~dp0"
powershell.exe -NoExit -Command "claude --dangerously-load-development-channels server:wuniq"Double-click and Claude Code launches ready to work. You can pin it to the desktop or taskbar. Adjust flags as needed: add --continue to resume the previous session, or --model opus[1m] to request Opus with extended context (availability depends on your plan) — see "Plan and model" below.
Create a file called wuniq-run.sh (or any name you prefer) in your working directory with this content:
#!/bin/bash
export PATH="$HOME/.local/bin:$PATH"
cd -- "$(dirname -- "$0")"
claude --dangerously-load-development-channels server:wuniqFrom the folder where you saved it, make it executable once:
chmod +x wuniq-run.shRun it from the terminal with ./wuniq-run.sh. Some desktop environments can also run .sh files on double-click, but terminal launch is the predictable option. Adjust flags as needed: add --continue to resume the previous session, or --model opus[1m] to request Opus with extended context (availability depends on your plan) — see "Plan and model" below.
The first time Claude Code connects to KaKeKiKoKu you'll see a series of prompts. Here's what to expect and what to choose.
Claude Code asks if you trust the working directory. Choose "Always allow".
Claude Code may ask for additional confirmation to use the wuniq.run tool. Accept. That's what allows the AI to read and write context through KaKeKiKoKu.
If this is your first Claude Code, complete the login with your Anthropic account. KaKeKiKoKu does not participate in this step — subscription and authentication are managed entirely by Anthropic.
Make sure a terminal/console window opens where you talk to the AI. On Windows, if a graphical desktop app opens instead of a console, you launched Claude Desktop by mistake (different product). Close it and review the command.
Inside Claude Code, type:
/mcpIt should list wuniq among the available servers. If it doesn't appear, Claude Code didn't find the registration — go back to step 1.
If you followed step 2 (.claude/rules/wuniq.md), Claude Code will run open list automatically when you start your first conversation.
If you didn't create the file, ask Claude Code to run open list. If the list is empty, open the project manually from KaKeKiKoKu or tell Claude Code the project path.
Close Claude Code, go back to the console, and relaunch. If it still doesn't work, see "Troubleshooting" at the end.
↑ Back to topKaKeKiKoKu works through your Claude Code subscription (it does not use the Anthropic API). The Anthropic plan you have determines which model is the default and how much context the AI can handle in a single session.
Claude Code's default selection follows your account type and any organization policy. At the time of this review, Anthropic documents:
If you launch claude --dangerously-load-development-channels server:wuniq without --model, Claude Code uses your plan's default. Perfectly valid for most sessions.
Claude Code now supports a 1M-token context window on Fable 5, Sonnet 5, Opus 4.6 and later, and Sonnet 4.6. The exact behavior depends on the model, provider, and plan:
| Plan | Opus + 1M context | Sonnet + 1M context |
|---|---|---|
| Max, Team, Enterprise | Automatically upgraded to 1M | Sonnet 5 is native 1M on Anthropic; Sonnet 4.6 requires usage credits |
| Pro | Requires usage credits for an Opus 1M variant | Sonnet 5 is native 1M on Anthropic; older 1M variants can require credits |
Usage-credit and provider rules can change independently of KaKeKiKoKu. See usage credits in Anthropic's support docs and the current model configuration page before relying on a particular entitlement.
Anthropic provides model aliases so you don't have to remember exact version numbers:
best — Fable 5 where available; otherwise the latest Opus.fable — Claude Fable 5 for the hardest and longest-running tasks.opus — latest Opus for complex reasoning.sonnet — latest Sonnet for daily coding work.haiku — fast model for simpler tasks.opus[1m] and sonnet[1m] — request the 1M context variant when the underlying model/provider needs an explicit suffix.opusplan — hybrid: Opus during plan mode, Sonnet for executiondefault — clear a model override and return to the recommended or organization-selected default.Examples (combine with the launch flag):
claude --model best --dangerously-load-development-channels server:wuniq
claude --model opus[1m] --dangerously-load-development-channels server:wuniq
claude --model opusplan --dangerously-load-development-channels server:wuniqYou can also pin a specific version with the full model name, but aliases are recommended — they keep pointing to the current version as Anthropic releases new models.
If your selected model, provider, or organization caps the session below 1M, KaKeKiKoKu remains productive because context loading is progressive: it does not send the entire project as raw text. Claude reads sidecars and uses search / read on demand.
Anthropic releases new models periodically. Check the Claude Code model configuration docs for current aliases, default behavior, and version-pinning options.
↑ Back to topIf you'd rather not use the --dangerously-load-development-channels flag (because the name bothers you, because you don't need push notifications, or for any other reason), you can launch Claude Code like this:
claudeKaKeKiKoKu still works — but in Precise mode instead of Automatic.
open, read, edit, sync, search, etc.sync in the chat to invoke it.dangerously flag bothers you (the name is decided by Anthropic, not KaKeKiKoKu).In KaKeKiKoKu > Settings > Application > AI Sync, choose Precise mode. That replaces automatic push with clipboard copy for all affected functions.
↑ Back to topCommon problems and how to solve them.
claude --version doesn't respond after installSome Claude Code installs don't add .local\bin to the user PATH correctly. Paste this in PowerShell, close it and reopen:
[Environment]::SetEnvironmentVariable("Path", [Environment]::GetEnvironmentVariable("Path","User") + ";$env:USERPROFILE\.local\bin", "User")After installing Claude Code with curl install.sh, the updated PATH only applies to new shells. Close the terminal where you ran the installer and open a new one. If claude --version still fails, source your shell config in the active terminal:
source ~/.bashrc # or ~/.zshrc, depending on your shell/mcpclaude mcp list. If wuniq is missing, repeat step 1.wuniq is listed but still does not load, remove the registration and add it again:
claude mcp remove wuniqwuniq-mcp.exe/snap/bin/wuniq.wuniq-mcpIf a previous registration points to the KaKeKiKoKu executable using an absolute path under C:\Program Files\WindowsApps\..., Windows refuses execution due to restrictive ACLs. Remove the registration and repeat step 1 using the alias wuniq-mcp.exe:
claude mcp remove wuniqclaude --version, then run claude doctor for a fuller installation and configuration check. Channels require Claude Code 2.1.80 or later, while newer models require later point releases. Run claude update if necessary.--dangerously-load-development-channels server:wuniq exactly. Without the server:wuniq part, the bridge doesn't connect.--model flag failsCheck claude --help or the Claude Code model configuration docs. Some current models require a newer Claude Code build; update first if aliases such as fable, best, or a 1M variant do not appear.
If you reinstalled KaKeKiKoKu and the connection fails, remove the old Claude Code registration and repeat step 1:
claude mcp remove wuniq/home/ (Linux)The KaKeKiKoKu snap is sandboxed by default and cannot read files outside your home folder unless you grant that permission. If your projects live in /mnt/, /media/, a USB drive, or a VM shared folder such as /mnt/hgfs/, run:
sudo snap connect wuniq:removable-mediaThen reload the KaKeKiKoKu web UI and open the project again.
Linux caps the number of files a single user can watch at once. Very large projects can hit that limit. Symptoms: file changes go undetected, KaKeKiKoKu panel doesn't update. Raise the watch limit:
echo "fs.inotify.max_user_watches=524288" | sudo tee -a /etc/sysctl.conf
sudo sysctl -pOn Linux, if Claude Code started KaKeKiKoKu through the MCP connection, KaKeKiKoKu may close when Claude Code closes. If you want KaKeKiKoKu to stay open between Claude Code restarts, launch KaKeKiKoKu from your desktop menu before launching Claude Code.
Some shared folders and network drives do not notify Linux apps reliably when files change. If your project is on a VMware shared folder, SMB/CIFS share, or sshfs mount, KaKeKiKoKu may not notice edits immediately even after access has been granted. When that happens, run sync from Claude Code or click Analyze in the KaKeKiKoKu UI.
Email support@kakekikoku.com with your operating system, Claude Code version (claude --version) and the contents of your Claude Code config file (Windows: %USERPROFILE%\.claude.json, Linux: ~/.claude.json). KaKeKiKoKu can also generate a diagnostic report (Support function in the app) that captures the infrastructure state — attach it to the email.