Most Zig developers today use tools like Visual Studio Code with extensions.
It works — but I kept wondering:
What would a Zig-first IDE feel like if it was designed around simplicity and speed?
So I built one.
Ferrum Studio.
Why I built this
While learning and working with Zig, I noticed the workflow often feels adapted rather than designed for the language.
You install an editor, configure extensions, tweak settings… and eventually it works.
But I wanted something simpler:
Open a Zig file
Press run
See output immediately
No friction. No setup overhead.
What Ferrum Studio does
Ferrum Studio is a lightweight IDE focused specifically on Zig.
A few things upfront:
Built with Go + Wails (uses a system webview — no bundled Chromium)
Frontend parts were built with help from AI tools (I’m still learning JavaScript)
Backend, Zig integration, and overall structure are written by me
Features (current)
Run Zig files (zig run) with live output
Build (zig build), test, and ast-check integration
Inline error display with simplified explanations
Basic autocomplete and snippets
Project templates (CLI, library, TCP server, embedded)
Integrated terminal with stdin support
Zig auto-detection
The main goal: a smooth workflow
The focus is on making this loop fast and simple:
open → run → see output → interact → fix errors
Handling things like:
real-time output streaming
stdin interaction
process control
…took more work than expected, but this is the part I’m most proud of.
Who should use this (right now)
Ferrum Studio is still early, but it’s already useful for:
Developers learning Zig who want a simple environment
People who prefer lightweight tools over heavier setups
Anyone who wants a fast “open → run → test” workflow
If you rely heavily on advanced IDE features (full LSP, deep refactoring, debugging), tools like Visual Studio Code are still better today.
But if you want a focused, minimal Zig workflow — this already works well.
What I learned
This project taught me a lot:
How Zig tooling works in practice (run, build, test, ast-check)
Managing subprocesses and terminal interaction
Designing an editor around a single language
Using AI tools effectively for parts I’m less experienced in
What’s next
Deciding between lightweight autocomplete vs full LSP (ZLS)
Improving error explanations
Exploring debugging support
Cleaning up and improving the codebase
Feedback?
I’d really appreciate input:
What do you expect from a Zig-focused IDE?
What slows you down in your current workflow?
What would make this genuinely useful for you?
Project
GitHub: https://github.com/CzaxStudio/Ferrum-Studio
Final thoughts
This started as an experiment — but it’s already shaping how I think about developer tools.
Simple, fast, and focused.
Thanks for reading 🙂
Top comments (0)