A one-person AI tooling studio

Build it.
Understand it.
Share what works.

This is a workshop, not a company. I make things, figure out how they actually behave, and share the parts that turn out to be useful - mostly around terminals, AI systems, and how to bring them together without giving up control.

security > privacy > cost > usability
Build and share

Working tools for a concrete problem. First up: ridinCLIgun, a terminal copilot that helps, warns, but never takes control.

Understand and write it down

Notes on AI safety, usability, agent-assisted workflows, and what is actually useful. The first English Garden text is live now; the glossary still sits in German while the rest catches up.

Safe and open

Security first. Privacy second. Cost third. Usability follows from those constraints, not the other way around.

ridinCLIgun

Open office scene with risky terminal commands visible across multiple screens
>_ridinCLIgun

A terminal tool for people who want to keep their shell, but occasionally want a second opinion before they press Enter. If you want to run agent systems on your own machine in a controlled way, you have to own the terminal. I built ridinCLIgun to fix my own problems with it - and it turned out other people had the same problems.

v0.4 shipped human in the loop local-first command knowledge room to grow

Direct product page

Useful today, still growing.

  • Current build: offline command knowledge, typo detection, language-aware AI, and review history are already working.
  • Human in the loop: ridinCLIgun advises. It never presses Enter for you.
  • Room to grow: the next steps lean toward teaching, workflow support, and supervising agents - without taking control away from the operator.
Workshop and garden scene suggesting a thoughtful studio environment for building and writing
Open the English Garden

What's growing here

A few subjects I keep coming back to. The first English Garden text is online now, and the series keeps growing from there. The glossary is still German for the moment, while parts 2 and 3 are already queued.

01
Agentic Coding and Security

The first English Garden article is live: a four-layer risk model for building safer code with coding agents.

Read part 1
02
German glossary

The companion glossary already exists and is still the best place for quick definitions until the English version is translated.

Open glossary
03
Lethal Trifecta and Prompt Injection

Prompt injection, untrusted input, the Rule of Two, and the design moves that keep an agent's working context clean.

Open article

/garden/ is not a blog. it's a garden. it grows.

Good tools make the user stronger, not more dependent.

Good tools make the user stronger, not more dependent. They explain what they do, and let the person learn and decide. They favour security first, privacy second, cost third, usability fourth - not because usability does not matter, but because the order decides whether the tool serves the person or the other way around. They do not promise more than they deliver. And they are fun - because getting things to actually work is one of the best feelings there is.

There is something of a civic duty in this: those of us who can figure these systems out should help others run their own agent setups safely, sovereignly, and affordably - participate in the discourse - and help make that the norm, not the exception.

inference-garden
section debug mode