Skip to main content

What's New

Recent additions to Travsr. For the longer-term plan, see the Roadmap.

travsr ui, enum members in the graph, and tighter MCP answers (v1.4.0)​

  • Upgrading from 1.3.0: run travsr init once in each repository. The index format changed (v3 to v4) because enum members are now graph nodes. An older index is not updated in place: the commit hook skips it until you rebuild, and travsr status warns you:

    warning: this index was built with an older version of travsr (format v3, current v4); run `travsr init` to rebuild it
  • travsr ui opens the graph in a browser. One command serves the VS Code extension's pages (Health, Graph, Callers, Dependencies, Blast radius, Execution path, Architecture, Context, Terminal and Repos) from the binary, on loopback by default. Browsing is read-only; the action buttons run daemon, reindex, fsck and connect only after a confirmation. See travsr ui.

  • travsr connect configures OpenCode and Kilo Code. It edits the project's opencode.json(c) or kilo.json(c) in place, keeps your comments, and writes the absolute path of the running binary. See travsr connect.

  • Enum members are graph nodes. Color.Red is now a variant:Color.Red node, so find_references on a member finds its use sites.

  • get_blast_radius takes max_files. The default is 500, and a cut list keeps the files nearest the change and ends with a note. A loose path or name says which files it resolved to, and a Rust mod x; names its child modules. The VS Code panel shows N+ when the list was cut.

  • find_pattern takes context. It shows up to 10 lines after each match (travsr pattern -A), and marks matches inside test code with [test].

  • Identifier lookups match by prefix. search_symbol and get_callers no longer return dispatch_tool_call for tool_call when a name that starts with it exists, so a real definition is not buried under loose matches.

  • get_snippets takes a path hint and names what it could not find. Each unresolved name gets its own note, and a repeated name renders once.

  • get_architecture_brief counts manifest-declared dependencies. Edges are tagged code, manifest or code+manifest.

  • get_graph_json honours token_budget in overview and drill-down modes, and the budget is charged for the JSON it returns.

  • MCP calls are checked against each tool's schema. A misspelled, missing or mistyped argument is rejected with a sentence naming it, instead of running the tool on an empty value. Responses are no longer cut off at 4 KB. A long-lived mcp --stdio server appends a note when the travsr binary on disk is a different build. See MCP tools.

  • Daemon replacement is safer. A client replaces a skewed daemon only from the binary path it runs, and any client may replace one whose binary was deleted. See travsr daemon.

  • Security. Dependencies were bumped for RUSTSEC-2026-0367, -0368, -0369, -0385 and -0386, and block-buffer to 0.12.1.

