Skip to main content

Public Roadmap

Travsr ships in themed phases, each a set of sprints with a clear exit criterion. This page reflects what is shipped today and what is next.

Phases​

PhaseThemeStatus
Phase 1MVP: CLI, SQLite, BFS, MCP stdioShipped
Phase 2Stability: VS Code extension, daemon + watcher correctnessShipped
Phase 3Full retrieval stack: PPR, Dijkstra execution paths, k-core, 0-1 knapsackShipped
Phase 4Language coverage: 16 languages via the Phase B plugin hostShipped
Phase 5Cloud Preview: hosted MCP SSE, cloud indexing, team reposIn progress
Phase 6Storage backend for very large graphs, PPR at scalePlanned

What is shipped today​

  • 16 languages parsed structurally by Tree-sitter (Phase A): TypeScript/JavaScript, Rust, Python, Go, Java, Kotlin, Scala, C#, Ruby, PHP, C, C++, Swift, Objective-C, and Dart.
  • Semantic call edges (Phase B). Native and automatic for TypeScript/JavaScript, Rust, and Python; installable per language via travsr lang install <lang> for the rest, each running in a sandboxed subprocess.
  • Live semantic resolution between commits (RFC-027). A save re-resolves only the changed region through the editor's language server or an unambiguous lexical lookup, so the graph follows edits without waiting for the next commit. Shipped for TypeScript/JavaScript, Rust, Python, Go, Dart, Swift, C++, Java, C#, Kotlin, PHP, C, and Objective-C; Ruby and Scala stay commit-gated.
  • Phase B plugin host. A two-transport architecture (in-process native plus sandboxed sidecar) with a per-language trust model across three sandbox tiers.
  • Full retrieval stack. BFS, Personalized PageRank, Dijkstra plus a λ-corridor for execution paths, k-core, BM25 lexical ranking, an optional cross-encoder reranker, and a 0-1 knapsack token-budget enforcer.
  • 28 MCP tools in a single-repo stdio session (17 in a global session, 7 read-only graph tools over SSE), including get_context, get_execution_path, get_graph_json, get_snippets, get_architecture_brief, get_subsystem_brief, and the read-only observability tools get_index_status, get_graph_health, and get_daemon_logs.
  • A PreToolUse guard and an architecture-rule CI gate. travsr guard redirects or denies a Claude Code text search the graph can already answer; travsr invariants checks declared dependency and cycle rules against the graph on every commit.
  • VS Code extension with a live Cytoscape graph panel plus Health, Synonyms, and Repos panels.
  • Multi-repo global registry: every travsr init registers a repo; one --global MCP server serves them all.
  • SSE server (travsr serve) for cloud and team deployments.

What is next​

  • Cloud Preview (Phase 5). Hosted MCP SSE endpoint, cloud-side indexing, and team repository support.
  • Prize-Collecting Steiner Tree for execution paths. get_execution_path uses Dijkstra plus a λ-corridor today. A real PCST is scoped for later and ships only if a benchmark shows it beats the current path search.
  • Storage for very large graphs (Phase 6). SQLite + WAL is the only backend today and has been sufficient for every target workload, so this is a ceiling question rather than a scheduled swap. Kùzu was once the planned answer and was dropped; if a second backend is ever needed, it will be chosen and designed fresh.

Feedback​

Open a GitHub Issue to suggest a feature or report a bug.

GitHub Issues