clikae
Posts tagged clikae
RSS FEED-
Spending cloud credit from a terminal
Anthropic gave every Claude Code account $250 of cloud-session credit. Spending it without burning the 16 GB machine on the desk turned into a division of labor: the terminal as dispatch desk, cloud sessions as the hands, the Air as the acceptance bench. Three hours of browser scripting before reading the first page of --help, then what the cloud cannot do, then a second account with nothing connected that found a real bug for two dollars.
-
Someone recommended a tool. We looked it up and did not install it.
A link arrived with a recommendation attached. The first answer I gave came from memory. What replaced it took one fetch of a docs page and one question about why a middle layer was needed at all.
-
A dying server pushed three live sessions out of tmux, and my fallback did it
My own test gate killed the tmux server twice in one day. That was the loud defect. The quiet one was a fallback I had written for a different failure: when attach failed, it carried on outside tmux — conversations intact, and unreachable from anywhere but that one terminal. It took three vantage points to see the whole of it.
-
Your cleanup handler did not run, and you will never be told
An EXIT trap restored something important. Closing the terminal window sent SIGHUP, which terminates without running EXIT traps, and the important thing stayed lost. The fix was not a bigger trap — it was to stop treating cleanup as the place correctness lives.
-
The day my own cleanup tool deleted 612 MB of live work
A cleanup feature ate a session that was still open, on my own machine, the day it shipped. Three independent guards had to fail for that to happen — and the deepest one was that the tool was showing a machine's guess instead of the name I had typed myself.
-
Your best reviewer is the one who has never heard your reasoning
A bug survived five releases because everyone who read that line already knew what it was supposed to do. The fix was not reading harder — it was pointing a reader with no memory at the diff, and paying the tax that comes with one.
-
The half they rent you, and the half that is yours
The model is rented and the vendors are at war over it, which is good news. The other half — who you are, what you know, where you left off — is yours, and it only stays yours if it can leave.
-
I spent nine months calling it a fuel tank
The container was named after the most visible thing inside it. It was actually holding long-term memory, session history, and a record of who I had been while using it — and once you notice that, the whole tool has to change shape.
-
They asked me to separate their accounts, not their tools
Isolating an account meant pointing one environment variable at a private directory. It worked. It also silently took away every custom command the user had written, because the vendor kept those in the same place.
-
Never judge a headless AI run by its exit code
An agent that hit its usage limit and wrote nothing still exits 0. So you check the file instead — and then a stale file, and an empty file, both lie to you too. Three versions of the same bug, and the rule that finally held.