Future Trajectory

Roadmap

Weaver's development follows a phased plan: foundation and safety harness first, then deeper syntactic and semantic intelligence, then the plugin ecosystem and agent workflow layers. Items marked Planned are not implemented yet; scope and timing may shift.

Phases 1–2: Complete (foundation, core MVP, safety harness)
Phase 3: In progress (syntactic & relational intelligence)

Phase Progress

1
Foundation & tooling
Complete
2
Core MVP & safety harness
Complete
3
Syntactic & relational intelligence
Active
4
Sempai query language
Early
5
Plugin ecosystem
Early
6
Agent workflows
Early
7
Jacquard (cards-first symbol context)
Planned
1

Near Term

Phase 3: Syntactic & Relational Intelligence

In Progress

CLI Discoverability & Help Surfaces

Phase 3.2

Making configuration and operation help directly discoverable from the CLI. Includes visible global flags (--config-path, --daemon-socket, --log-filter), operation-level --help, and actionable error messages with valid-alternative listings.

  • Short help on bare invocation
  • Operation-level --help
  • Domain/operation enumeration
  • Edit-distance typo suggestions
In Progress

Actionable Error Responses

Phase 3.x

Standardising error output across the CLI: client-side domain validation before daemon startup, valid-operation alternatives for typos, and a consistent three-part error template (problem, alternatives, next command).

2

Mid Term

Phases 4–7: Sempai, Plugins, Agent Workflows, and Jacquard

Planned

Sempai Query Language

Phase 4

A Semgrep-compatible structural query language built on Tree-sitter. Delivers observe query for pattern-based code search, with YAML rule files and a one-liner DSL. The Tree-sitter backend handles metavariable unification, ellipsis matching, and bounded traversal.

Planned

Capability-First Plugin Ecosystem

Phase 5

Plugins declare capabilities (rename-symbol, extricate-symbol, extract-method) and the daemon routes operations to the correct provider per language. Plugin processes run in sandboxed IPC sessions with authenticated envelopes. Initial providers: Rope (Python) and rust-analyzer (Rust).

Planned

Jacquard: Cards-First Symbol Context

Phase 7

Small, structured "symbol cards" and bounded graph slices exposed as observe operations (get-card, graph-slice). Cards carry signature, doc comments, decorators, and LSP-enriched metadata. Graph slices use typed edges (call, import, config) with explicit budgets (max_cards, max_edges, max_estimated_tokens). History diffs over recent commits use probabilistic symbol matching.

observe get-card observe graph-slice Budgeted Traversal JSONL
3

Long Term

Directional — scope and timing subject to change

Interactive Approval Mode

A future weaver act <operation> --interactive flow that presents lock-failure diffs and diagnostics for explicit human approval or rejection before write operations continue. Timeout and non-interactive environments fail closed.

Directional

Project Onboarding

A future weaver project onboard command that orchestrates existing Weaver components to generate a deterministic PROJECT.dna summary artefact from repository metadata and analysis outputs.

Directional

Symbol History Diffs

Time-travel diffs for graph slices over recent commits, with probabilistic symbol matching across renames, moves, and splits. Part of the Jacquard extension.

Directional

Editor Integration

Native editor plugins (VS Code, IntelliJ) that surface Weaver's observe and verify operations in the editor UI. Currently a future goal — Weaver integrates with language servers but does not yet ship its own editor extensions.

Directional

Help Shape the Future

Weaver is open source. Our roadmap is driven by community needs. If you're building AI agents or specialized dev tools, we want your input on these priorities.