Back to browse
GitHub Repository

A VS Code extension that visually manages your code jump history

1 starsTypeScript

Code Jump Tracker – Never get lost after "Go to Definition" again

by tominaga-h·Mar 6, 2026·3 points·1 comment

AI Analysis

●●SolidSolve My ProblemNiche Gem

Sidebar history stack for 'Go to Definition' jumps when VS Code's native back button goes blind.

Strengths
  • Addresses a genuine friction point in code navigation that VS Code's native history doesn't solve visually.
  • Smart auto-tracking excludes small cursor movements, capturing only meaningful jumps (10+ lines or cross-file).
  • Dual sidebar views (History Log and File Group) plus manual pinning give flexible navigation strategies.
Weaknesses
  • Solves a problem already partially addressed by VS Code's native breadcrumb trail and Go Back button.
  • No evidence of competitive advantage over similar tools like VS Code's Timeline or other jump-stack extensions.
Target Audience

Code reviewers and developers working in large codebases who frequently use 'Go to Definition' to trace logic.

Similar To

VS Code Breadcrumbs · Code Time (WakaTime) · GitLens breadcrumb trail

Post Description

Hi HN,

I build a VS Code extension called Code Jump Tracker. https://github.com/tominaga-h/code-jump-tracker

I created this because I was constantly getting lost in large codebases during code reviews. I use "Go to Definition" (F12) a lot to trace logic. While VS Code has a native "Navigate Back" shortcut, it operates blindly—you can't see your stack history, making it hard to jump back to a specific file after exploring multiple branches.

Code Jump Tracker solves this by acting like `pushd/popd` for your editor.

Key features: - Auto-tracking: Automatically logs your jumps (Go to Definition, Outline clicks) into a clean, native-looking Webview table in the sidebar. - Manual Pinning: Found a core function you need to revisit? Pin it. It adds a persistent marker icon to your gutter. - Unique Locations: Keeps a deduplicated list of your visited symbols. - Persistent: State is saved per-workspace using `workspaceState`, so your history survives editor restarts.

I built the UI using VS Code's native CSS variables within a Webview to ensure it perfectly matches your theme and aligns columns beautifully (something the standard TreeView couldn't do well).

I'd love to hear your feedback, bug reports, or feature requests!

Similar Projects

Productivity●●Solid

DryCast – Never run outside to save your laundry from rain again

The Drying Core™ is a neat, physics-forward idea — it uses vapor pressure deficit, wind desiccation, solar irradiance and dew-point prediction to produce a single drying score and actionable windows. I like the fabric-specific timing, on-device processing and low-latency rain alerts/widgets; the missing piece is hard validation data and regional coverage limits (WeatherKit dependence), which will determine if this is indispensable or just clever.

Big BrainNiche Gem
AwkwardPanda
104mo ago