Muse Assistant

Muse Assistant is Meta’s consumer Muse app — a general assistant, not a coding agent. Connecting it to kcap lets a Muse chat use your workspace’s tools, and lets you record the chats you choose as kcap sessions.

It is separate from Muse Code, Meta’s coding-agent CLI, which kcap captures, imports, and hosts like the other supported agents.

Connect in one step

Give Muse the connect-capacitor skill — paste it into the chat, or ask Muse to read it from https://raw.githubusercontent.com/kurrent-io/kcap-cli/main/kcap/skills/connect-capacitor/SKILL.md — then say Connect Capacitor and give your workspace address (for example https://acme.kcap.ai).

Muse then does the rest inside its VM:

1. Installs kcap under ~/workspace/kcap. Only your home directory survives a VM replacement, so the skill never installs kcap globally.
2. Runs kcap setup --muse-assistant with your workspace, which signs you in with a device code: Muse shows you a URL and a short code to approve on your own device.
3. Registers kcap’s tools with Muse as a custom connector, and writes a capacitor skill that tells Muse how to use them.
4. Offers an hourly kcap status cron that keeps the sign-in from lapsing on an idle VM. It is created only if you agree.

Each time Muse first contacts a new host — your workspace, phog.kurrent.io, then your sign-in provider — a card asks you to approve it. Choose Always allow this site. Setup lists these hosts before it contacts them; if a step reports that it cannot reach the server, approve the waiting card and Muse runs the step again.

--muse-assistant installs no hooks, skills, or MCP servers for any coding agent in the VM and imports no history. If the sign-in lapses later, say reconnect Capacitor.

What a chat can do with kcap

Once connected, a Muse chat can call kcap’s tools:

• Session recall — search and read recorded coding-agent sessions.
• Team memory — search and save durable team knowledge.
• Insights — query your workspace’s agent analytics.
• Work items and declared plans.
• Curated knowledge — facts and skills.

Ask in ordinary language: “what did my team work on this week”, “find the session where we fixed the login bug”, or “save this for the team”.

Recording chats

Connecting records nothing. Recording is opt-in per chat:

• Say record my chats (or name the chats). Muse installs its capacitor-recording skill, reads the exact recording scope back to you, and waits for a clear yes before granting it.
• A recorder cron on the Muse side then runs every 15 minutes. It reads each granted chat’s new messages and hands them to kcap muse-assistant ingest, which uploads them.
• Recorded chats appear as kcap sessions with the vendor muse-assistant. They are always private and owned by you, whatever your default visibility.
• Only user, assistant, and commentary messages are recorded; Muse’s developer messages are never sent. Tool calls, browser actions, approvals, and files are not recorded, and recorded chats carry no cost.
• A gap of two hours or more starts a new session.
• Say stop recording to revoke a chat’s grant: nothing further is sent from it, and kcap tries to close its open session, retrying on a later run if that fails.

Ask Muse what Capacitor is recording to see every chat’s status (kcap muse-assistant scope show). The CLI reference covers the commands.

Limits

• Custom connector. kcap is not yet a listed Muse connector, so each user connects their own Muse Assistant with the step above.
• kcap in the VM. The connector, the tools, and recording all run through the kcap CLI installed in your Muse VM; without it, nothing connects or records.
• Not every tool. Pages and flows are not part of the Muse connector.