Taylor Dolezal

Taylor Dolezal

@onlydole.dev

Engineer, writer, and community builder. Head of OSS @dosu.dev. Previously CNCF. onlydole.substack.com

2.2K followers686 following317 posts

Taylor Dolezal reposted

Should Humans Review An AI Agent's Work? Our CEO's, Devin Stein, take: people are already overwhelmed with review. Reviewing small pieces of conflicting information is work nobody has time for. Let the agent's do it.

How fun AGNTCon + MCPCon has been in San Jose! So far it's rain, palms, a full room for Dex Horthy’s State of the Software Factory, a Bigfoot and a glazed T-rex. 🦖 I’ll be here through Friday. Building agents or MCP? Say hi and let’s talk! 👋 😄

When each agent session on Kubernetes gets its own Pod, that Pod keeps CPU and memory reserved while the agent waits. Google's Agent Substrate snapshots the idle agent and returns its sandbox to a shared pool. Alexa Griffith walked me through it on Attention Deficit Ep. 8!

youtu.beGPT-6 Luna vs Sol. Can a harness close the gap? | Attention DeficitGPT-6 Luna vs Sol. Can a harness close the gap? Taylor and Alexa compare cheaper runs with longer waits in one coding experiment.

Taylor Dolezal reposted

It's Dosu Drop Day! 🎃 🔌 Live context from connected MCP servers (beta) 🔔 Approve knowledge updates in Slack 🔎 Deeper research, with the slowest answers about 30 seconds sooner 🏠 A limited self-hosted trial when security review blocks hosted Dosu go.dosu.dev/drop-oct26-b...

Taylor Dolezal reposted

In our Vercel AI SDK replays, agents learned the same build rule across 59 sessions and 40 tickets. One Codex run traced a missing import to a dependency's missing compiled output. What knowledge should you save for the next agent? dosu.dev/blog/coding-...

How do your Claude Code and Codex tokens break down? ( hint: you can find out with npx @dosu/decant )

Dosu@dosu.dev

We gave Claude Code (Opus 5.5) and Codex (GPT 6.1 Sol) the same 49 Vercel/AI tickets, and we found some interesting gaps. Check out the full story (with graphs)! go.dosu.dev/agent-cost-g...

Taylor Dolezal reposted

Does your coding agent choose a skill from the task...or only when you name the skill? Try a fresh session without the conversation where you wrote the instructions. Our procedural memory guide explains what to check. dosu.dev/blog/procedu...

Taylor Dolezal reposted

After internal tests, we saw three embedding models rank undated Celery and DBOS facts in the same order for June and December questions. Your coding agent needs the history behind a fact to judge when to apply it. dosu.dev/blog/semanti...

Okay, your agent saved the instruction. Does it still make sense now that the code has changed? I would love to go back and see why we ended up there in the first place!

Dosu@dosu.dev

Your agent runs pytest again. In the last session, it learned that make test-int starts the database the tests need. That lesson may still be saved, but never retrieved. Before correcting your agent again, check what made it into context. go.dosu.dev/episodic-mem...

Taylor Dolezal reposted

i told opus to remix the pdoom video and take liberties

Taylor Dolezal reposted

It's Dosu Drop Day! 🎒 For our back-to-school edition, Dosu does the studying. When a coding session ends, Dosu writes down what your team would otherwise rediscover. 📝 Session-end study 🧾 Knowledge read cards 💳 Credits that go further go.dosu.dev/drop-sep26-bsky

Astra, Sol, and Luna from OpenAI have new badges in Decant v0.6.0. ✨🔥🌙 See where your tokens went and what your agents did in each session, right on your machine. Your move, Anthropic! A themed Claude lineup would be fun to design around. github.com/dosu-ai/decant

Taylor Dolezal reposted

Who reviews agent memory when people can’t keep up? Michael Mangus, Head of Product at Dosu, on trusting AI to maintain memory—and making mistakes easy to correct. Recording + transcript: dosu.dev/webinars/age...

Taylor Dolezal reposted

