Brunoborges Jdb Agentic Debugger
brunoborges-jdb-agentic-debugger is a Claude Code plugin for the Ship phase that lets your agent debug running Java JVMs in real time through JDB and JDWP.
by brunoborges · github.com/brunoborges/jdb-agentic-debugger
Let Claude attach to a running JVM with JDB so you can set breakpoints, inspect threads, and trace exceptions without leaving the agent chat.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install brunoborges-jdb-agentic-debugger@brunoborges/jdb-agentic-debuggerBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:brunoborges/jdb-agentic-debugger") and the paste-ready config with skillselion.get_install_config("plugin:brunoborges/jdb-agentic-debugger").
What it does
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. Solo builders 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.
Highlights
- 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
Why builders use it
Java stack traces and println debugging eat hours when you need thread state, breakpoint stops, or live variable values inside a running JVM.
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.
At a glance
- Type - Plugin in Development Tools.
- Adoption - 0 installs, 42 stars, 0 votes.
FAQ
Who is brunoborges-jdb-agentic-debugger for?
Solo 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.
Comments
Share how you use brunoborges-jdb-agentic-debugger, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.