Small fixes and upkeep
12 of 15 tasks doneSee small fixes and routine upkeep together, without a delivery date.
Building
On track
10 of 19 delivered
See small fixes and routine upkeep together, without a delivery date.
You will be able to keep the remaining agent settings consistent across both machines.
Old setup copies can go once their results match the central version exactly.
You will be able to add more approved services after the current safety checks pass.
Sensitive utilities will offer limited, named actions instead of broad access to the machine.
Excluded skills can return after a review confirms that they handle secrets safely.
The strategic hinge (roadmap 2026-07-20, freeze 7b): rewrite the instruction surface to route by intent with per-harness generated bindings, migrate instruction units, enforce I3-S min-rev/opt-out (validator gap found in review), verify hub-only sessions per harness (Claude Code, Codex, Cursor), then park duplicate direct connections one agent at a time. Exit: one bearer inherits the Wave-A daily estate.
Slack, Google trio, Obsidian, Browserbase, Context7 equivalents self-hosted behind the hub. Network isolation for tool workloads lands here.
The gws wrapper re-homes to the cloud server, killing the last component that depends on the home PC being up.
Code and shell executors join behind a dedicated scoped auth design with per-operation permissions and time-boxed grants.
Agents on your Windows PC can use the same trusted tools hosted on your other machine.
Each agent sees only its assigned tools, and one faulty service cannot hold up the others.
You can rebuild the shared tool hub from its central records after a complete loss.
Both Windows agents can use the same selected tools while keeping separate identities.
You can update rules, skills, and safety checks once and send the right set to both machines.
Thirteen shared commands work in both agents, with dependable saved files for background work.
Both machines copy agent memory into separate central histories each night without triggering extra releases.
Control-plane spine: governance repo + write-back service, hub-meta server, phone-first governance UI, kill switch with durable tombstone, stable ID model. Makes the two north-star sentences real: one-paste onboarding, ten-second cuts.
Mohit's 2026-07-20 feedback after first use: create custom profiles, add/remove tools per profile, per-agent overrides and profile assignment, and one page showing EVERYTHING MyComposio serves (tools, skills, instructions). Turns the Wave-0 viewer into the real control surface.
Tools already on the cloud server but not yet behind the hub (hub MCP, Exa, episodic-memory) join the federation.