FluxCode

A native code editor for Windows and Linux, written in Rust and drawn by the GPU.
One small program with an AI agent panel, a Python-friendly terminal, built-in Source
Control, and read-only views for files other editors refuse to open. No telemetry.

A MuaraAI project, built by a first-semester university
student in Indonesia (MyKineID). Open source, and still in
development.

The agent added a docstring (line 23), the Changes card lists the file with Undo, and
because access is set to Read & write, it has to ask before running a command.

Download

Get the newest build from Releases.

There are no version numbers yet: every change merged into main becomes a build named
after the moment it was made, like BuildDev-2026-11-09-18-19-54. Installed copies offer
the new one in a card and update themselves in one click. Settings > Updates turns the
check off.

A closer look

A Python error becomes a card with the file, the line and a hint; for a missing module, Fix
installs it. A SQLite database opens as its tables, SQL and row counts, like Word, Excel,
PDF and ZIP files do, instead of an error.

Source Control stays fast with thousands of new files and offers to ignore the folders
that hold them. Go to File (Ctrl+P) finds a file from a few letters of its name.

Four color themes, three interface sizes and your own background image. The interface
also comes in Bahasa Indonesia, shown here with the update card in the FluxCream theme.

What makes it different

• Laid out and driven like VS Code. Activity bar, side bar, tabs, panel and status
  bar sit where VS Code puts them, and the keys are VS Code's: Ctrl+Shift+P opens the
  Command Palette with every command and its shortcut, Ctrl+P finds a file, Ctrl+G
  goes to a line, Ctrl+/ comments, Alt+Up moves a line. If you know VS Code, you
  already know where things are. It is not a VS Code clone: there are no extensions and
  no debugger yet (see the table below).
• Light like Zed. The whole editor is one Rust program drawn by the GPU with GPUI,
  the framework Zed is built on. On the PC this was measured on it opens its window in
  about 0.2 s and holds about 95 MB, in one process.
• Built for AI agents. The agent panel speaks the Agent Client Protocol and lists
  every agent in the ACP registry, each with its own icon. Missing ones install with one
  click into FluxCode's own folder. You choose the model, mode and permissions under the
  message box; the agent can ask you multiple-choice questions; each turn's file changes
  can be undone; the agent's instruction files are one click away in Settings.
• For beginners and experts. A beginner can pick an agent from a list, answer its
  questions by clicking, and keep it read-only. An expert gets the palette, the shortcuts,
  per-agent instruction files and every editor option in Settings: font, size, tab size,
  word wrap, whitespace, line numbers, folding, bracket closing, smart indent, cursor
  padding, scrolling past the end, interface size, themes and a background image.

What else it does

• Syntax colors for about 200 languages, picked by file name, extension or #! line.
• Multi-root workspaces: drag a folder onto the window to add it or switch to it.
• The agent panel (Ctrl+L) runs any agent in the ACP registry,
  such as OpenCode, Claude Agent, Codex, Gemini CLI, GitHub Copilot or MuaraAI's Mura. An
  agent that isn't on your PC has a download button in the agent menu (with the agent's own
  icon from the registry); FluxCode puts it in
  ~/.fluxcode/agents (npm packages too, not in your global npm) and starts it only while
  you use the panel. Model, effort, mode and permissions are dropdowns under the message
  box. Edit a sent message and the answer restarts from it; the agent gets an overview of
  the workspace and a local memory you can read, edit or switch off.
• Source Control commits, pushes, pulls and syncs, shows a commit graph, opens pull
  requests and GitHub Actions runs through gh, and Remove Git undoes a git init.
• After an update, a "What's new" page opens once with the notes since your last build
  (from changelog.flux, in the interface language). Help > What's New
  opens it again.
• Settings > About FluxCode links to this repository, the issue tracker and the changelog.

FluxCode, Zed and VS Code

All three are good editors made for different people. This is where each stands today.

* Measured on one Windows 11 PC on 10 November 2026: FluxCode (this build), Zed 1.27.0 and
VS Code 1.145.2, each started 5 times with a fresh empty profile, telemetry and update
checks off, no folder open; the time is to the first visible window, averaged over runs
2 to 5. Other PCs give other numbers; the order is what to read from it.

Pick FluxCode if you want a small, quiet editor on Windows or Linux with an agent you can
keep on a short leash, and you open logs, databases and documents next to your code.
Pick Zed for macOS, language servers out of the box and pair programming.
Pick VS Code when you need a specific extension, a debugger or remote development.

Privacy

FluxCode sends nothing about you. The only request it makes by itself is the update
check: a plain GET of the release list from github.com, with no build ID, machine ID or
cookie, at start and every 6 hours (Settings > Updates turns it off). Everything else goes
out only when you start it: the agent you run, git, and GitHub when you sign in. The
agent menu reads the public ACP agent list from cdn.agentclientprotocol.com, at most once
a day and only when you open the menu.

Shortcuts

VS Code's keys on Windows and Linux. Ctrl+Shift+P (or F1) lists every command with its
keys, and Settings > Keyboard shortcuts shows the same list.

Ctrl+L opens the agent (as in Cursor) where VS Code would select a line.

Build from source

Rust stable, then:

cargo build --release          # target/release/fluxcode(.exe)
cargo test --bin fluxcode

• Windows: HLSL shaders need fxc.exe from the Windows SDK, or set GPUI_FXC_PATH to
  tools/fxc-shim built with cargo build --release --manifest-path tools/fxc-shim/Cargo.toml.
  With the GNU toolchain, use a CARGO_TARGET_DIR without spaces (MinGW windres).
  packaging/windows/build.ps1 -Install builds, packs and installs like a release.
• Linux: pkg-config clang libxkbcommon-dev libxkbcommon-x11-dev libwayland-dev libx11-xcb-dev libxcb1-dev libfontconfig1-dev libfreetype6-dev libvulkan-dev (Debian
  and Ubuntu names).
• Builds name themselves from FLUXCODE_BUILD (BuildDev-YYYY-MM-DD-HH-MM-SS); without
  it, from the current UTC time.

Contributing

FluxCode is open source, and issues are open to everyone: report a bug or suggest an idea
through Issues. A bot checks each
new issue for earlier reports of the same problem and for an outdated build.

Pull requests are accepted only from members of the MuaraAI organization; others are
closed automatically. Details in CONTRIBUTING.md. What changed in each
build: CHANGELOG.md.

The icon

The mark is a meander: one unbroken line that turns only at right angles and never
crosses itself. The pattern is named after the river Maeander in western Anatolia (the
Büyük Menderes today). The Greek geographer Strabo wrote that it winds so much that
every winding course came to be called after it. One of the oldest known meanders is
carved into mammoth-ivory bracelets found at Mezin, in Ukraine, more than 15,000 years
ago; Greek potters of the Geometric period later painted it around whole vases.

FluxCode takes three things from it. The name: a flux is a flow, and the meander is a
river drawn as a rule. The structure: code also runs as one path that turns into a
block and comes back out, the way a call returns to where it started. The colors: ivory
for the Mezin carvings and ochre for fired clay, on ink. The line is split at its center
into two hooks of the same shape, turned 180 degrees and holding each other, so the mark
looks the same upside down. The app's FluxDark and FluxCream themes use the same three
colors.

License

GPL-3.0-or-later. Third-party components: THIRD_PARTY_NOTICES.md.