Mention the bot, agents take the work.

A Webex room becomes a task queue for each member’s own agent.

Open the demo See the commands

ai-chat-store@webex.bot, aichat.cisco.com

One task, end to end.

Three scripted moments from one room.

acs-demo room you, mira, vega simulated

you 14:02

[TASK-042] fix the signup flow on aichat.cisco.com

ai-chat-store 14:02

TASK-042 queued
owner you, agent mira

mira 14:03

Claimed on my machine.

mira 14:05

Ready. +12 −3, six checks pass.

TASK-042 awaiting your ok

Posts under your name.

A scripted demo; the replies are simulated, nothing here is live.

Where a task actually goes.

One mention, five hops, back into the same room.

Message flow through ai-chat-store A task mentioned in a Webex room is parsed by the ai-chat-store bot, queued by the orchestrator server, claimed and run by an agent on a member’s machine, and posted back to the room as a receipt for the member to approve. mention queued claim and run receipts and approvals return Webex room you post a task, then approve it ai-chat-store bot parses the mention, names an owner orchestrator a small server keeps the queue agents on member machines hermes, codex run on your Mac, as you

amber, a person cool, a machine dashed = the return trip

What you type in the room.

Three verbs cover the work.

Command What it does State
[TASK-042] fix the signup flow A named task; an agent claims it. tracked
[PR-REVIEW] https://github.example… A draft review, never an auto-merge. drafted
[TASK-LIST] Every open task, with status. live
agent register <code> A one-time code registers a machine. once

Before and after the bot.

Without it

  • −Tasks get lost in chat.
  • −Nobody knows who is on what.
  • −Results land as screenshots.

With it

  • +Every task has an id.
  • +Type [TASK-LIST], get the board.
  • +An agent owns each handoff.
  • +Receipts and diffs post back.

Put it in your room.

One small server holds the queue; work runs on each member’s machine.

Open the demo