One-command setup, self-restarting daemon, and honest empty answers (v1.3.0)​

  • Upgrading from 1.2.1. The index format is unchanged. In a TypeScript or Python repository, run travsr init --force once to pick up the Next.js, path-alias, JSX and Python attribute-type fixes below; any repository that uses inheritance picks up the new inherited-method call edges the same way. If Kotlin is already installed, rerun travsr lang install kotlin.
  • travsr init sets up everything in one command. It detects the repository's languages, installs their language tools, indexes, traces calls before returning, connects Claude Code and Cursor, and starts the daemon to keep the index fresh. --semantic is now a hidden no-op, since init always traces calls. Every surface that reports a language's readiness (init, status, lang list, MCP notes, the VS Code extension) shares one check with five states, ready, needs_toolchain, unsupported_os, setting_up and failed, and each non-ready line carries one concrete next step. See travsr init and travsr status.
  • travsr status --verbose adds the counts line, each language's diagnostics and tool versions, and the Phase B warnings. travsr connect --print --json lists the AI tools found and whether each connects by itself or needs one step from you.
  • The daemon restarts itself after a binary upgrade. The CLI compares the daemon's reported version with its own on every terminal query, travsr mcp start-up and init, and restarts a mismatched daemon (an older one that reports no version counts as mismatched). travsr mcp also starts a daemon when none is running. See travsr daemon.
  • repos tells "index deleted" from "never indexed". travsr repos, repos_list and the VS Code Repos panel report indexed, index deleted or never indexed (or unknown for an entry an older binary wrote) instead of a single exists flag. --json rows gain a status field. See travsr repos.
  • Empty MCP answers say which kind of empty they are. get_callers and find_references tell an unresolved name apart from a known symbol with nothing calling it, and find_pattern answers [note: no matches] for a search that ran and found nothing, distinct from input it rejected. The get_context abstain message now says no symbol name matched, rather than that the query is not in the repo.
  • get_execution_path no longer guesses between ambiguous endpoints. A bare name with several definitions returns the candidate list and says which side is ambiguous, instead of reporting "no path found" about the wrong pair.
  • No more phantom references. Each Phase B run now retracts a file's earlier reference lines and scip caller edges before recording new ones, so a stale line no longer survives later runs, fsck and even a fresh init.
  • Resolution fixes. A Next.js tsconfig.json with compilerOptions.plugins no longer breaks TypeScript analysis; @/* and other paths aliases now resolve; a JSX element (<Foo/>) counts as a reference to the component; Python resolves a call through a type-annotated instance attribute (self.app.add_url_rule(...) with app: App); and a method inherited from a base class now produces a call edge.
  • Smaller fixes. A tool unpacked from a zip keeps its execute bit, which fixes Kotlin reporting "produced no symbols". The warm ask cache no longer returns a stale answer after the embedding sidecar restarts. The docs retrieval lane now respects the caller's RBAC scope. The VS Code extension no longer over-counts results when the index is behind, Show Execution Path draws only the route, and Objective-C .m/.mm files get code lens and hover.
  • Security. embed gc can no longer be made to delete a file outside .travsr/; a symlink at .travsr/embed.lock.info can no longer redirect a lock-status write; and the share tarball installer now verifies a sha256 sidecar before extracting anything.

The live lane reaches C, Objective-C, PHP, and Kotlin​

  • Live resolution between commits now covers four more languages. An edit in C, Objective-C, PHP, or Kotlin resolves through the live editor server (clangd, Intelephense, kotlin-language-server) the moment you save, instead of waiting for the next commit to re-run the batch analyzer. They join TypeScript, JavaScript, Python, Rust, Go, Dart, Swift, C++, Java, and C#, which already had it. Ruby and Scala are deliberately left out: ruby-lsp cannot resolve an untyped receiver, and Scala's language server needs an sbt compile first, so edits in those two still wait for the next commit.
  • A round of cross-language edge-resolution fixes landed alongside it: several languages were dropping a whole file's edges on save when a real definition had no structural counterpart to unify onto (affecting Dart, Scala, Objective-C, Go, TypeScript, and Swift), and a few analyzers (C, C++, Go, Scala) emitted definitions with no counterpart at all, which are now handled the same way. A C or PHP project below the repository root is no longer skipped, and a save with no live lane attached no longer loses more edges than the edit itself removed.

travsr guard, travsr invariants, and two architecture-level MCP tools​

  • travsr guard, a Claude Code PreToolUse handler. It runs at the moment an agent reaches for Grep, Glob, Read, or a shell text search, and either attaches the Travsr call that answers the same question (advisory) or refuses the read and names the replacement (strict). Fail-open by construction: a missing index, an unreadable payload, or a missed deadline all let the original call through. Turn it on with travsr init --guard or travsr connect --guard. See travsr guard.
  • travsr invariants, an architecture-rule CI gate. It reads architecture-invariants.json from the repository root and checks dependency and cycle rules against the graph, exiting non-zero on a violation. A rule naming a component the graph no longer has is reported as violated rather than silently skipped. See travsr invariants.
  • get_architecture_brief and get_subsystem_brief, two new MCP tools. The first returns a whole repository's components, weighted dependency edges, layering, and cycles; the second walks the call graph from one entry point and returns the call spine by depth, who calls in, and every call that crosses the component boundary. Both share the same definition of "component" get_repo_map uses, so the three tools cannot disagree with each other. See get_architecture_brief and get_subsystem_brief.
  • The Android SDK is granted automatically to Java and Kotlin analyzers, but only for repositories that build with the Android Gradle Plugin, so a Gradle or Maven build that never touches Android pays nothing for it. The SDK location comes from ANDROID_HOME, ANDROID_SDK_ROOT, or the IDE's default install location, never from repository content such as local.properties. A degraded analyzer run now says why in travsr init and travsr status. See Installation.

Bundled TypeScript, JavaScript, and Python analyzers, and honest partial status (v1.1.1)​

  • TypeScript, JavaScript, and Python cross-file analysis works in an installed binary. Their analyzers had never shipped in a release: outside a source checkout those three languages got structural edges only, while travsr lang list reported them active. The release now carries a travsr-lib/ directory beside the binary with both analyzers bundled, and every installer extracts it. After upgrading, run travsr init --semantic --force once in each TypeScript, JavaScript, or Python repository to pick up the new cross-file edges. See Installation.
  • A failed analyzer is reported instead of reading as complete. An analyzer that ran and failed now downgrades travsr status and travsr init to semantic: partial (incomplete: <lang>) and names the analyzer, instead of printing semantic: complete.
  • travsr lang install only claims what it has checked. Its success line now comes from actually resolving the analyzer; when the bundled one is missing it says so and gives the reinstall remedy, and lang list and lang detect report partial for it. See travsr lang.
  • travsr lang status <language> works. status is an alias of list, which now takes an optional language filter and refuses an unknown language by name.
  • The Phase A pyright pass is gone. It never produced an edge and cost a subprocess per Python file. Python's cross-file analysis is unaffected.

Live resolution between commits, and log.level (v1.1.0)​

  • Upgrading from 1.0.0: run travsr init once in each repository. The index format changed, and an older index is not updated in place: the watcher and commit hook skip it and queries keep answering from the old graph until you rebuild. travsr status warns you:

    warning: this index was built with an older version of travsr (format v2, current v3); run `travsr init` to rebuild it
  • Live semantic resolution between commits (RFC-027). A save used to drop the file's committed semantic edges and rebuild only the lexically unambiguous subset. Definitions an edit leaves byte-identical now keep their committed edges, and only the changed region is re-resolved. See Architecture.

  • The daemon's log level is a setting. log.level (error, warn, info, debug, trace; default info; env TRAVSR_LOG_LEVEL) is managed with travsr config get/set/unset/list. RUST_LOG still wins when set. See travsr config.

  • JavaScript cross-file analysis without a tsconfig. A CommonJS or plain JavaScript repository with no tsconfig.json used to produce zero semantic edges; Travsr now synthesizes one.

  • Jest and Vitest tests are indexed as tests. describe, it, and test callbacks become test and suite nodes, so get_context and ask file them under tests instead of letting them take the top slot.

  • find_references and get_callers agree. Both read the same recorded occurrences, get_callers no longer truncates at 4 KiB, and two definitions sharing a name are disambiguated instead of collapsed. See find_references and get_callers.

  • travsr --version reports the bare version. The +<shortsha> build suffix is gone from both the CLI and MCP serverInfo.version.

travsr ask answers questions about Travsr, and elevated languages stop asking permission​

  • travsr ask handles questions the graph cannot answer. "What is this repo written in?" used to match "repo" against symbol names and return a screen of hits that looked like an answer. Questions about Travsr itself, or about the repository as a whole, are now recognised before retrieval and answered in place; a repository-composition question runs lang list and an index question runs status. It is strict in one direction on purpose: anything the catalogue cannot fully account for still goes to retrieval, because a confident wrong answer to a code search is worse than a missed meta question. See travsr ask.
  • travsr ask --examples and --cmds. The first lists the question shapes Travsr can answer, filled in with the most depended-upon real symbols from your own index, so every line runs as printed. The second prints the whole command surface, subcommands included, grouped by what each is for. Both are checked against the CLI definition at test time, so neither can advertise a command that does not exist.
  • Elevated languages no longer ask for approval. Java, Kotlin, Scala, and C# required a per-user approval, an approver handle, a justification, and a host allowlist, before they could be installed. That gate is gone for local use and travsr lang approve is removed with it. The runtime isolation policy is byte-for-byte what it was; only the human approval moment went away. See Installation.
  • travsr connect writes MCP wiring only; the rules file is opt-in. The always-on rules block is re-read on every turn of every conversation, and it had grown to roughly 567 tokens per turn, competing with your own rules for attention. Most of it named which tool answers which kind of question, which the MCP client already sends: tools/list hands the model all 28 tool names and descriptions before the conversation starts. What remains ships behind travsr connect --rules. See travsr connect.
  • travsr lang list shows what you can act on. The PACKAGE column (npm names that no longer install anything) and the SANDBOX column (an internal tier) are replaced by a THIS REPO column that mirrors the per-repo gate exactly, so a language can no longer read "active" while full analysis is off for the repo in front of you. Installing a language inside a repo is itself the consent signal for that repo. See travsr lang.
  • Consent-gated unsandboxed analysis on Windows. Java (Gradle) and Scala (sbt) fork workers that cannot run inside the Windows isolation layer. travsr lang allow-unsandboxed <language> records a one-time, per-language, machine-local permission to run them with your own privileges instead; without it they are skipped honestly rather than producing a silent zero-node run. The child starts from a cleared environment, so GITHUB_TOKEN, AWS_*, SSH_*, and NPM_TOKEN never reach the build tool.
  • Live per-language progress during cross-file analysis. travsr init used to print Finalizing and then block with nothing on screen, so a JVM cold start looked like a hang. Each language now reports as it starts and finishes, with the timeout quoted only when something currently running is actually bounded.
  • Struct and class fields are addressable. Fields are now graph nodes in twelve languages, and a field read surfaces in find_references as a real path:line site on its own ref/field edge kind, so field use sites are visible without polluting the call graph that get_callers and get_blast_radius traverse.
  • travsr embed reindex --rebuild. Re-embeds the whole index from scratch, for use after switching models when older vectors may be inconsistent with newer ones.

Observability tools and a sidecar version contract​

  • Three read-only observability MCP tools. The MCP surface could answer questions about your code but not about the index those answers came from, so an agent could not tell "there are no callers" from "the graph cannot see them yet". get_index_status reports freshness, counts, per-language Phase B state and semantic readiness; get_daemon_logs returns recent daemon entries, severity-filtered and redacted; get_graph_health reports ghost paths, orphan edges and lexical parity without ever mutating anything.
  • Sidecar version floors. Travsr spawns external binaries that version independently, and install correctness used to be judged by file presence alone, which never flips false when a better release ships. A cached sidecar three releases behind ran anyway and failed with a cryptic downstream error. There is now a hard, offline compatibility floor: a below-floor sidecar is refused at spawn with the reinstall command named, and travsr status, travsr embed status and travsr lang list all end with a sidecars: block showing what is installed. See Sidecar health.
  • Exact search mode for search_symbol. Narrow a noisy name to its exact matches instead of wading through fuzzy ones.

16-language coverage and get_snippets​

  • get_snippets MCP tool. Kind-aware code retrieval that returns the source of matched symbols directly, so an agent can read implementations without a second round trip. This brings the core MCP query surface to 12 tools (21 in single-repo stdio, counting the synonym_* and repos_* management tools).
  • Swift, Objective-C, and Dart. Phase B semantic indexers shipped for Swift (travsr-swift-index-emitter), Objective-C (travsr-lang-objectivec, macOS only), and Dart (travsr-dart-index-emitter), bringing structural coverage to 16 languages.
  • Phase B plugin host. Every non-built-in language now runs through a sandboxed plugin host with a two-transport architecture (in-process native or external sidecar) and a per-language trust model. Install any of them with travsr lang install <lang>.

Dynamic synonyms and new sidebar panels​

  • travsr synonym CLI. Add, remove, and list query-time synonym pairs from the terminal. Synonyms expand search terms at query time, searching billing also hits nodes tagged payment and invoice. See travsr synonym.
  • Synonyms panel. Manage synonym pairs visually in VS Code without touching the CLI. See Synonyms Panel.
  • Languages panel. Shows which languages are indexed in the current repo and lets you install language tools with one click. See Languages Panel.
  • Repos panel. Lists all repos in the Travsr registry with live active/stale badges and a one-click prune button. See Repos Panel.
  • Graph Stats panel. Shows node count, edge count, schema version, DB size, and last-indexed time at a glance. See Graph Stats.

Visual graph panel and get_graph_json​

  • Visual graph panel. Open the Cytoscape.js graph panel from the command palette with Travsr: Show Graph (Cmd+Shift+G). It renders the live code graph for a symbol and lets you click through dependencies and callers. See VS Code features.
  • get_graph_json MCP tool. Returns a subgraph as raw node and edge JSON rather than token-budget-trimmed prose. It backs the graph panel and is useful for custom integrations and CI tooling. See the tool reference.