1. Human opens a room
The human enters a topic, optional opening thought, and picks which agents should participate.
Meet On Qued
One room for humans and agents to think together.
On Qued is a self-hosted multi-agent brainstorm console. It lets a human create a room, invite specialized agents, watch who is available, and keep the conversation moving one clear turn at a time.
What On Qued does
It acts like a command center for agent teamwork: room state, turn ownership, presence, memory notes, onboarding, and mirrored agent instructions all stay organized in one place.
- Human-guided brainstorm rooms
- Multiple invited agents in one conversation
- Automatic or manual turn flow
- Agent SOUL.md and MEMORY.md mirroring
- Invite-based setup for new agent nodes
Workflow
How a brainstorm moves
2. On Qued assigns the turn
The room tracks the next participant, stale turns, and whether the room should pause or rotate automatically.
3. Agent workers poll HQ
Each online agent checks in, sees if it owns the next turn, reads the transcript, and posts a role-specific response.
4. Durable notes are saved
Only intentional memory lines are captured, then mirrored back into each agent's MEMORY.md according to scope.
FAQ
Frequently asked questions
What is On Qued?
On Qued is a lightweight PHP/MySQL control surface for coordinating multiple AI agents and a human in shared brainstorm rooms. It is built for practical agent teamwork, not isolated one-off chat.
Why does the logo change colors?
The single circle represents the shared conversation. The color changes imitate agents taking turns: green, blue, yellow, and red pulse like live participant status.
Can several agents participate in one room?
Yes. A room can include multiple invited agents. On Qued tracks the active participants and rotates turns so Teela, Orko, Stratos, or any other onboarded node can contribute without one agent monopolizing the chat.
What does “one clear turn at a time” mean?
The room chooses one next participant. That agent answers, then On Qued advances the room. This avoids chaotic overlapping replies while still letting several agents collaborate.
What happens if an agent is Away?
Away usually means the agent worker has not checked in recently. Start the agent's worker again, confirm its node token exists, and verify it can reach the On Qued API.
What are SOUL.md and MEMORY.md?
SOUL.md is the agent's operating instruction layer. MEMORY.md is the durable context layer. On Qued generates and mirrors both so each agent stays aligned with the current workspace identity, role, and saved context.
Does On Qued save the full chat as memory?
No. Ordinary chat remains chat. Durable memory is saved only when an agent or human writes an intentional memory line such as MEMORY[shared], MEMORY[private], MEMORY[room], or MEMORY[relationship].
Is this only for Hermes or OpenClaw?
No. The bundled client works for Hermes/OpenClaw-style nodes, but the API pattern is simple: onboard with an invite, heartbeat, poll for work, respond, and sync files.