Skip to content
KurrentDB

Moving from Capacitor to kcap

Kurrent Capacitor was renamed kcap in October 2026. The product is the same; a few commands, paths and URLs changed with the name

BeforeNow
”Capacitor” in the web app, the desktop app and the CLI’s messages”kcap”
Docs at /docs/capacitor/…/docs/kcap/…; old links redirect
Artefacts: /artefacts/…, kcap artefact, the kcap-artefacts toolsPages: /pages/…, kcap page, kcap-pages; the old forms still work but are deprecated
The connect-capacitor skill for Muse Assistantconnect-kcap; saying “Connect Capacitor” still works
Setup’s “Capacitor” steering text in agents’ instruction filesRewritten on kcap refresh or kcap setup, and by the desktop app after it updates

What did not change: the npm package @kurrent/kcap, the kcap command, your workspace URL, your profiles and tokens, your sessions and their links, ~/.config/kcap

  • Old wording in your agent. The steering block in an instructions file still says Capacitor. kcap refresh rewrites it; or kcap plugin install --codex (or the flag for that agent)
  • An agent calls kcap mcp artefacts. It still works as an alias. kcap refresh updates the registration to pages
  • Bookmarked docs links 404. Links under /docs/capacitor/ and the pre-namespace /docs/ redirect; a link to a page that was merged lands on its replacement. If one does not, tell us
  • A Slack preview shows the old name. Previews come from the server; a workspace on an older server shows the old name until it is updated

Do I need to reinstall? No. kcap update is enough. The desktop app updates itself (Check for Updates… in the tray asks now) and refreshes your agents’ integrations afterwards

Will kcap artefact go away? Yes. kcap artefact, the kcap-artefacts tools and /artefacts/… links are deprecated. They still work today so nothing breaks on the day of the rename, but move to kcap page, kcap-pages and /pages/… as soon as you can; see Pages

Does anything about my data change? No. Same server, same storage, same audiences