You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+18Lines changed: 18 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -113,6 +113,21 @@ The Rules panel opens from the header. Rules are grouped into **Active**, **Draf
113
113
114
114
**Remind agents** re-sends the current rules on the next trigger. The badge on the Rules button shows unseen proposals only. Max 160 chars per rule.
115
115
116
+
### Sessions
117
+
Structured multi-agent workflows with sequential phases, role casting, and turn-taking. Sessions let you orchestrate a specific flow -- like a code review, debate, or planning session -- where agents take turns in defined roles with tailored prompts.
118
+
119
+
**Built-in templates:** Code Review, Debate, Design Critique, and Planning. Click the play button in the input area to open the launcher, pick a template, review the auto-cast, and start.
120
+
121
+
**Custom sessions:** Click "Design a session" in the launcher, pick an agent, and describe what you want. The agent proposes a session draft as a card in the timeline. From there:
122
+
-**Run** -- opens a cast preview where you assign agents to roles, then starts the session
123
+
-**Save Template** -- saves the draft as a reusable template in the launcher
124
+
-**Request Changes** -- inline feedback form; the agent revises and the old draft is superseded
125
+
-**Dismiss** -- grey out the card
126
+
127
+
During a session, phase banners mark transitions in the timeline, a sticky session bar shows progress, and agents are triggered sequentially with phase-specific prompts. The output phase is highlighted when the session completes.
128
+
129
+
Sessions are channel-scoped (one active per channel) and survive page refreshes. Custom templates persist across restarts.
130
+
116
131
### Activity indicators
117
132
Status pills show a spinning border in each agent's color when that agent is actively working — so you can minimize the terminals and still know at a glance who's busy. Detection works by hashing the agent's terminal screen buffer every second: if anything changes (spinner, streaming text, tool output), the pill lights up. When the screen stops changing, it stops instantly. Cross-platform — Windows uses `ReadConsoleOutputW`, Mac/Linux uses `tmux capture-pane`.
118
133
@@ -385,6 +400,9 @@ The wrapper registers with the server, watches for @mentions, reads recent chat
385
400
|`jobs.py`| Job store — JSON persistence, status tracking, threaded conversations |
386
401
|`rules.py`| Rule store — JSON persistence, propose/activate/draft/archive/delete with epoch tracking |
387
402
|`summaries.py`| Per-channel summary store — JSON persistence, read/write with 1000-char cap |
0 commit comments