Loom (VS Code Extension) Roadmap
Last Updated: 2026-07-02 Tier: 1 (see workspace AGENTS.md "Portfolio Tiers") Tracking Issue: https://gitlab.flexinfer.ai/services/loom/-/issues/21
Current Status
Loom is the VS Code extension for MCP context management: platform config sync
across six agent platforms, server health monitoring, skills browser,
agent-context views, and — since v1.2.0 (released 2026-06-27) — the loom-core
flightdeck surface (Stall Board + Context Ledger), a weaver economics row in
the Sync Dashboard, expanded mills detail panels, and a hub health-divergence
banner. The last-20 commit window (git log origin/main -20) shows work
arriving in bursts around loom-core surface releases: quiet 2026-05-20 →
2026-06-27, then the v1.2.0 burst, then CI template onboarding merged
2026-07-02 (last activity). Backlog groomed 2026-07-02: the nine 2026-03-04
OpenAI Responses program issues (#12–#20) targeted loom-core internals and
were closed here as misfiled (tracked in loom-core #63).
- Plan store:
plan-workspace-portfolio-refresh-2026-h2-roadmaps-quality-baselin-f3db23(active cross-repo plan) - Deployed: not deployed — VS Code extension shipped as a VSIX, runs local-only against the user's loom daemon/hub
- CI: platform/gitops node template family (onboarded 2026-07-02); default-branch pipeline success 2026-06-27 at the 2026-07-02 baseline capture
Now
- Post-v1.2.0 stabilization; keep the newly onboarded node CI template green (#21, P2)
Next
- Downstream loom-core golden contract fixtures tracked in CI (#21)
- Webview hardening: reduce inline HTML/JS debt in release-critical panels (#21)
- Release gates (docs, coverage, package, publish) aligned with the shipped v1.2.x surface (#21)
Later
- Parity overview: fleet, health, tasks, memory, presence, and stream promoted into one shell
- Search capability metadata to replace hardcoded tool-family assumptions
Backlog
Full backlog: P1 issues · P2 · P3 · Milestones