Roadmap
This is a living view of where Weaver is going, grouped by horizon rather than dates. Items move up a tier as they progress. It’s a direction, not a contract — priorities shift as the project (and the way people run agents) evolves.
▸ Recently shipped
- Claude Code hooks — coordination is now structural for Claude Code: an advisory warning before any edit that overlaps another live session, and automatic presence after every edit. See the hooks guide.
- Note lifecycle — notes have ids and
weaver note --update <id>supersedes stale learnings.
▸ Now — in flight
What’s actively being worked on.
- Docs & landing polish — homepage redesign, typography, and this roadmap.
- Real-world dogfooding — running Weaver on its own repo across Claude Code and OpenCode, folding the findings back in.
- Tighten cross-harness session identity — more reliable detection of distinct sessions across Claude Code, Codex, OpenCode, and Pi.
▸ Next — committed, soon
Lined up and likely to land in the near term.
- Hook coverage for more harnesses — bring the structural pre/post-edit coordination to other agents as their hook systems allow.
- More harness coverage — Cursor, Gemini CLI, and Aider recognized out of the box.
- Notes & activity search — query and filter notes and history instead of scanning the whole log.
- Dashboard & watch upgrades — a richer live view, with filtering by area or agent.
▸ Later — directional
Bets we’re interested in but haven’t committed to. Feedback shapes what makes the cut.
- Optional shared / remote commons — opt-in sync so agents on different machines can share context. The core stays local-first and serverless; this would be strictly additive.
- Harness-native packaging — ship Weaver as a Claude Code plugin / skill (and equivalents) for one-step setup.
- Smarter conflict advisories — suggest how to split overlapping work, not just flag the collision.
- Richer query layer — revisit a graph-style query over the commons, if demand warrants.
- Native Windows support — today Windows runs via WSL2; native binaries if demand shows up.
▸ Shape the roadmap
Weaver is open source and the roadmap is meant to be influenced.
- Have an idea or a pain point? Open an issue.
- Want something prioritized? 👍 the issue — reactions are a real signal.
- Want to build it? See Contributing. Changes land through pull requests.