Breeze Code

Code at blazing speed. Turn ideas into reality.

A free, featherweight code editor for Windows. Say what you want in plain words, then watch Claude Code, Codex, Antigravity or a local model build it, live, right next to your code.

Download for Windows  ·  Website  ·  FAQ  ·  Report a bug

Why · Agents · Multi-agent · Features · Getting started · Configuration · Installer · How it fits together · Team · License

Why Breeze Code

Watch every move Every file read, edit and command an agent makes streams into the chat as it happens, tagged with who did it. No black box.

Bring the agent you already use Claude Code, Codex, Antigravity, or a local model through Ollama, LM Studio or any OpenAI-compatible server. Swap any time.

Light and free No plans and no credits. You only pay if you pick a paid agent. A local model runs with zero cloud.

Yours stays yours Files stay on your PC, API keys and sign-in tokens are encrypted by the Windows keychain, and updates ask before downloading.

Bring your own agent

Breeze finds the coding agents already installed on your computer and signs in with their own accounts. Pick a default, then set its model and effort from its chip in the agents panel.

Agent	How Breeze talks to it	Plan usage in Settings
Claude Code	The claude CLI	Tokens this month, plus live 5-hour and weekly limits
Codex	The codex CLI	Tokens this month, plus its plan window
Antigravity	Antigravity's agent service	Not reported by Antigravity
Local model	Ollama, LM Studio or any OpenAI-compatible server	No limit, it runs on your PC

Several agents, one prompt

@mention agents from different companies in a single prompt and each takes its piece. They call dibs on their files first, you settle any overlap, and then they build side by side.

flowchart LR
    P["Your prompt<br/>@Claude front end<br/>@Codex backend"] --> S{"Breeze splits<br/>the task"}
    S --> C["Claude claims<br/>src/ui/, index.html"]
    S --> X["Codex claims<br/>server/, package.json"]
    C & X --> O{"Overlap?"}
    O -- "yes" --> Y["You pick<br/>who gets it"]
    O -- "no" --> B
    Y --> B["Both build<br/>side by side"]
    B --> L["One chat,<br/>every line tagged"]
    B -. "touches another<br/>agent's file" .-> G["Breeze puts it<br/>back and tells you"]

Features

Watch it work

Ask in plain words. The agent card shows who's on it and what they're up to, and every read, edit and command lands in the chat live.

Your agent, found

First launch looks for coding agents, Git and Node.js. Pick one, or point Breeze at a local model. Settings → Agents shows each agent's usage and rescans on its own when you install something new.

Save points, thanks to Git

Stage, discard, commit and push from Source Control, with a graph of every checkpoint and branch. Files an agent is touching get flagged in the explorer and tabs.

Breeze Box

Just a prompt and a chat. No editor, no fuss. Code in a reply turns into a card you can copy or download in one click.

Vibe Code Mode

While an agent works, the IDE fades out and an Instagram or Facebook feed rolls. A card says when your code's ready; head back whenever you like.

Oh, and

Run with F5	Python, C, C++, C#, Java and Rust run on the compilers you already have. Missing one? Breeze tells you what to grab
Live preview	Pop index.html open beside your code and refresh as you go
Built-in terminal	Run Node and whatever else without leaving the editor
Big files, no sweat	Only the lines on screen get drawn, so huge files stay snappy
Local LLM, token-wise	A project map, ranged file reads and snippet edits keep requests small
Accounts	Sign in with GitHub or Google, with several accounts
Discord	Rich Presence shows what you're working on
Feels alive	Tiny synthesized sounds for clicks, typing and agents, with a volume slider

Getting started

Requires Node.js 20 or newer.

npm install
npm start

npm start compiles the renderer's TypeScript (src/renderer/breeze/*.ts, editcore.ts, codeview.ts) and launches the app. The compiled .js files are build output and aren't committed.

[!TIP] Run npm run build once, then open src/renderer/breeze.html in a browser for a demo of the UI with a sample project and canned agent runs. No Electron needed.

