Skip to content

feat(agents): file any conversation in the owner's workspaces - #4173

Draft
baxen wants to merge 1 commit into
mainfrom
mbot/workspace-agent-tools
Draft

baxen wants to merge 1 commit into
mainfrom
mbot/workspace-agent-tools

Conversation

@baxen

@baxen baxen commented Nov 21, 2026

Copy link
Copy Markdown
Collaborator

Summary

The sidebar now uses unified workspaces, but the agent tools still assumed Solo-only workspaces. This PR updates the tools so agents can file any conversation the owner can see.

  • workspace_list replaces solo_workspace_list. It already read the unified layout, so it returns every workspace, channel groups included.

  • channel_create with workspace works for any type. The owner must be able to see the result:

    • a Solo chat must name the owner in members;
    • a stream or forum must be open. A private one would leave the owner out, so it is refused before creation.

    Filing still checks the relay's confirmed metadata and roster: the agent created it, no plugin region manages it, its named members joined, and the owner is a member or it is open.

  • Workspace defaults apply on create unless a template is chosen, as in the dialog. They load through loadChatSetup, the exported read that the Solo New chat flow uses.

    • Solo chat: the default agents join in the create, and the Canvas starts with the full workspace block.
    • Team channel: the Canvas gets only shareableInstructions, as New channel shares by default, and the default agents are added after.
    • Defaults that fail to load stop the create before anything is published. On a host without saved channel kits there are no defaults.
  • New channel_move: takes a conversation (default: current) and a workspace ID, or an empty one to unfile. It works for any type, DMs included. It reads relay metadata and roster as the owner and moves only what the owner can see. Like Move to, it refuses chats a plugin region manages, then writes the same sidebarPreferences.assign.

  • Host capability renamed: soloWorkspaces is now workspaces { list, defaults, prepare, move } in the agent service, runner and MCP app client. Like before, it exists only on a local agent run, never on plugin handles or external MCP connections.

  • Docs: docs/buzz-help.md, docs/agents.md (section renamed "Filing conversations in the owner's workspaces") and docs/solo/README.md.

Decisions

  • An agent can't file a private team channel in a workspace, because the owner isn't a member of it. Adding the owner automatically, or allowing members on streams and forums, would change the create and is left out.
  • An open channel the agent files while the owner isn't in it is recorded in that workspace. The sidebar lists only conversations the owner belongs to, so it appears there once they join.
  • move checks visibility as the owner, not as the agent. An agent can therefore file the owner's DM with someone else.

Testing

  • vitest run (full suite)
  • tsc --noEmit
  • Biome check on the changed files
  • New tests: tools.test.ts (team-channel defaults, Solo default agents, template override, defaults failure, channel_move), app-client.test.ts (forwarding and retirement), service.test.ts (open-channel filing, relay-confirmed visibility refusal, defaults canvas sharing, move/unfile/refusals, unconfirmed move, community change).
  • Not exercised in the running desktop app.

🤖 Generated with Claude Code

Rename solo_workspace_list to workspace_list, let channel_create file
any conversation type the owner can see, apply the workspace's defaults
on create as New chat and New channel do, and add channel_move to file
or unfile an existing conversation, DMs included.

Co-authored-by: mbot <3754f8729004d95654c46dbab3129e4ab9ef05cc2534e2a3fbfc155983bd637b@buzz.block.builderlab.xyz>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant