Prerequisites
- Java 21+ on PATH
- An agentic CLI installed and authenticated (e.g., Claude Code, Gemini CLI, Codex)
- An ACP-compatible IDE â JetBrains 2026.1+, Zed, VS Code, or any editor with ACP support
Install from Release
Download the fat JAR from the v0.4.0 release:
bud-acp-server-0.4.0-jar-with-dependencies.jar â the ACP agent
Install from Source
This produces:
bud-acp-server/target/bud-acp-server-*-jar-with-dependencies.jar
Create or edit ~/.jetbrains/acp.json:
Replace /path/to with the absolute path where you saved the JAR.
Restart your JetBrains IDE after editing the config.
Your First Project
- Open any project in IntelliJ
- Open AI Chat tool window
- Select âBudâ from the agent dropdown
- Type:
create a REST app called hello-api in /tmp
Bud will scaffold a complete Spring Boot REST project with:
GreetingController with GET endpoint
GreetingService with business logic
ProblemDetail error handling
- Working tests
- Maven wrapper
What You Can Ask
Bud understands natural language and routes your request to the right approach. Here are tested prompts organized by what Bud does with them.
Known patterns (instant, no LLM code gen)
These match one of Budâs 9 reference projects â Bud uses proven, working code directly:
Domain apps (LLM-expanded with real business code)
These have specific business entities â Bud scaffolds a base project and expands it with domain models, repositories, services, and controllers:
Edge cases (handled gracefully)
How It Works
When you send a message to Bud in AI Chat:
- JetBrains sends the prompt to Budâs ACP agent over stdio
- Budâs LLM classifier (Sonnet, running on your approved CLI) analyzes the intent â capabilities, domain entities, best-fit reference project
- The execution planner routes to the right tier:
- CACHE â matches a reference project, uses working code directly
- INITIALIZR â generates via start.spring.io (Boot 3.x, Gradle)
- EXPAND â starts from a reference project, then AI generates domain-specific code
- Tools execute deterministically â no LLM in the actual scaffolding. Your CLI is only used for classification and domain code generation.
- Results stream back through ACP to your chat window
The first prompt may take 30-60 seconds (CLI startup + classification + MCP server startup). Subsequent prompts in the same session are faster.