neuron-explorer
Steering-first neuron explorer for Qwen3.5-4B: push every MLP neuron, keep every rollout, browse the results
Start here How BootUI works Your application serves the console at /bootui/ and its JSON API at /bootui/api/**. The Vue UI is packaged inside the jar, so your build needs no Nod...
Developer toolsJava · JavaScriptGitHub @jduboisOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
The missing developer UI for Spring Boot and Quarkus!
Taken from the repository README
Loading the full README. The saved excerpt is shown below.
BootUI adds an embedded, local-only developer console to your application. It runs on Spring Boot 4 (servlet or
WebFlux) and Quarkus, serving the same Vue UI and REST contract (/bootui and /bootui/api/** by default,
configurable with bootui.path / bootui.api-path) from a shared,
framework-neutral engine — add the matching Spring Boot starter or the Quarkus extension and BootUI activates only in
local development.
Read the documentation at.Read the full README ↗BootUI adds an embedded, local-only developer console to your application. It runs on Spring Boot (servlet or
WebFlux) and Quarkus, serving the same Vue UI and REST contract (/bootui and /bootui/api/** by default,
configurable with bootui.path / bootui.api-path) from a shared,
framework-neutral engine — add the Spring Boot starter (one for both stacks) or the Quarkus extension and BootUI
activates only in local development.
Read the documentation at https://www.julien-dubois.com/boot-ui/.
BootUI 2.0 is available on Maven Central, with exact correlation, a runtime journal, Runtime Insights, run comparison, and optional Java-agent instrumentation. Follow the setup guide, read its known limitations, and share feedback in GitHub Discussions.
| Topic | Link |
|---|---|
| Setup | https://www.julien-dubois.com/boot-ui/setup |
| Features | https://www.julien-dubois.com/boot-ui/features |
| MySQL operational view | Feature guide |
| Properties | https://www.julien-dubois.com/boot-ui/properties |
| AI agents | https://www.julien-dubois.com/boot-ui/ai-agents |
| Command line | https://www.julien-dubois.com/boot-ui/cli |
| Sample app | https://www.julien-dubois.com/boot-ui/try-sample-app |
| Repository docs | https://www.julien-dubois.com/boot-ui/repository |
| Known limitations of 2.0 | Known limitations |
BootUI exposes a local, opt-in Model Context Protocol server so AI coding agents (GitHub Copilot, Claude Code, …) can run its advisors and read runtime diagnostics while fixing your code.
Install the BootUI skill in any Agent Skills-compatible coding agent:
npx skills add https://github.com/jdubois/boot-ui/tree/main/skills/bootui
The interactive installer detects supported agents and installs the canonical consumer skill. Native integrations are also available:
| Agent | Native installation |
|---|---|
| GitHub Copilot | gh skill install jdubois/boot-ui skills/bootui |
| Claude Code | /plugin marketplace add jdubois/boot-ui, then /plugin install bootui@bootui |
| Cursor | Find BootUI on Cursor Directory |
The Cursor and Claude Code plugins install the skill and configure the MCP server together. BootUI also pairs with Coffilot, a GitHub Copilot canvas extension that builds, runs, and scans your app from the GitHub Copilot App's side panel. See the AI agents guide for preview, configuration, and safety details.
The bootui CLI asks a running application one question and prints the answer, with one command per BootUI
diagnostic — the same set the MCP server exposes, projected mechanically from the same registry.
curl -fsSL https://www.julien-dubois.com/boot-ui/install.sh | sh
bootui beans --query dataSource
bootui hibernate scan --json | jq '.topFindings[]'
It needs no MCP client and no agent, prints exact JSON when piped, and exits 2 when a panel's own policy
declines the call and 3 when --fail-on <severity> finds a finding at or above that severity, so CI can branch on it. Windows has a PowerShell installer, and JBang works too — see the
command-line guide.
Licensed under the Apache License, Version 2.0.