Repository navigation
Conversation
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
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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_listreplacessolo_workspace_list. It already read the unified layout, so it returns every workspace, channel groups included.channel_createwithworkspaceworks for any type. The owner must be able to see the result:members;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
templateis chosen, as in the dialog. They load throughloadChatSetup, the exported read that the Solo New chat flow uses.shareableInstructions, as New channel shares by default, and the default agents are added after.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 samesidebarPreferences.assign.Host capability renamed:
soloWorkspacesis nowworkspaces { 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") anddocs/solo/README.md.Decisions
memberson streams and forums, would change the create and is left out.movechecks 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 --noEmittools.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).🤖 Generated with Claude Code