Skip to content

Writing · 2026-06-30 · By the operator at Tend the Tech

When the tool doesn't exist, we build it.

We run more than a hundred AI work sessions across our clients. There was no way to tell them apart. So we built one. Here's the story — because it's the same thing we do for your shop.

The mess

Every job we do runs as its own AI session — a Beacon page, a Google Business Profile fix, an email cleanup, a new build. We use Claude Code for a lot of the work. After a few months there were over a hundred sessions, each with a name the tool auto-picked for it.

The names were useless. "General coding session." "Resume previous coding session." Three of them called the exact same thing. Finding last Tuesday's work meant opening them one by one.

The fix should be one line: put the date on each one. "6.30 Beacon email cleanup." Sort by date. Done. That's where it got interesting.

The obvious fix fought back

We renamed a session. It reverted. We renamed it again and watched — the date undid itself 35 seconds later.

The app keeps its own copy of every name in memory and writes it back over yours while it's running. You're not editing the list. You're arguing with it.

So the rule changed: make the change while the app is fully closed. Nothing to argue with, disk wins, the names stick on the next open. Small thing. Took a revert-at-35-seconds to see it.

Then the dates were wrong

Second trap. The "last active" time the app stores gets bumped just by opening a session — no work done, but now it reads as touched today. Ten sessions we'd only glanced at came out stamped with today's date.

The real "last worked on" isn't a timestamp. It's the last actual message in the conversation. So we date from that instead. One session read as yesterday's; the last real message was three weeks old. Now it says three weeks old, because that's the truth.

The result

A hundred-plus sessions, each stamped with the day we last touched it, correct and stable. One double-click to refresh whenever the list sprawls again.

Then we wrote it up as a reusable tool — a Claude Code skill — so next time it's not a project, it's a button. It sits in our tool library with the rest.

Why this is on our website

Because it's the whole job. The off-the-shelf tool didn't do this. Most people would live with the mess — squint at the list, lose ten minutes, move on. We don't. We build the small thing that saves the hours, then keep it for next time.

That's what "hand us the keys" means. When the tech you rely on has a gap, we don't file a support ticket and wait. We close the gap. We did it for our own shop here. We do it for yours.

The tech you don't have time for, handled — down to the tools that don't exist yet. Tell us what's broken.

The first text is free.

Tell us what's broken or what's bugging you about the digital side. We'll tell you straight whether it's worth fixing, what it costs, and whether we're the right people to do it.

Text us →