Hey Product Hunt. I’m building GhostMap. I built it because TODO and FIXME comments kept failing me in real projects. They are fast to write, but after a few weeks they often stop being useful. A comment says “fix retry logic,” but not why it matters, whether it is still open, what code region it belongs to, or what risk it was supposed to capture. GhostMap is a VS Code extension that turns structured @ghost annotations into a navigable active-file tree. The goal is simple: Keep developer context inside the code, but make it structured enough to actually use later. What you can try today: Ghost Tree for the active file Structured @ghost annotations Named anchors like #payment-retry Range anchors with @ghost start and @ghost end Status and description fields Snippets for faster annotation Support for 19 languages GhostMap is still pre-1.0. Current limits: It maps the active file, not the whole workspace yet. Some language-specific symbol edge cases are still being cleaned up. Block and JSDoc comments are not the main @ghost syntax in V1. Commercial/company/production use requires authorization. I’m not trying to replace issue trackers. Some work belongs in GitHub Issues, Linear, or Jira. GhostMap is for code-local context: the notes, risks, decisions, regions, and work markers that are only useful because they live next to the code they describe. I’d love feedback from developers who already use TODO Tree, Better Comments, VS Code Outline, or their own TODO convention. Main question: Would structured annotations fit your workflow, or should this stay closer to normal TODO comments?

GhostMap

Structured annotations that live inside your code

Structured annotations that live inside your code