Agents on Thede Technologies

An Agent Reads My Email

Thu, 06 Aug 2026 00:00:00 +0000

Every morning at five, an agent reads yesterday’s email and writes me a briefing. Most mornings I read the briefing instead of the inbox.

My friend Kyle Reinford just published the pattern he uses - Cloudflare Email Workers catch messages at the edge and file them into R2, so a model never touches his real Gmail. Mine is the same idea from the other end: he guards the front door, I process at home. Apple Mail already syncs my accounts to disk. A script reads the last 24 hours of messages and hands each body to a local model - Qwen3.6-35b-a3b, running in LM Studio on my Mac Studio. No agent harness, no tool loop - just one chat call to localhost per message. All the model gets to do is fill out a tiny form: what is this, does it need me, one-line summary. A renderer turns the day’s forms into a static page. Nothing leaves the house.

The Thread That Never Ends

Fri, 09 Oct 2026 09:00:00 -0500

For years the rule with AI chat was: keep threads small and single-focused. One chat per task. Finish, close, open a fresh one. Long threads rot. I learned that one the hard way in April, when I mined a month of my own sessions and found that past a hundred turns the answers stopped being right.

With Fable, I stopped.

One thread has been open for days now. I asked it what it was best at, and it said taking in a tremendous amount of information and not losing track of any of it. So I opened a single terminal window and we worked on five projects at the same time. It didn’t lose the thread once. It knew which piece belonged to which project and what we needed to do next.

The Machine I Can't Turn Off

Wed, 07 Oct 2026 09:00:00 -0500

I told my partner the other night that I can never turn the Mac Studio off.

There’s a job on that machine at 11:45 at night. One at 3:30 in the morning. One at five, one at seven. Every one of them is an agent. It wakes up, reads something, thinks about it with a model that runs entirely on the chip under my desk, writes something down, and goes back to sleep.

The architecture of advice

Mon, 11 May 2026 00:00:00 +0000

In the last post I looked at the sheer volume of AI-assisted engineering: 55,000 turns of professional capital recovered from a single month. But once you have the data, you stop asking “how much?” and start asking “what kind?”

So I ran a high-fidelity thematic enrichment pass over 466 sessions from the corpus and started mapping what I’m calling the architecture of advice: the hidden patterns that define how AI actually influences a multi-repo technical portfolio.

30 days of AI collaboration

Thu, 07 May 2026 00:00:00 +0000

In the spring of 2026 I spent 30 days living in the “jagged frontier” of AI-assisted software engineering.

If you’ve worked with Claude Code, Gemini CLI, Cursor, or Codex you know the feeling. A high-intensity session ends, the terminal clears, and months of architectural decisions, debugging insights, and technical pivots vanish with the scrollback. The next morning you remember the outcome but not the reasoning that got you there.

I decided to stop losing that knowledge. This is the data-driven retrospective of 466 sessions, 55,224 turns, and 1,772 technical decisions recovered from a single month of work, and what I found when I went back through the corpus systematically.