meta: Agents Roster AI Assistant — tracking issue #1216

New issue

Open

opened 2026-05-15 17:03:39 +00:00 by architect · 0 comments

architect commented

2026-05-15 17:03:39 +00:00

Collaborator

Feature: Agents Roster AI Assistant

An AI Assistant on the Agents Roster page that helps operators design fleets of agents from a plain-English description. The operator describes their goals; the assistant proposes a complete fleet (roles, system prompts, skills, tool permissions, MCPs). Operator reviews, edits, refines, accepts.

Locked decisions (v1)

Surface: sidebar panel on the existing roster page
Scope: new-fleet design only (improve-mode is a follow-up)
Templates: small canned set — solo dev, research team, support ops
Persistence: in-memory session store; survives no reload
Rate limiting: soft cap 20 refinements/session, no hard wall
Model tier: Sonnet for the assistant call; prompt-cached catalog block

Open questions (deferred — not blocking v1)

Multi-turn editing scoped to a single existing agent ("improve the reviewer specifically")
Session persistence across reloads (revisit before GA)
Cost surfacing / hard rate limit

Tickets

#	Title	Depends on
#1210	schema: roster-assistant proposal contract	— (blocks all)
#1211	be: catalog snapshot collector + `GET /roster/assistant/catalog`	#1210
#1212	be: `POST /roster/assistant/propose` endpoint + session store	#1210
#1213	fe: AI Assistant sidebar panel	#1210
#1214	be: assistant prompt + Claude call with structured output	#1210, #1211, #1212
#1215	fe: proposal preview, per-agent edit, diff, accept-to-roster	#1210, #1213

Dispatch order

#1210 — contract; blocks everything. Land first.
#1211, #1212, #1213 in parallel — once #1210 merges.
#1214 — once #1211 and #1212 merge.
#1215 — once #1213 merges.

Acceptance for the feature

Operator opens the assistant, types a description, gets a structured proposal in < 15s
Proposal has name, role, system prompt, model tier, skills, tool permissions, MCPs, rationale per agent
Operator can accept all, accept a subset, edit fields inline, or send a refinement
Refinements show a diff against the previous proposal
Nothing is written to the roster without explicit accept
Only catalog-resident skills/MCPs are proposed; unconfigured MCPs are flagged

## Feature: Agents Roster AI Assistant An AI Assistant on the Agents Roster page that helps operators design fleets of agents from a plain-English description. The operator describes their goals; the assistant proposes a complete fleet (roles, system prompts, skills, tool permissions, MCPs). Operator reviews, edits, refines, accepts. ## Locked decisions (v1) - **Surface**: sidebar panel on the existing roster page - **Scope**: new-fleet design only (improve-mode is a follow-up) - **Templates**: small canned set — solo dev, research team, support ops - **Persistence**: in-memory session store; survives no reload - **Rate limiting**: soft cap 20 refinements/session, no hard wall - **Model tier**: Sonnet for the assistant call; prompt-cached catalog block ## Open questions (deferred — not blocking v1) - Multi-turn editing scoped to a single existing agent ("improve the reviewer specifically") - Session persistence across reloads (revisit before GA) - Cost surfacing / hard rate limit ## Tickets | # | Title | Depends on | |---|---|---| | #1210 | schema: roster-assistant proposal contract | — (blocks all) | | #1211 | be: catalog snapshot collector + `GET /roster/assistant/catalog` | #1210 | | #1212 | be: `POST /roster/assistant/propose` endpoint + session store | #1210 | | #1213 | fe: AI Assistant sidebar panel | #1210 | | #1214 | be: assistant prompt + Claude call with structured output | #1210, #1211, #1212 | | #1215 | fe: proposal preview, per-agent edit, diff, accept-to-roster | #1210, #1213 | ## Dispatch order 1. **#1210** — contract; blocks everything. Land first. 2. **#1211, #1212, #1213** in parallel — once #1210 merges. 3. **#1214** — once #1211 and #1212 merge. 4. **#1215** — once #1213 merges. ## Acceptance for the feature - Operator opens the assistant, types a description, gets a structured proposal in < 15s - Proposal has name, role, system prompt, model tier, skills, tool permissions, MCPs, rationale per agent - Operator can accept all, accept a subset, edit fields inline, or send a refinement - Refinements show a diff against the previous proposal - Nothing is written to the roster without explicit accept - Only catalog-resident skills/MCPs are proposed; unconfigured MCPs are flagged

architect added the

area:agents

area:meta

type:meta

labels

2026-05-15 17:03:46 +00:00