Statusline Builder configures a full Claude Code statusline with drag and drop, no code required
It ships with 33 elements to mix and match, free forever, no account and no email gate
Giving away a genuinely useful tool builds more trust than any paid product description could
The free tool taught me more about what people actually want than my paid products did
The Tool Nobody Has to Pay For
Every Claude Code session shows a status bar at the bottom of the terminal, and by default it tells you almost nothing worth knowing. Anthropic left that bar customizable on purpose, which is generous and also a trap, because customizing it means writing a script that outputs the right text in the right format, and most people who would benefit from a good statusline have zero interest in writing that script.
Statusline Builder exists to remove that step entirely. It is a visual configurator with 33 elements you can drag into place, from context usage and token counts to cost tracking and rate limit warnings, and when you are done arranging them you get one command to paste into your terminal. No sign-up. No email address collected before you can use it. No trial period after which the good parts lock behind a paywall. You open it, you build your statusline, you copy the command, and it works.
I built and shipped this one differently from most things in the shop, because it will never make a single euro on its own. It is free forever, by design, not as an introductory offer with a catch waiting on the other side. That is an unusual thing for a one-person studio to spend evenings on, and I want to walk through why I think it was worth doing anyway, what it actually costs to give something away properly, and what it taught me that none of my paid products did.
Most tools that call themselves free eventually reveal the catch. An email gate before the download. A watermark that only disappears once you pay. A trial period that quietly expires. Each of those choices is defensible on its own, and I understand why other studios make them. But every one of those choices also turns "free" into a lever for getting something else from you, and the moment a visitor notices the lever, the trust the free tool was supposed to build starts leaking out the other side. I wanted Statusline Builder to be free in the plain, boring sense of the word, because that is the only version of free that actually earns anything back.
What 33 Elements Taught Me About Restraint
The number 33 was not a target I set out to hit. It is what was left after I cut the elements that sounded useful in a planning document but turned out to be noise once they were actually sitting in a terminal prompt. Early versions of the builder had more options than that, things like decorative separators and elaborate color themes that were fun to build and immediately made every generated statusline harder to read at a glance.
A statusline lives in the corner of your eye. You are not supposed to study it, you are supposed to notice it. That constraint turned out to be the real design brief, more than any feature list I wrote down beforehand. Every element that made it into the final 33 earns its place by answering a question fast: how much context is left, what is this session costing, how close am I to a rate limit, which model is actually running right now. Anything that took more than a glance to interpret got cut, no matter how good it looked in a screenshot.
Building the drag and drop ordering was the part that made this restraint concrete instead of theoretical. Once you can freely reorder 33 elements, you immediately see which combinations clutter the line and which ones read cleanly together, because you are looking at it happen in real time instead of imagining it. I spent more time removing elements after building them than I spent building them in the first place, which is not the ratio I expected going in, but it is the ratio that produced a tool people actually keep using instead of configuring once and reverting.
The one-click install command mattered just as much as the element set. A configurator that hands you a JSON file you then have to figure out how to wire into your settings is still asking for effort most people will not spend. Collapsing the whole output down to a single command you paste and forget was the difference between a tool people try once and a tool people actually install.
Why I Give Away Something That Makes No Money
The honest answer starts with what I actually use myself. I run Claude Code for a meaningful share of my working hours, and a statusline that shows the wrong information, or no information, is a small daily cost that adds up fast. I built the first version of this purely to fix my own terminal, the same way I wrote about setting up the .claude folder mostly because I needed the reference for myself first. Making it public and free was a second decision, separate from the first, and it deserves its own reasoning.
Part of it is straightforward reciprocity. This blog and this shop exist because people who write about Claude Code, ship plugins, and share configurations for free taught me most of what I know about using it well. A free, genuinely useful tool is the closest thing I can offer back to that same community, without pretending it is charity. It is closer to paying forward the exact kind of thing that helped me.
Part of it is also plainly strategic, and I do not think there is anything wrong with saying so. A tool someone uses every single day, in the corner of their terminal, is a far stronger relationship than a blog post someone reads once. People who use Statusline Builder see the RAXXO name every time they glance at their prompt, and if that experience is good, unpretentious, and free of catches, it earns a kind of trust that no amount of product copy on a paid page could buy on its own. I am not going to pretend the free tool exists in a vacuum away from the rest of the shop. It sits right next to my guide to the best Claude Code skills and plugins, part of the same effort to make Claude Code better for people who spend real hours in it.
What I will not do is let that strategic reasoning turn into a hidden hook. No email capture, no upsell interstitial between building your statusline and copying your command. The moment a free tool starts optimizing for anything other than being useful, it stops being the thing that earned the trust in the first place.
What Building a Free Tool Taught Me About My Paid Products
I did not expect the free tool to change how I think about the paid ones, but it did, in a specific way. Because Statusline Builder has no signup wall, I get to watch, in a loose and anonymous sense, how people actually use it: which elements get dragged in first, which combinations show up again and again, which parts of the interface get ignored entirely. None of that comes with names or emails attached, just patterns in how the tool gets used, and those patterns are more honest than almost any other feedback I get.
The clearest lesson was how much people undervalue their own screen real estate. Given 33 options, most people settle on four or five, and the ones they pick are almost always the plainest, most literal choices, context left, cost, model name, nothing decorative. That is a useful thing to know when I am designing any interface, paid or free, because it confirms that clarity beats cleverness even when cleverness is sitting right there as an option.
It also reset my instinct about what "enough" looks like before shipping. A free tool with no price tag riding on it removes the temptation to keep adding features just to justify a price, which is a temptation I notice more than I would like in paid products. Statusline Builder shipped when it did the core job well, not when it had accumulated enough features to feel expensive. That is a discipline I have tried to carry back into everything else I build since, whether it makes money or not.
Bottom Line
Statusline Builder will never be one of the paid products in this shop, and that was the entire point from the start. It exists because a good statusline is a small daily improvement to a tool I use constantly, and because giving that improvement away, without a catch, is worth more to the relationship between this studio and the people who read this blog than any single sale would be.
Building it taught me two things I did not expect to learn from a free tool. First, that restraint, cutting elements instead of adding them, is what actually makes a configurator usable instead of just impressive in a screenshot. Second, that watching how people use something with zero friction attached tells you more about what they actually want than almost any other kind of feedback available to a one-person studio.
If you use Claude Code and your statusline still shows the defaults, that is ten minutes you are owed back. Go build the one you actually want, and keep the command. It costs nothing and it was never supposed to.
Top comments (0)