Stop losing your breakpoints: Meet Breakpoint Bookmarks for VS Code

#vscode #python #webdev #javascript

If you've ever stopped mid‑debug to chase a different bug, you know the pain: you come back and all your carefully placed breakpoints are gone. You try to remember where they were, what conditions you had, which logs you set… and momentum dies.

I built Breakpoint Bookmarks to fix that. It lets you save your current breakpoints to a named “flow”, switch between flows instantly, and restore everything exactly where it was—conditions, logpoints, function breakpoints and all.

TL;DR — Install it, hit Save, and stop babysitting your breakpoints.

Quick demo

Save your current session

Load a saved flow

What it does

One‑click save & restore of all your active breakpoints (source & function)
Unlimited flows — create one per bug, feature, or customer issue
Works with anything VS Code can debug (JS/TS, Python, Java, C#, Go, Rust, PHP, Ruby…)
Friendly UI: a dedicated sidebar with inline actions (Save, Load, Edit, Delete)
Type‑safe & reliable: built in TypeScript, tested, and cross‑platform

Install (10 seconds)

From the Command Palette (Ctrl/Cmd+P):

ext install OmarDulaimi.breakpoint-bookmarks

Or via CLI:

code --install-extension OmarDulaimi.breakpoint-bookmarks

Marketplace page: https://marketplace.visualstudio.com/items?itemName=OmarDulaimi.breakpoint-bookmarks

Repo: https://github.com/omar-dulaimi/breakpoint-bookmarks

How to use it

1) Set up your breakpoints as usual (conditions, hit counts, logpoints, function breakpoints—go wild).

2) Open the Breakpoint Bookmarks view (Activity Bar → “Breakpoint Bookmarks”).

3) Click Save to snapshot your current session to a named flow.

4) Later, click Load on any flow to restore the entire session—exact lines, conditions, and messages.

5) Use Edit to tweak the JSON by hand (power users, this is for you).

6) Delete a flow when it’s no longer useful.

Pro tip: Keep a “Happy‑path” flow you can load anytime you need a clean baseline.

Settings you might care about

// Settings → search for “breakpoint bookmark”
{
  // Use relative paths so flows work across machines & teammates
  "breakpointBookmark.useRelativePaths": true,

  // When loading a flow, clear any pre‑existing breakpoints first
  "breakpointBookmark.clearPreviousBreakpoints": true,

  // Pick a custom folder for the saved JSON files
  "breakpointBookmark.saveLocation": ".vscode/breakpoint-flows"
}

Real‑world uses

Multiple parallel bugs — keep one flow per issue, jump between them in seconds.
Feature flags & envs — flows for “staging”, “canary”, “prod‑sim”.
Onboarding — hand new folks a “Debug 101” flow for the codebase.
Customer escalations — save the exact breakpoints used to reproduce a ticket.
Pairing & reviews — share a flow in the repo so everyone can follow the same trail.

What’s new lately

Function breakpoints are fully supported (alongside file/line breakpoints)
Cleaner sidebar UI with hover actions and a top‑bar Save button
Better Windows path handling and cross‑platform behavior
Backward‑compatible with older bookmark files

(Changelog lives in the repo if you like the gory details.)

Roadmap — tell me what to ship next

I have a few ideas cooking, but I’d rather build what you need:

Shared/team flows out of the box (auto‑discover in workspace)
Branch‑aware flows (auto‑switch based on current git branch)
“Save only changes since last load”
Diff/merge flows, and search across flows
CLI to automate flows in CI/repros
API for other extensions to read/write flows

Have a better idea? Open an issue or drop a comment — I read everything.

Issues & feature requests: https://github.com/omar-dulaimi/breakpoint-bookmarks/issues
Pull requests welcome: https://github.com/omar-dulaimi/breakpoint-bookmarks/pulls

If this saves you time ❤️

A star or review goes a long way. If it’s really helping your day‑to‑day, you can also sponsor development — even a tiny amount helps me ship faster and keep docs & fixes flowing.