Used by developers at
Meta
Salesforce
Spotify
Huawei
Qualcomm
Atlassian
Databricks
Shell
AT&T
DoorDash
Bosch
- STEP 1AskDescribe the change. Or just say it out loud.
- STEP 2Read the planSee what it intends before anything moves.
- STEP 3ApplyTick the changes you want. Done.
How a change reaches your code
It plans before it writes
By default, you see the plan before a single file is touched. Confirm it, refine it, or send it back.
A diff, in your IDE
Changes come back as a unified diff in VS Code’s merge editor or JetBrains’ own diff viewer. The format you already read.
Accept selected changes
Every changed file gets its own checkbox. Keep the ones you agree with, merge parts of the rest. Never all-or-nothing.
You decide what it sees
Your open files go into the prompt. Add or remove any of them, so you know exactly what it’s working from.
It knows your codebase
Scans your repo so it can find the files that matter — and answer questions about code you’ve never read.
Two-way voice, built in
Talk to it, and it talks back. It reads the plan aloud so your eyes stay on the diff.
Native VS Code + JetBrains plugins
Real plugins — not an editor fork. Your keybindings, your settings, your diff viewer.
How do credits work? What are they for?
Credits are the currency used on Codebuddy to make requests to different AI models.
Each time you ask Codebuddy to do something, it costs a certain number of credits
depending on the model you're using for the main portion of the request.
Each time you ask Codebuddy to do something, it costs a certain number of credits
depending on the model you're using for the main portion of the request.