Brunoborges Jdb Agentic Debugger
- 63 repo stars
- Updated February 27, 2026
- brunoborges/jdb-agentic-debugger
brunoborges-jdb-agentic-debugger is a Claude Code plugin that lets your agent debug running Java JVMs in real time through JDB and JDWP.
About
brunoborges-jdb-agentic-debugger is a Claude Code plugin that packages an agent skill for driving JDB—the Java Debugger CLI—against live or launchable JVMs. developers shipping Java APIs, Spring services, or CLI tools can ask the agent to attach with JDWP, plant breakpoints, walk threads, and read variable state when stack traces are not enough. It fits after you have a reproducible failure during backend work, pre-release testing, or first production incidents, when you want structured debugger commands instead of guessing from logs. You still need a JDK with jdb on PATH and a process started with debug flags. Complexity is intermediate: comfortable with Maven/Gradle run configs and JDWP ports. It complements IDE debugging by keeping the loop inside Claude Code for quick surgical sessions.
- Attach or launch Java processes over JDWP for agent-driven JDB sessions
- Set breakpoints, step execution, and inspect locals without a full IDE handoff
- Inspect threads, stack frames, and exception paths from natural-language debug goals
- Targets real-time diagnosis of running JVMs, not static log grep alone
- Single-plugin bundle focused on Java CLI debugger workflows for coding agents
Brunoborges Jdb Agentic Debugger by the numbers
- Data as of Jul 28, 2026 (Skillselion catalog sync)
/plugin install brunoborges-jdb-agentic-debugger@brunoborges/jdb-agentic-debuggerAdd your badge
Show developers this plugin is listed on Skillselion. Paste this into your README.
| repo stars | ★ 63 |
|---|---|
| Last updated | February 27, 2026 |
| Repository | brunoborges/jdb-agentic-debugger ↗ |
What it does
Let Claude attach to a running JVM with JDB so you can set breakpoints, inspect threads, and trace exceptions without leaving the agent chat.
Who is it for?
Best when you're maintaining Java or Kotlin-on-JVM backends and already run apps with remote debug enabled and want the agent to operate the debugger CLI.
Skip if: Skip if you're on non-JVM stacks, developers and only need static analysis, or environments where JDWP ports cannot be opened for security policy reasons.
What you get
You get agent-guided JDB attach, breakpoints, and inspection so you can confirm root cause and patch faster without bouncing between chat and a heavyweight IDE session.
- Agent-executed JDB session notes: breakpoints, stack walks, and variable snapshots
- Actionable diagnosis of the failing Java code path
- Repeatable attach/launch steps you can reuse in CI or local dev
By the numbers
- 1 plugin in bundle (pluginCount: 1)
- Repository brunoborges/jdb-agentic-debugger
- 42 GitHub stars at catalog ingest
Recommended Plugins
0xbigboss Linear CliLinear CLI built with Zig1
15195999826 LomomarketplaceLomo's Claude Code Plugin Marketplace1
1broseidon MarketplaceCurated collection of Claude Code plugins for fullstack development teams1
4rgon4ut Cc Zig LspZig LSP plugin for Claude Code4
708u TwigSimplify git worktree and branch management with configurable symlinks, change carrying, and cleanup.22
8avalon8 AvalonclaudemarketAvalon 的 Claude Code 插件市场How it compares
Agent skill for JVM CLI debugging, not an MCP media server or a generic linter.
FAQ
Who is Brunoborges Jdb Agentic Debugger for?
and small-team developers shipping Java applications who want Claude Code to run JDB attach, breakpoints, and inspection against JDWP-enabled processes.
When should I use Brunoborges Jdb Agentic Debugger?
Use it when a JVM bug needs live stepping, thread analysis, or exception breakpoints during backend work, pre-ship testing, or staging incident response.
How do I add Brunoborges Jdb Agentic Debugger to my agent?
Install the plugin from the brunoborges/jdb-agentic-debugger repository into Claude Code, ensure JDK jdb is available, and start or attach to a JVM with JDWP enabled before invoking the skill.