I make games with Unity, and I build the backend systems and dev tooling behind them.

I'm Lukas, a software developer studying at HTL Leonding. I got into this through game dev and never stopped enjoying it. But I also spend a lot of time on backend systems, tooling, and the occasional robot.

I think developer experience is a feature, not a nice-to-have. A teammate should get what a tool does in the first ten seconds. If I have to jump between twenty windows and three docs to figure it out, I've already decided I hate it.

I also work on a distributed AI voice assistant, because I wanted my own Jarvis.

Actively developed

• vektorgrid: a local-first voice assistant, split across a C# orchestrator, stateless Python inference workers, satellite microphones, and an Android companion for approving tool calls. Five repos, early but architecturally further along than anything else I've done.
• SceneForge AI: a Unity editor assistant that turns model output into a diff of proposed scene changes. You review the diff, tick what you want, and only then does anything move. Currently Groq-backed with a reflection-based tool system.
• browser-webrtc: a WebRTC client and Python signaling server. Actively developed, and the successor to an earlier SFU-server version of the same idea.

Smaller things

• lego-spike-serial: a command interpreter for a LEGO Spike over serial. Good exercise in writing a real protocol for hardware that gives you no feedback.
• Unity.md: a markdown renderer for the Unity inspector.
• Programming NAOs, which is still the most fun way I've found to watch a robot walk into a wall.

In progress, not public

• A game about doing government missions as a pigeon. It's in a private repo getting a rework, so I can't show it off yet.

• gruenzweil.cc
• lukas.gruenzweil@liwest.at · personal
• l.gruenzweil@students.htl-leonding.ac.at · school