Use case
CapyBro for developers
AI text editing that lives in your IDE, terminal, and Git client — not in yet another browser tab.
You already context-switch enough. CapyBro puts an AI rewrite, fix, translate, or explain action on a global hotkey that fires inside VS Code, JetBrains IDEs, Windows Terminal, your Git GUI, Slack, and GitHub in the browser. Wrap a commit message, polish a README, turn a stack trace into a plain-English question, or translate a Jira ticket — without leaving the window you're in. And because there's a local Ollama mode, your proprietary code never has to touch a cloud API.
Where developers use it every day
Better commit messages and PR descriptions
Select your rough draft in the commit box or PR template, press the hotkey, and a prompt like "rewrite as a conventional commit" or "summarize this diff as a clear PR description" turns it into something your team will actually read. Works in the VS Code SCM input, GitHub Desktop, and the GitHub web editor.
Docstrings, comments, and README polish
Highlight a function comment or a paragraph of your README, and have the AI tighten it, fix grammar, or rewrite it for a non-expert audience. Markdown stays intact. The same hotkey works in the editor and in the GitHub web UI when you edit docs inline.
Turn errors into questions
Paste a stack trace or a cryptic compiler error, run an "explain this error and likely cause" prompt, and get a plain-English starting point before you even open a search engine. Keep it local with Ollama when the log contains internal paths or secrets.
Translate tickets, docs, and chats
Working on an international team? Select a Jira ticket, a Slack message, or a chunk of foreign-language documentation and translate it in place — any language pair your model supports, without copy-pasting into a separate translator.
Prompt recipes for developers
Create these once in Settings → Prompts and trigger them from the prompt menu (Ctrl+Shift+Q). Each can pin its own model.
Rewrite the following as a Conventional Commits message: a concise type(scope): subject line under 72 chars, then a blank line and a short body explaining why. Keep it in English.
Explain this error message in plain English: what it most likely means, the 2–3 most common causes, and the first thing to check. Be concise.
Write a clear, concise docstring/comment for the selected code. Describe what it does and its parameters, not how it works line by line. Match the language of the surrounding code.
Rewrite the selected technical text so a non-developer stakeholder can understand it. Keep it accurate, drop the jargon, keep it short.
Developer FAQ
Does CapyBro work inside VS Code and JetBrains IDEs?
Yes. CapyBro uses a system-wide hotkey and the Windows clipboard, so it works in the editor pane of VS Code, all JetBrains IDEs (IntelliJ, PyCharm, Rider, WebStorm), Visual Studio, Sublime, and Notepad++. Select text, press the hotkey, the rewrite lands in place.
Can I keep proprietary code from going to a cloud AI?
Yes — switch to Ollama mode. The AI then runs locally on your machine with zero network calls, so source code, logs, and secrets never leave your computer. Use OpenRouter for everyday non-sensitive text and Ollama for anything confidential.
Can different prompts use different models?
Yes. Each prompt can pin its own model — for example a fast cheap model for commit messages and a stronger model for explaining errors. The Pro model-switch hotkey also cycles your pinned models mid-task.
Will it mangle my Markdown or code formatting?
The AI edits the text you selected and pastes the result back; it doesn't touch anything you didn't select. For Markdown, a prompt that says "preserve Markdown formatting" keeps headings, lists, and code fences intact.
Put AI on a hotkey in your dev environment
Free, open-source, ~48 MB. Bring your own OpenRouter key or run fully local with Ollama. Works in every Windows app you already code in.