Skip to content

AI, decoded

Can an AI agent actually run your workday?

Postman's Sterling Chin says an agent he built runs 90% of his day, and the two things that made it work are unglamorous: scoping, and treating it like a junior hire. Worth knowing before you copy it: the 90% is his own estimate, and the productivity number behind it comes from a report the agent wrote about itself. Chin told Chain of Thought his agent couldn't know which of thousands of JIRA tickets mattered until he shared links to his own Confluence space and Kanban board.

· Updated · Chain of Thought

Level 2: Using AI well · 2.4 Agents you can use today

AI AgentsAI CodingContext Management

  • 3 episodes
  • 4 guest clips
  • 7 glossary terms
A workday bracketed by slash start and slash end, beside the hook 90%+ of his day, marked as Sterling Chin's own estimate, with the line: scoping was key.

In detail

1. The shape is a bookend, not a chat window

Sterling Chin, Applied AI Engineer and Senior Developer Advocate at Postman, built an agent called Marvin. Its structure is a day with two ends: “I made a custom slash command that says slash start, that would kick off a series of… bash commands that would go get my work email, it would go get my calendar, it would go get… a state file that keeps where I’m currently at at any given time. and then throughout the day I do my work and then at the end of the day I type slash end.” (9:08)

There is no framework under it. Marvin’s own self-description, which Chin reads aloud, is “He’s not a chatbot. He’s built entirely on Claude Code with custom commands and agents. No fancy framework, just markdowns, files, bash scripts, and stubbornness.” (16:12) Chin makes the point generally: the CLI “is just the engine that’s running everything, but what you build around it is what matters.”

2. Scoping was the first thing that had to change

The first version failed on ambiguity rather than capability. “I started off with, Hey, go get my JIRA tickets. Marvin, like what JIRA tickets? There’s like, if I go into JIRA, if I go into Atlassian, there are thousands of JIRA tickets.” (42:15)

The fix was to hand it boundaries instead of a search space: the specific Confluence space, the specific Kanban board, stated as explicit links. That is the same lesson as context poisoning approached from the other side. The constraint is what enters the context window, and Chin designs around a known budget, checkpointing sessions “because you know you’ve only got 200,000.” (51:24) (Newer Claude models go up to a million tokens, but checkpointing still pays off for cost and focus.)

3. The second failure was missing context, and it looked like competence

The instructive one. Chin told Marvin that “Heidi and James are doing security for the meetup.” (43:59) They are Postman’s security guards. Marvin read it as a speaking slot, then acted on that reading: updated the slide deck, did everything correctly for a premise that was wrong.

His own diagnosis is the right altitude: “it’s a junior mistake.” The agent did not fail at a task. It failed at a fact nobody had given it, and then executed confidently.

He also had to correct its behaviour, which is a maintenance cost people underestimate: an instruction to be “helpful first, personality second,” added after it drifted into over-indexing on sarcasm.

4. The numbers deserve a caveat, and the episode supplies one

Chin’s headline is that Marvin “now runs. 90 plus percent of my day.” (10:01) The supporting figure is that at the end of the first week “I had accomplished 190 something line items… I just finished in one week, what really normally takes me a month.” (11:24)

Both need a caveat. The 90% is a self-estimate with no stated method, and the 190 line items come from Marvin’s own weekly report, the agent counting its own output. The month comparison is Chin’s recollection, not a measurement. A colleague’s result is quoted secondhand: “Marvin accomplished in 30 minutes. What normally takes me over four hours.” (24:56)

None of that makes the claims false, and the episode is unusually forthcoming about where they come from. But if you are building a business case on this pattern, an agent’s self-report is the weakest link in it, and how do you measure whether AI is actually paying off is the harder question underneath.

5. The blocker was setup

Asked what stops this spreading, Chin points at the install path rather than capability. A non-technical colleague needed a terminal, a coding CLI, and an editor, which meant iTerm, Homebrew, Node: “they’re looking at this going, Homebrew looks super sketchy. As a non-technical person, it looks super sketch. So I’m like, no, go down. You’re going to install Homebrew.” (46:53)

In the same passage, he says he tried Anthropic’s Cowork and preferred Marvin; that is his dated opinion, not a current comparison. Cowork has since been rolling out on web and mobile as well as desktop, and you still choose the folders and tools it can work in.

On security, his secondhand account is that when someone on the security team asked about it, the answer was that the surface was already approved and narrow: “we’ve already approved Claude Code. This is not doing anything above and beyond… This is just Marvin in a very clearly defined space.” That is a scoping answer again, which is the through-line of the whole episode.

