Describe the part. Watch it take shape.

Change one parameter. Everything downstream follows.

A Robion project is a git repo. The model is code the agent writes; everything else is derived from it — regenerable, diffable, versioned. You never edit an output. You change the source, and you approve.

The agent edits one file; every artifact regenerates. Nothing is drawn by hand twice.

Five workshops. One process.

A 3D-printing maker, an electronics tinkerer, a woodworker, a CNC hobbyist and a software developer use different subsets of the same graph — with a different last mile. They meet on the spine: model it, see it, verify it, buy it, make it.

● works today◐ on the roadmap— not that workshop

3D print

from prompt to STL today; slicing and print monitoring next

electronics

KiCad boards with DRC/ERC, gerbers, board-in-enclosure fit

wood

furniture-grade drawings, BOMs and finishing plans; cut plans next

CNC & laser

DXF and true-scale PDF today; toolpaths and nesting next

software

where Robion started: agents, worktrees, diffs, reviews

Your agent models it. You see it instantly.

OpenSCAD and build123d models render in a live 3D panel — orbit them, even with a SpaceMouse. Open KiCad boards with DRC/ERC checks, preview Gerbers, DXF and PDF. Everything the agent produces appears in a panel next to the chat, ready for your next instruction.

• OpenSCAD
• build123d
• KiCad + DRC/ERC
• Gerber
• DXF
• PDF
• SpaceMouse

The agent builds the knobs.

Through set_controls the agent adds buttons, toggles and sliders to its own panel. Drag a slider — wall thickness, hole diameter, count — and the model re-renders in about 0.4 seconds. Tune the part like a customizer, without touching code.

All your agents on one screen.

Projects in a left rail, a colored state strip per agent. Every task is a tmux-backed Claude Code session — quit the app, agents keep working. Give a task its own git worktree and a sandbox when you want isolation. Robion started as a dev tool, and it stays one.

• running
• waiting for you
• done, unseen
• error

Amber means a human is needed.

⌘J jumps to the agent that needs you — permissions first, then questions, then errors. ⌘0 shows every task grouped by state. Dock badge, notifications. Amber never means anything else.

A locked-down toolbox in every session.

Robion injects a whitelisted MCP server into every Claude Code it launches: open files in a compare grid, show a diff, preview a dev server, request a review, build controls. Task-scoped — an agent cannot reach outside its folder.

• open_file
• open_files
• open_diff
• open_url
• request_review
• set_title
• set_controls
• get_controls
• remove_controls
• controls_help

Seventeen ways to look over their shoulder.

3D models, SVG, DXF, Gerber, PDF, git, a Jira viewer, an MCP inventory with startup times and token costs, usage and rate-limit stats. Diffs keep a "since last turn" baseline — click a line range and it goes back to the agent as a prompt.

• terminal
• 3D model
• diff
• viewer
• git
• tree
• markdown
• media
• web preview
• html
• Jira
• MCP servers
• stats
• activity
• checks
• controls
• overview

The cockpit in your pocket.

A real PWA served by your Mac and exposed only inside your Tailscale tailnet — the server stays on loopback. The phone renders the whole agent-built cockpit: progress bars, image tiles, checklists, live status. Approve or deny with a reason straight from the lock screen via optional ntfy push — from the couch or the workbench. Nothing touches the public internet.

Rules the app never breaks.

The editor is a viewer.

Robion never edits your files. The agent does — and you see every change.

tmux owns every process.

Quit the app; agents, builds and dev servers keep running.

The agent drives what you see, never how the app behaves.

MCP tools open panels and build controls. They cannot change settings or reach outside their task.

Machines start on a human click.

Agent-defined commands run when you press the button — never on their own. That holds for printers and mills too.

Nothing leaves your Mac.

A local server on loopback; the phone only inside your tailnet.

Amber means a human is needed.

And never anything else.

The road to “I made this.”

The maker half grows in waves — each one closes a full loop from idea to a made thing. Built in the open; the order can change with what you build.

1. 01Maker Packnextinstallable playbooks per workshop: intake → model → drawings → BOM → build sheet
2. 02The print loopplannedslicing, G-code preview, print progress on your phone
3. 03The 2D worldplannedlaser-ready DXF, nesting & cut plans, 1:1 drilling templates
4. 04CNC 2.5Dplannedcontour, pocket & drill toolpaths with a setup sheet

Runs on your Mac. Nothing leaves it.

macOS

Apple Silicon or Intel, signed & notarized build

Claude Code CLI

the agents are your own Claude Code sessions

tmux

owns every agent process, so they survive the app

Node 22+

runs the local server

OpenSCAD / KiCad

optional — for live model rendering and board checks

Python + build123d

optional — for BREP models, STEP and drawings

Tailscale

optional — for the phone client on your tailnet

Questions

Is it free?

The download is free.

Windows or Linux?

macOS only today.

Where does my code go?

Nowhere. Robion runs locally; the agents are your own Claude Code sessions on your machine.

Do I need to know CAD?

No. You describe the thing and tune sliders; the agent writes the parametric model. Knowing CAD helps, but the point is that it is optional.

Download Robion.

Free download. Signed and notarized DMGs, automatic updates from GitHub releases.

Latest release