Roadmap

V1 is shipping.
V2 is the engine direction.

GhostMap V1 is a focused tool for supported VS Code workspaces – per-file Ghost Tree and local cache, no workspace-wide indexing yet. V2 is the workspace indexing engine direction; future enterprise-oriented integrations on top of it are sketched as a future direction, not a shipped product.

V1 - Available now

The foundation.

V1 is free for personal, educational, and evaluation use and works locally in supported VS Code workspaces, without an account.

Ghost Tree shipped

Live symbol map of any file. Classes, functions, interfaces - organized by real code structure, not folder names.

Ghost Ranges shipped

Named code sections that own everything inside. The cleanest way to mark a refactor, a migration, or a hot zone.

Ghost Anchors shipped

Contextual (attaches to nearest symbol) and named (independent node). Both carry description and status.

Ghost Index shipped

Loading engine that persists the tree between sessions. Open a file: the tree is there instantly.

Ghost Engine shipped

Local language extraction for 19 supported languages, with quality tiers shown in the support matrix.

Diagnostics shipped

Unclosed ranges, detached anchors, invalid status, malformed syntax - caught as you type with one-click fixes.

V2 - Vision (not yet shipped)

The next layer.

V2 builds on V1's model. The same Ghost Tree, the same vocabulary - extended with a workspace-wide indexing engine and future Enterprise roadmap capabilities for teams. Everything below is planned, not available today.

V2 Indexing Engine planned, not shipped

V1 indexes the active file and caches the result per document. V2 is planned to add a workspace-wide Ghost Index v2, filesystem watching, and background validation so the active-file experience stays responsive. Same Ghost Tree, broader scope.

Status: design + skeleton branches only. Not in any shipped 0.5.x.

Language pack expansion separate workstream

19 languages ship today. A separate workstream scopes roughly 20 more (Kotlin, Swift, Haskell, OCaml, Lua, R, Bash, SQL, ...). New languages will only be advertised here after parser packaging, query checks, and fixtures prove they are reliable enough to graduate from "planned" to "supported".

Status: roadmap. Runs in parallel with the V2 engine, not inside it.

Ghost Comments planned, not shipped

In V1, @ghost annotations live as comment lines in your source code. In V2, they move out of the file entirely - stored in the Ghost Index - and VS Code renders them as invisible overlays. Your code stays clean. A migration engine converts existing V1 annotations automatically.

Ghost Threads planned, not shipped

Planned conversations tied to a specific block of code. Not a global chat - a focused thread attached to exactly the function, class, or Ghost Range it's about. Decisions, open questions, and architectural rationale stay where they belong. Any service integration would require separate consent before shipping.

Ghost Graph planned, not shipped

Visual maps tracing how code flows: a variable declared here, used there, passed to this function, returned from that one. Ghost Graph follows the path from definition to last usage - across files - and renders it as a navigable graph. Built for understanding unfamiliar code fast.

Agile integration enterprise – future, not shipped

A future Enterprise sketch: status changes in GhostMap could flow to Jira / Slack and other trackers, sprint timelines could surface in the Ghost Tree as urgency signals, and a review pipeline could update the relevant anchor. None of this is implemented today, and any integration with server services would require its own privacy notice and consent before it ever ships.

AI descriptions & suggestions enterprise – future, not shipped

A future Enterprise sketch: AI-generated descriptions for undocumented symbols, Ghost Range suggestions on dense files, and context-aware reminders sourced from Ghost Threads. None of this is shipped, and no AI runs in any current GhostMap version. Any such feature would be opt-in and disclosed before release.

V1 → V2 Migration

Your V1 annotations are safe.

When V2 ships, GhostMap will include a migration engine that converts existing @ghost comment lines into invisible Ghost Comments stored in the Ghost Index. The conversion is automatic. Your code gets cleaner; your annotations stay intact.

The V2 Ghost Engine will be a superset of V1 - same syntax, same vocabulary, same tree model. Every concept you learn today carries forward.

Start with V1 today.

Free for personal, educational, and evaluation use. VSIX install today; Marketplace planned; Open VSX planned.

Install – Local VSIX

V1 is shipping.V2 is the engine direction.