Script	What it does
npm start	Compile and run the app
npm run build	Compile TypeScript only
npm run watch	Compile on change
npm test	Syntax-check the main process and run the tests
npm run dist	Build the Windows installer into dist/

Configuration

Sign-in and Discord presence need client ids. Copy the example file and fill in your own:

cp breeze.config.example.json breeze.config.json

Or put them in a .env file next to main.js:

BREEZE_GITHUB_CLIENT_ID=
BREEZE_GOOGLE_CLIENT_ID=
BREEZE_GOOGLE_CLIENT_SECRET=
BREEZE_DISCORD_CLIENT_ID=

Environment variables override the config file. Both breeze.config.json and .env are gitignored; never commit them.

• GitHub: create an OAuth App and enable Device Flow (no secret needed).
• Google: create a Desktop app OAuth client.
• Discord: create an application and use its Application ID.

[!TIP] Breeze assumes a local LLM has a 4k-token context on Ollama and 8k elsewhere. If you raised your server's context size, set llmContext in Breeze's saved state so the agent can use the extra room.

Building the installer

npm run dist

This runs scripts/write-config.js, which writes breeze.config.json from your .env so the packaged app has its client ids, then builds dist/Breeze Code Setup <version>.exe with electron-builder.

[!WARNING] The installer is unsigned, so Windows SmartScreen may warn on other machines. Values bundled into an installer can be extracted by anyone who has it, so only put public client ids (and Google's desktop-app secret, which is not confidential) in .env when building.

How it fits together

flowchart TB
    subgraph R["Renderer · src/renderer"]
        UI["breeze.html + breeze.css"]
        F["breeze/*.ts<br/>one file per feature"]
        E["editcore.ts + codeview.ts<br/>the code editor"]
    end
    PL["preload.js<br/>the bridge"]
    subgraph M["Main process · src/main"]
        MJ["main.js<br/>files, terminal, Git, auth, runs"]
        T["team.js + mentions.js<br/>multi-agent prompts"]
        G["guard.js + pathguard.js<br/>path and command safety"]
        TC["toolchains.js<br/>compilers for F5"]
        AB["agentbrain.js<br/>local LLM context"]
    end
    subgraph A["Agents"]
        CL["Claude Code CLI"]
        CX["Codex CLI"]
        AG["Antigravity"]
        LL["Local LLM server"]
    end
    R <--> PL <--> M
    MJ --> CL & CX & AG
    AB --> LL

Path	Purpose
src/main/main.js	Electron main process: files, terminal, agent runs, usage, Git, auth
src/main/team.js, mentions.js	Splitting one prompt between several agents, file claims and crossings
src/main/agentbrain.js	The local LLM agent's context budget, project map and file-tool formats
src/main/antigravityAgentService.ts	Talks to Antigravity's agent service
src/main/preload.js	Bridge between the main process and the UI
src/main/toolchains.js	Compiler and tool detection for Run
src/main/discord.js	Discord Rich Presence client
src/main/guard.js, pathguard.js	Path and command safety checks
src/renderer/breeze.html, breeze.css	UI
src/renderer/breeze/	Renderer logic, one file per feature (settings, git, terminal and so on), loaded in order by breeze.html
src/renderer/editcore.ts, codeview.ts	The code editor's position logic and its virtualized text surface
assets/brand/ · fonts/ · icons/	App icon and wordmarks · bundled fonts · agent and feed logos
runtime/	C runtime helpers
scripts/	Build helpers
docs/screenshots/	Screenshots used in this README
BreezeCode-Web/	The website
test/	Tests

Team

| Member | | --- | --- | | @itsphatto | Founder and Lead Software Engineer: | | @sapfire151 | Lead Front End Developer and UI/UX Designer: | | @LangZab | UI/UX Designer: | | @esrazti | Contributor |

License

Breeze Code is free and open source software, released under the MIT License. You may use, copy, change and share it, including for commercial work, as long as the copyright and license notice stay with it.