A summary of a summary keeps getting further from the source. Michael Mangus, Head of Product at Dosu, explains how repeated summaries lose details in agent memory. Recording + transcript: dosu.dev/webinars/age...

I’m curious about using more open-weight models alongside frontier ones for daily work. Broad benchmarks don’t tell me much about how that would work in practice, so evals built around everyday tasks have been catching my attention.

I’d love to understand more of the thinking behind people’s choices. I’m interested in how you’re approaching evals for your own work, even if you haven’t settled on an approach. I’m still figuring out where open-weight models would fit into my own work.

Ever wonder what happens when you sign in to Netflix on your TV? You get shown a code, approve it on your phone, and never have to type in a password. Coding agents don't get that luxury, though. Learn about how we solved that problem in Dosu's CLI, and where we found our inspiration!

go.dosu.devHow to design a CLI login flow for coding agentsDesign a CLI login for coding agents with a ticket flow that pauses, resumes in a new process, and returns the next command in JSON. Learn how Dosu built it.

Alexa burned $3,000 in tokens in a day. I ran sixteen adversarial reviewers on a blog post. New Attention Deficit episode is out, where we talk about what agents cost, and when it makes sense (or cents) on when to give your agents more work. bit.ly/4d4EDJ5

attentiondeficitpod.substack.comAttention Deficit Ep. 6 – Sixteen Adversarial ReviewersA $3,000 token day, Claude gets $534 to trade, Anthropic marks its text, and a Bash harness that knows when it’s time to go to sleep.

Taylor Dolezal reposted

It's Dosu Drop Day! 🗄️ Your Claude Code, Codex, and Cursor logs hold answers you keep spending tokens on. Now, Dosu stores them. 1. Backfill your Library from agent logs 2. Configure Dosu by asking Dosu 3. Analytics on login 4. See what knowledge your agent used go.dosu.dev/drop-aug26-b...

What EXACTLY are your agents doing? Communicating? Coding? Planning or gathering Context? Dosu's new OSS project, Decant, can answer that for you!

Dosu@dosu.dev

We launched a new OSS project today called Decant! Decant reads the logs Claude Code and Codex write and splits each run into categories of Context, Planning, Code, and Communicating. We'd love to hear what you think and what you learn from your sessions. go.dosu.dev/decant-aug26-bsky

Do you read for fun? Reading for pleasure fell from 28% in 2004 to 16% in 2023, and AI has led to increases of monthly book releases. Some good news comes from Dallas, where a school phone ban drove 200,000 more library checkouts. Join Alexa and me for ALL the tea, and maybe go read a book.

attentiondeficitpod.substack.comhttps://attentiondeficitpod.substack.com/p/attention-deficit-ep-4-the-effortReasoning effort is a price dial most of us have been setting incorrectly, Peter Thiel bets $140 million on wave-powered compute, and people stop reading for fun.

_______________________________________ < Curiosity is a useful debugging tool. > ——————————————————— \ ^__^ \ (oo)\_______ (__)\ )\/\ ||——w | || ||

Attention Deficit ep 3 is out! Anthropic told Claude its eval had no internet…but it did. Plus, we speak about the librarians teaching people to turn AI off, and Alexa does a defense tech deep dive, from PayPal to the Pentagon. open.substack.com/pub/attentio...

open.substack.comAttention Deficit Ep. 3 – The incident part II, the off switch, and follow the dataClaude reaches real companies from inside a cyber eval, a librarian’s class on turning AI off packs the room, and we follow the defense tech money from PayPal to the Pentagon.

Cursor's swarm rebuilt SQLite from its 835-page manual. Same quality, a bill of $10,565 or $1,339 depending on which model planned and which typed. Attention Deficit Ep 02 digs in, plus the OpenAI and Hugging Face incident.

attentiondeficitpod.substack.comhttps://attentiondeficitpod.substack.com/p/attention-deficit-ep-2-the-incidentA model breaks out of its eval and into Hugging Face, the market starts asking for receipts, and we go looking for the scheduler agent stacks are missing.