Skip to content

Latest commit

 

History

History
57 lines (43 loc) · 2.35 KB

channels.md

File metadata and controls

57 lines (43 loc) · 2.35 KB

Channels

Sub-features

  • Create a channel from existing bots.
  • Send to its active task.
  • Wait for the room-level run rather than one member's transient state.
  • Read a bounded channel transcript.

User path

Create a channel from the sidebar, choose its members, and send a message in the channel composer.

Driving it

Create two fixture bots with new-bot, then:

pnpm control:omb new-channel --name Review --members BOT_A_ID,BOT_B_ID --url http://127.0.0.1:PORT
# Copy channel.id from the JSON above as CHANNEL_ID.
pnpm control:omb send-channel --channel CHANNEL_ID --text "Reply once" --url http://127.0.0.1:PORT
pnpm control:omb wait --channel CHANNEL_ID --timeout 60 --url http://127.0.0.1:PORT
pnpm control:omb messages --channel CHANNEL_ID --limit 20 --url http://127.0.0.1:PORT

Capture the returned channel ID from new-channel. The wait result must be settled; the transcript is the evidence.

Gotchas

  • Do not wait directly on a bot while it is speaking for a channel.
  • A confirmation card produces needs-user; it is not a timeout.
  • This first map does not claim to verify channel layout or sidebar UI.

Chief room management

pnpm exec vitest run server/chief-rooms.e2e.test.ts
pnpm exec vitest run server/index.test.ts -t 'Chief room|team-goal lead|credential-card ownership'

The end-to-end test launches the isolated control fixture, creates disposable bots, starts its fake Chief engine and uses that turn's mounted agents MCP proxy. It creates a room, renames it, changes members and its bulletin, then checks the saved state. A foreign-section member is refused; stopping the owning turn revokes the proxy's permission to rename the room. The test retains its control commands, tool results and final state beside the printed server log, without recording the bearer token, and removes its temporary home.

The API regressions exercise spoofed sender/thread claims, slow expired requests, current Chief status, peer allow-lists, hidden bots, creation limits, busy rooms, pending approvals, goal leads and in-flight credential saves. Public channel creation and edits use the same validation as the Chief tools. Chiefs cannot move rooms/bots between sections, remove themselves, or change working folders. Chiefs configured to require peer approval must ask the user to make room changes; these tools do not add a separate approval workflow.