Working Notes on Agent Systems/Brad Zhang

@teach_fireworks / X longform

The main line of Agent development in 2026: moving from Agent Framework to Agent Runtime.

The main line of Agent development in 2026: moving from Agent Framework to Agent Runtime. The most obvious change in 2026 is that the Agent technology stack begins to be layered...

May 22, 2026 · 2 min read

The main line of Agent development in 2026: moving from Agent Framework to Agent Runtime.

The most obvious change in 2026 is that the Agent technology stack begins to be layered.

In the past, many teams packed prompts, tool calling, memory, workflow, permissions, logs, and deployment into one application.

The industry is now being split into several layers: 1 User entrance layer: ChatGPT / Codex App / VS Code / GitHub / Enterprise portal ↓ 2 Harness layer: prompt, tools, memory, subagent, planner, skills ↓ 3 Runtime layer: session, resume, event log, checkpoint, HITL, trace, fork ↓ 4 Compute Layers: sandbox, devbox, container, remote VM, K8s actor ↓ 5 Protocol layer: MCP, A2A, Agent Skills, AGENTS.md ↓ 6 Governance layer: identity, policy, audit, eval, observability, cost This Stratification is not a pure theory.

When OpenAI updated the Agents SDK in April 2026, it focused on model-native harness, native sandbox execution, and the separation of harness and compute; it also made it clear that agents need to be able to check files, run commands, edit code, and process long-horizon tasks in a controlled sandbox.

LangChain also made the problem very straightforward in the Deep Agents runtime article in April 2026: A good harness is responsible for prompts, tools, and skills, but a production-level long-task agent also needs durable execution, memory, multi-tenancy, human-in-the-loop, and observability.

Visual summary

Article argument map

Generated from the post's content graph

FORMATTOPICCAPABILITYMARKETcoverscoverscoverscoverscoverssignalssignalssignalsFORMATarticle featureTOPICagentsTOPICharness engineeringTOPIClong running agentsTOPICai workbenchesTOPICmemoryCAPABILITYagent workflowCAPABILITYharness engineeringCAPABILITYlong-running agentsCAPABILITYAI-native workbench
Mermaid outline
flowchart LR
  format-article["article feature"]
  topic-agents["agents"]
  topic-harness-engineering["harness engineering"]
  topic-long-running-agents["long running agents"]
  topic-ai-workbenches["ai workbenches"]
  topic-memory["memory"]
  capability-agent-workflow["agent workflow"]
  capability-harness-engineering["harness engineering"]
  capability-long-running-agents["long-running agents"]
  capability-ai-native-workbench["AI-native workbench"]
  format-article -->|covers| topic-agents
  format-article -->|covers| topic-harness-engineering
  format-article -->|covers| topic-long-running-agents
  format-article -->|covers| topic-ai-workbenches
  format-article -->|covers| topic-memory
  format-article -->|signals| capability-agent-workflow
  format-article -->|signals| capability-harness-engineering
  format-article -->|signals| capability-long-running-agents

Visual structure

Essay structure map

Built from summary and key paragraph positions

The main line of Agent development in 2026: moving from Agent Framework to Agent Runt...THESISThe main line of Agentdevelopment in 2026:moving from AgentFramework to AgentSIGNALThe main line of Agentdevelopment in 2026:moving from AgentFramework to AgentOPERATORThe industry is nowbeing split intoseveral layers: 1 Userentrance layer:IMPLICATIONLangChain also madethe problem verystraightforward in theDeep Agents runtime
Mermaid outline
flowchart LR
  thesis["The main line of Agent development in 2026: moving from Agent Framework to Agent Runtime. The most obvious..."]
  signal["The main line of Agent development in 2026: moving from Agent Framework to Agent Runtime."]
  operator["The industry is now being split into several layers: 1 User entrance layer: ChatGPT / Codex App / VS Code /..."]
  implication["LangChain also made the problem very straightforward in the Deep Agents runtime article in April 2026: A go..."]
  thesis -->|frames| signal
  signal -->|develops| operator
  operator -->|lands in| implication

Source: View the original post