@insitue/claude-plugin 0.7.4 → 0.7.5

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "insitue",
-  "version": "0.6.4",
+  "version": "0.6.5",
   "description": "Drive a Claude Code session from the InSitue browser overlay. Pick an element in your app, claude reads the file and proposes the edit.",
   "mcpServers": {
     "insitue": {

package/CHANGELOG.md

@@ -1,8 +1,12 @@
 # @insitue/claude-plugin
 
+## 0.7.5
+
+- **Fix the channels command — it must be tagged with the marketplace.** The flag is `--channels plugin:insitue@insitue-plugins` (not `plugin:insitue`, which errored with "entries must be tagged"). Corrected in the `/insitue:connect` tip, the README, and the push-mode docs. Also synced the marketplace listing version.
+
 ## 0.7.4
 
-- **`/insitue:connect` no longer blocks the session.** In poll mode the agent silently re-looped `next_pick` forever, freezing the chat (queued messages never processed). It now polls once then hands control back, drains buffered picks on your next message, and points you at channel mode (`--dangerously-load-development-channels --channels plugin:insitue`) for truly hands-free background picks.
+- **`/insitue:connect` no longer blocks the session.** In poll mode the agent silently re-looped `next_pick` forever, freezing the chat (queued messages never processed). It now polls once then hands control back, drains buffered picks on your next message, and points you at channel mode (`--dangerously-load-development-channels --channels plugin:insitue@insitue-plugins`) for truly hands-free background picks.
 - **Brand the sign-in success page.** The loopback login success page uses the brand purple gradient heading instead of the off-brand green.
 
 ## 0.7.3
@@ -21,7 +25,7 @@
 
 ## 0.7.0
 
-- **Live picks without blocking the chat (channels, opt-in preview).** The MCP server now also PUSHES each pick as a Claude Code channel event (`notifications/claude/channel`). Start your session with `claude --dangerously-load-development-channels --channels plugin:insitue` and picks wake the idle agent instead of you waiting on a poll — the chat stays free for conversation the rest of the time. Plain `claude` + `/insitue:connect` is unchanged (8s poll fallback). The agent de-dupes by pick id, so the push + poll paths never double-handle a pick. Channels are a Claude Code research-preview feature (CLI-only); the flag is required during the preview.
+- **Live picks without blocking the chat (channels, opt-in preview).** The MCP server now also PUSHES each pick as a Claude Code channel event (`notifications/claude/channel`). Start your session with `claude --dangerously-load-development-channels --channels plugin:insitue@insitue-plugins` and picks wake the idle agent instead of you waiting on a poll — the chat stays free for conversation the rest of the time. Plain `claude` + `/insitue:connect` is unchanged (8s poll fallback). The agent de-dupes by pick id, so the push + poll paths never double-handle a pick. Channels are a Claude Code research-preview feature (CLI-only); the flag is required during the preview.
 
 ## 0.6.3
 

package/README.md

@@ -197,7 +197,7 @@ you can have picks **pushed** directly into the session so the
 chat stays completely free between picks:
 
 ```bash
-claude --dangerously-load-development-channels --channels plugin:insitue
+claude --dangerously-load-development-channels --channels plugin:insitue@insitue-plugins
 ```
 
 With this flag, every pick the user sends from the browser wakes
@@ -212,7 +212,7 @@ channel listener falls back to the normal poll automatically.
   preview period and may change or be renamed in a future release.
 - **Dropping the flag:** on Team/Enterprise, an admin can add `insitue`
   to the `allowedChannelPlugins` org policy — then the channel runs with
-  just `claude --channels plugin:insitue` (no dangerous flag). Once
+  just `claude --channels plugin:insitue@insitue-plugins` (no dangerous flag). Once
   channels leave research preview / the plugin is on Anthropic's default
   allowlist, the flag won't be needed at all.
 - It works only with the CLI (`claude`), not Claude Desktop.

package/commands/connect.md

@@ -35,7 +35,7 @@ double-delivery is possible and you must de-dupe by `id`.
 ### Push mode (channels — opt-in, Claude Code only)
 
 If the user started Claude Code with channel support
-(`claude --dangerously-load-development-channels --channels plugin:insitue`),
+(`claude --dangerously-load-development-channels --channels plugin:insitue@insitue-plugins`),
 picks are PUSHED into this session as
 `<channel source="insitue">…</channel>` events. Each event
 contains the pick's `id`, `userNote`, `source file:line`,
@@ -72,7 +72,7 @@ your context and skip any id you've already processed.
    >
    > Tip: for hands-free background picks (so I act the moment you
    > pick, without you waiting on me), relaunch with
-   > `claude --dangerously-load-development-channels --channels plugin:insitue`.
+   > `claude --dangerously-load-development-channels --channels plugin:insitue@insitue-plugins`.
 
 2. **Watch for a pick — ONE poll, then hand control back.** Call
    `mcp__insitue__next_pick` (it long-polls ~8s).

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@insitue/claude-plugin",
-  "version": "0.7.4",
+  "version": "0.7.5",
   "description": "Drive Claude (Code AND Desktop) from the InSitue browser overlay — pick an element in your app, claude reads the file and proposes the edit.",
   "keywords": [
     "insitue",