Ryan Carson: How I Run My Team of Agents

A July 2026 walkthrough of hardware, windows, and agent workflows — Devon, Codex, Sentry automation, and prod-safe secrets

← Part of the AI Agents knowledge base · AI · Productivity

Source: Ryan Carson (@ryancarson) — “How I run my team of agents” · Original post on X

Building @HelloUntangle. Video hosted at static2.mikesblog.com for stable embed.

Summary

In this short workspace tour (July 2026), Ryan Carson walks through how he actually works day to day: multi-monitor hardware, a hybrid analog/digital task system, and a stack of agents that act like a software factory — especially Devon for high-volume shipping and Codex for local Mac control.

Hardware & desk

Dell ~52″ display — enough real estate for about eight screens/windows at once
Written paper to-do list — keeps some of life intentionally analog
Shure mic — for calls/content
Razer mouse — switched from Magic Mouse after wrist pain; already happier
Hardware button → WhisperFlow — one physical button wired for voice/dictation flow

Agent & app layout

Slack + Sentry → Devon

Alerts channel auto-posts from Sentry. A Devon automation picks issues up, spins a Devon thread, triages, and fixes — closed-loop incident response.

Devon as software factory

~30–40 PRs/day via Devon. Credits from the company, but he’d pay again — “worth every cent.” Core shipping engine.

OnePassword + prod mutations

Any prod mutation (DB, Clerk users, etc.): Devon must ask for API keys. Ryan pastes from OnePassword as a one-time session secret — deliberate backstop so prod never changes without high awareness.

Codex (local Mac)

Local “life stuff”: browser control and on-machine tasks. Preferred agent surface for everything that lives on the Mac rather than the remote software factory.

Untangle product work

Testing two UI versions of Untangle side by side; admin tools open on the same canvas as agents and social (X).

Why this setup matters

Specialization by surface: Devon for high-throughput code/PRs and automated triage; Codex for local computer use.
Human in the loop only where it hurts: prod secrets and mutations require a conscious OnePassword paste — not ambient agent access.
Observability → agent: Sentry isn’t a dashboard you check later; it’s a trigger that spawns work.
Physical UX still counts: monitor real estate, ergonomic mouse, hardware voice button, paper list — agents don’t replace desk design.

Fits the same pattern as Codex computer-use workflows, agentic setup checklists, and verification / background agent loops — but as a real founder’s live desk, not theory.

Related Guides

ChatGPT + Codex Super App

Codex computer use, multi-thread, and power-user local workflows.

Read part 2 →

Agentic Setup Checklist

Harness items: worksheets, prod safety, night shift, reviews.

Open the checklist →

Stop Babysitting Agents

Verification loops and background routines so agents keep working.

Read the guide →

Company Questions

How execs think about Claude Code / Codex access and prod risk.

Read the list →

Full Transcript

Complete transcription of Ryan Carson’s workspace walkthrough. Video embedded above.

What's up everybody?

Quick run-through of how I work these days.

So I want to walk you through all the windows I use, all the apps I use, all the hardware I use.

First of all, obviously we've got a sim enroll.

Yum.

Okay, so I've got a my big Dell 52 allows me to have eight screens up at once.

I've got my written list of things to do because I like some analog of my life.

Got a nice Shure mic for all things.

Just bought this Razer which I love.

I was getting a lot of wrist pain.

I had a Magic Mouse so looking forward to it.

Already this is great.

I love it.

And this button right here I've already wired to WhisperFlow.

So I've got Slack up here.

You'll notice this is an alerts channel with Sentry.

So Sentry posts automatically and then I've got a Devon automation that picks it up right away, spins up a Devon thread, triages it, fixes it.

Got one password.

One thing I'm doing now is if I want to do any prod mutation, whether it's database or clerk users, Devon has to ask me for the correct API keys which I grab from one password and then paste them in as a one-time session secret.

So it's a really good way just to make sure we're not going to mutate anything on prod without you know being highly aware of what's going on.

So it's a good sort of backstop for a prod mutation on databases.

So obviously this is Devon.

You know I'm shipping probably like 30 to 40 PRs a day now on Devon.

It's just very very good software factory.

They do give me a ton of credit but I have paid in the past for them.

I would pay again.

It's worth every cent to me.

This is Untangle.

I'm testing two different versions of the UI.

Obviously I have X here.

Yay.

And then I've got Codex here which I do a lot of local like life stuff on.

So it can control my browser.

It can do a lot of stuff.

So I love Codex for just all things local on my Mac.

Very very good.

And then I've got some Untangle admin stuff there.

So that's kind of it.

And then this is the rest of the office.

All right.

Good to see you all.

Happy hacking.

Workspace walkthrough by Ryan Carson (@ryancarson). View the original post on X →