Three OpenAI Engineers Shipped a Million Lines

Image Credit: Skynet

Long AI agent runs stay useful when context is managed outside the opening prompt, with separate files for plans, progress, rules, and working state.

That approach helps teams steer 6-to-10-hour sessions, reduce stale instructions, and keep agents aligned as projects evolve.

Paul’s Perspective:

This matters because longer-running agents are only as valuable as their ability to stay aligned with current business intent. Companies experimenting with AI automation can get better outcomes not by chasing larger context windows alone, but by designing a practical operating model that keeps plans, memory, and execution cleanly separated.


Key Points in Video:

  • One large instruction file tends to become a backlog of outdated guidance, so the video recommends separating four context types instead of relying on a single master prompt.
  • The examples cited include OpenAI, Anthropic, and Arize, showing how leading teams move the current plan into lightweight files the agent can refresh as work changes.
  • Arize’s example highlights a workflow spanning 27 model calls, underscoring why persistent external context matters once a task stretches across many steps.
  • The video references 400,000 Claude Code sessions and a 70/80 split, reinforcing that context structure has measurable impact at scale.
  • For more complex work, the suggested starting package gives an agent four distinct inputs so it can maintain direction without frequent restarts.

Strategic Actions:

  1. Stop relying on the opening prompt to govern the entire run.
  2. Separate context into distinct files for instructions, current plan, progress or memory, and working state.
  3. Keep the active plan short and current so the agent knows which decisions still matter.
  4. Update progress files during the run to preserve portable memory across long sessions.
  5. Move changing operational context to disk rather than leaving it buried in the prompt window.
  6. Use the four-file starter structure at the beginning of a project to reduce drift and rework.
  7. Review and reshape context as the task evolves instead of restarting the project from scratch.

The Bottom Line:

  • Long AI agent runs stay useful when context is managed outside the opening prompt, with separate files for plans, progress, rules, and working state.
  • That approach helps teams steer 6-to-10-hour sessions, reduce stale instructions, and keep agents aligned as projects evolve.

Dive deeper > Source Video:


Ready to Explore More?

If your team is exploring AI agents, we can help you put practical structure around prompts, workflows, and context management. We work with clients to turn ideas like this into usable systems that fit real operating needs.

Curated by Paul Helmick

Founder. CEO. Advisor.

@PaulHelmick
@323Works

Welcome to Thinking About AI

Free Weekly Email Digest

  • Get links to the latest articles  once a week.
  • It's easy to stay up-to-date with all of the best stories that we discover and curate for you.