Summary
Problem Statement
The "set state" MCP tool that updates issue status is currently only invoked during swarm mode orchestration. Non-swarm looms (standard single-issue workflow via il start) do not update issue state through the MCP, making their progress invisible to any Kanban-style project view.
Enhancement Goal
Extend set-state MCP calls to the standard loom lifecycle (start, finish, cleanup, and potentially agent pipeline stages) so that every issue managed by iloom — not just swarm children — has its tracker state kept in sync. This lays the groundwork for project-wide Kanban board visibility.
The agent also flagged a few clarifying questions for you:
- Which lifecycle transitions should trigger set-state calls for non-swarm looms? (e.g.,
il start → in_progress, il finish → done, il cleanup → abandoned, or also agent pipeline stages?)
- Tracker scope — uniform across GitHub, Linear, and Jira from the start, or a subset initially?
- Kanban consumer — is this for the VS Code extension's existing board, a standalone dashboard, or both?
Want me to post this enhanced description to the issue tracker, or do you want to answer those questions first to refine it further?
Summary
Problem Statement
The "set state" MCP tool that updates issue status is currently only invoked during swarm mode orchestration. Non-swarm looms (standard single-issue workflow via
il start) do not update issue state through the MCP, making their progress invisible to any Kanban-style project view.Enhancement Goal
Extend set-state MCP calls to the standard loom lifecycle (
start,finish,cleanup, and potentially agent pipeline stages) so that every issue managed by iloom — not just swarm children — has its tracker state kept in sync. This lays the groundwork for project-wide Kanban board visibility.The agent also flagged a few clarifying questions for you:
il start→ in_progress,il finish→ done,il cleanup→ abandoned, or also agent pipeline stages?)Want me to post this enhanced description to the issue tracker, or do you want to answer those questions first to refine it further?