Start here
What is Brompter?
Brompter runs coding agents beside the app you are building. Each task keeps its own chat, terminal, and diff, so you stay in one window.
Brompter was DevChat. The local command is still devchat. You notice a bug in the running app, draw a box around it, and tell the agent what is wrong. The edit streams back while the same app reloads next to the chat. No alt-tab, no restating the screen in words.
When to use Brompter
- You want Claude Code, Codex, Cursor, or Gemini working on the repo you already have open.
- You want to review the diff before it lands, line by line, and send notes back to the same chat.
- You want a terminal, a browser, and a file editor in the same window as the agent.
- You want several chats in parallel, each on its own git worktree, without stashing.
Who it is for
Brompter is for people who already write code and want agents as leverage. It assumes you read diffs, care which branch a chat is on, and keep a workspace tidy. It is a power tool for that loop, not a no-code builder.
What Brompter is not
- Not a model. You bring the agent CLI you already pay for, or an API key.
- Not a git host. Worktrees, branches, and commits are real git on your machine.
- Not a hosted IDE. The app runs locally, including the desktop shell. Your repo stays on disk.
Next
Install the desktop app or the local widget, then walk through your first session. That page is the shortest path from a blank window to a shipped edit.