architect: agent management redesign #21
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "architect/agent-management-redesign"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Sprint pitch: agent management redesign
Vision issue: #557
What this enables
Operators can hire agents by backend (
disinto hire anthropic,disinto hire llama --url ...) instead of inventing names and roles, and list all agents (disinto agents list) with backend, model, roles, and status in one table.The factory becomes self-describing: an operator who inherits a running instance can immediately see what agents exist, what backends they use, and what roles they fill.
Complexity
Risks
hire-an-agentmust keep working during transition (deprecation path)Cost
No new services, cron jobs, or formulas. Pure CLI/config refactor. ~230 lines new, some removed.
Recommendation
Worth it. High-value, low-risk adoption improvement. The current UX requires knowing name, role, and backend in the wrong order. Independent of all in-flight sprints.
Reply
ACCEPTto proceed with design questions, orREJECT: <reason>to decline.