block / block/buzz

Managed agent claims to create channels successfully, but channels never appear in the UI

Open
#6,028 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Rust
Stars
32.7k
Forks
4.3k
Avg merge
1d 13h
Merged PRs (30d)
253

Description

### Description
A managed agent (Fizz) reported that it successfully created multiple channels after receiving the instruction “structur now”.

The agent replied with a clear confirmation that the following channels were created

However, **none of these channels are visible** in the Buzz Desktop client (sidebar or channel list). Only the previously existing channels (`#general` and `#welcome-everyone`) remain. it was also not able to delete a channel which he was ordered to do so

This creates a false sense of success and wastes significant time, as the agent insists the structure was applied while the workspace remains unchanged.

### Steps to Reproduce
1. Create / use a managed agent with instructions to organize channels.
2. Ask the agent to create the channel structure (or give the signal “structur now”).
3. Agent responds that channels were successfully created and lists them.
4. Check the channel sidebar / list → new channels do not appear.

### Expected Behavior
- Either the channels are actually created and become visible to all members,
- or the agent clearly reports that it failed (e.g. missing permissions, relay error, etc.).

### Actual Behavior
Agent claims success (“structure done ✅”) and lists the new channels, but they do not exist in the UI or on the relay from the user’s perspective.

### Additional notes
- Agent also correctly noted that it could not delete `#welcome-everyone` because only the channel owner can delete groups.
- The agent appears to believe the channel creation succeeded.

### Environment
- **OS:** Linux
- **Buzz Desktop:** latest
- **Agent:** managed (Fizz)
- **LLM:** DeepSeek V4 Flash (via OpenRouter)
- **Relay:** Hosted / community relay

### Impact
High – the agent gives false confirmation, making workspace setup unreliable and time-consuming.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.