Co-presence

What it is

Co-presence is a feature of the Prompt Editor: a Claude Code plugin that puts your coding agent in the room with you. It reads the prompt and its review, talks to you in the editor's Coding Agent panel, highlights what it is describing, stages edit proposals you accept with one click, and wakes on its own when you message it or decide on a card. This page is how to set it up.

Every change goes through you.

The agent stages proposals - you accept or reject each one - and applying its own proposal takes permission you grant in that session. It has no path to your prompt that skips your accept.

Install - once, about two minutes

You need your pfr_... key in your shell (mint one at /setup/mcp). This plugin reads HOSHO_API_KEY from the shell - if your key only lives inside an MCP client config, export it first.

export HOSHO_API_KEY=pfr_...
claude
/plugin marketplace add HOSHO-AI/hosho-plugin
/plugin install hosho@hosho

Install at user scope when prompted - the plugin follows you across projects and is tied to your personal key; project scope would write it into shared team settings.

Start a session

claude --dangerously-load-development-channels plugin:hosho@hosho
/model sonnet

Then join - one of two forms, your choice:

/hosho:join <prompt URL>

/hosho:join <editor URL>

The --dangerously-load-development-channels flag is a Claude Code requirement, not a Hosho shortcut: channels are a research preview, and during it Claude Code only accepts channel plugins from an allowlist Anthropic curates - a plugin from any other marketplace needs the flag. It shows a confirmation screen the first time, bypasses the allowlist only, and your organization's channel policy still applies. A plain claude session also works with full co-presence - the agent just catches up on its next turn instead of waking on its own.

On Team/Enterprise Claude plans, an admin must enable channels (`channelsEnabled`) for wake-ups to work.

Updating

claude mcp remove --scope user hosho-channel
claude
/plugin marketplace update hosho
/reload-plugins

Good to know

• Can I use my team's shared key? It works, but your own key is better: it names the agent after you, and on a shared key every teammate's activity anywhere wakes your sessions.
• Why does the launch command need a development flag? Channels are in research preview, and `--channels` only accepts plugins on an allowlist Anthropic curates. A Team/Enterprise admin can set their own `allowedChannelPlugins` to drop the flag. Plain `claude` also works and keeps full co-presence - you just won't be woken automatically.
• What permissions will it ask for? On the first Hosho tool call, choose "always allow" for both Hosho servers. The tool surface is read-and-stage by default; applying an edit needs your explicit permission in the session.
• I set Hosho up before v0.3.0 Earlier versions asked you to register the wake channel by hand; the plugin declares it now. Clear the old entry once so it doesn't run twice - it's the first step on the Update tab.
• Where does the key live? In your shell, as `HOSHO_API_KEY`. The MCP keeps its own copy inside its client config, so the plugin can't read that one - paste yours into your shell profile.