When my home server started talking back, the next question was obvious: could it work on my code too? Honestly, this was the part I was most nervous about. A bot that writes a bad note gives me a bad note. A bot that pushes code can ship a bug to my live site (or get tricked into doing something I'd never approve).
So this is mostly a post about guardrails. And about the pull requests that convinced me they work.
Read-only first
Before it could change anything, I wanted it to be able to read...
I was listening to today's Syntax.fm's podcast episode where Wes and Scott were talking about the dawn of vibe coded Adobe clones, more specifically the release of the ArtCraft suite of apps that's been making waves on social medias for ...
If you're reading this on my site instead of in a feed reader: hi, yes, it looks different. π
Honestly, the old look had gotten stale. It was the stock Webstead default theme with every setting left at its default. Cream background, orange accent, fancy serif headings. Nice! But it looked like every Webstead site, and I wanted mine to feel like mine.
So now it's a terminal.
What changed
A prompt for a header. aaron@crowdersoup:~$, with a blinking cursor (it stops blinking if your system asks...