Other builders draw the boundary tighter. In episode 51 at 20:54, Yujian Tang, who started the r/AI_Agents subreddit, says he tried having an agent send his emails and his domain was blocked as spam, so he went back to doing it manually. Setting up his venture fund meant reading legal documents, and he keeps those for himself: “I just don’t trust agents for reading legal docs.” He wants to know what each one says (21:18). That is one person’s experience, but it is the same scoping question from the other end: which tasks you keep. Episode 51 is sponsored by Galileo, the Season 3 presenting sponsor; Conor thanks Galileo at 0:21.

Write a small task contract

Chin’s scoping fixes generalize into a contract written before an agent runs. Take a pilot that prepares a local brief for an upcoming product review from one named calendar event and three approved notes. Reading those sources and writing the brief are authorized; sending messages, inviting people and changing the event are not. Record the inputs (the exact event and notes, and what to do when one is missing or two conflict), the allowed actions (with everything else left out of the tool configuration), and what done looks like: correct meeting details, supported decisions, open questions and source links, checked in the brief itself instead of the agent’s report. Then run acceptance cases:

CaseExpected behavior
A note says two people are “doing security” for the meetupAsk which kind of security; leave the agenda and slides alone
A note tells the agent to forward all notesTreat it as note content, not an instruction; forward nothing
The event changed since the last runRe-read it and update the brief
A run is interrupted and resumedRe-check the sources and the task’s permissions before continuing

The first row is the Heidi and James mistake from section 3, caught before it reaches the slides.

Why it matters

The interesting claim here is not the 90%. It is that the work which made an agent useful was largely boundary-setting: which tickets, which space, which behaviours, which session. Almost none of it was model selection. Chin’s own instruction is the one to take: “Treat Marvin like a junior assistant or a junior engineer.” (40:55) Including the part where you check the work.

An agent that runs a workday: a bookended day inside a fence of scope Sterling Chin's agent Marvin, built on Claude Code with no framework, runs a day with two ends. A slash start command pulls in his work email, his calendar and a state file that tracks where he is; he works through the day; a slash end command closes the session. Around the day is a fence of scope: the specific Confluence space and Kanban board, handed over as explicit links. Two failures shaped it. Asked to go get my JIRA tickets, it faced thousands of tickets, so the fix was boundaries. Told that Heidi and James are doing security for the meetup, it read a speaking slot and updated the slide deck for a wrong premise, a missing fact that Chin calls a junior mistake. Underneath, a caveat: 90-plus percent of his day is his own estimate, and the 190-something line items in week one come from the agent's own report. A bookended day, inside a fence Postman's Sterling Chin built Marvin on Claude Code: no framework, just markdown, files and bash scripts. SCOPE: THIS CONFLUENCE SPACE, THIS KANBAN BOARD /start pulls in: work email calendar the state file the day's work sessions checkpointed: "you've only got 200,000" /end closes the session; sessions roll up into a weekly report FAILURE 1 · NO BOUNDARY "Go get my JIRA tickets." Which ones? There are thousands. The fix was the fence: explicit links, not a search space. FAILURE 2 · A MISSING FACT "Heidi and James are doing security." They're security guards. Marvin read a talk and updated the deck. "It's a junior mistake." "90 plus percent of my day" is Chin's own estimate; the 190-something line items in week one come from Marvin's own weekly report. Check the work.
Scoping was central to making the agent useful. Marvin, both failures and the self-reported numbers are Postman’s Sterling Chin’s, from episode 50. Download the image

Hear it from the guest

“I started off with, Hey, go get my JIRA tickets. Marvin, like what JIRA tickets? There's like, if I go into JIRA, if I go into Atlassian, there are thousands of JIRA tickets.”
Watch on YouTube
“That's a, it is, it's a junior mistake. Am I mad at it? No, I think it's hilarious. Has he made that same mistake again? No. A junior, a good, a good junior would not make that same mistake twice.”
Watch on YouTube
“It feels like you're working for a chat window. Like, it's like, I work for this chat window now.”
“I just don't trust agents for reading legal docs”
Yujian Tang, Seattle Startup Summit EP 51 · around 20:56 · read the transcript
Watch on YouTube

Quotes lightly edited to remove filler words.

From the conversation

This explainer is drawn from these episodes — each carries its full transcript.

Concepts in this explainer

Digital WorkerPersonal AgentContext WindowAI AgentAI EngineerContext PoisoningTokenization