Category: agents
-
Codex Source Dive (I): the agentic loop is a runtime boundary
TLDR: A Codex turn is not one model call. It is a managed execution window where user input, tool calls, tool results, cancellation, compaction, and final answers are ordered by the runtime.
-
Codex Source Dive (II): goals are runtime state, not prompts
TLDR: A Codex Goal is a thread-level long-running task state machine. It stores objective, status, budget, usage, resume state, and continuation gates instead of relying on one remembered prompt.
-
Codex Source Dive (III): subagents are a thread tree
TLDR: A Codex subagent is not a background model call. It is a persistent child thread with identity, inherited runtime policy, forked context, mailbox communication, capacity limits, and resume behavior.
-
RLM: Recursive Language Model
TLDR: RLM's real insight is not recursion as a slogan. It moves long context out of the Transformer window and into an external environment that the model can inspect, slice, search, and delegate over.
-
Apodex-1.0: deep research as multi-agent verification
TLDR: Apodex-1.0 is most interesting as a verification-centric agent-system design: independent subagents explore, a shared report pool accumulates evidence, and verifier agents audit claims from outside the worker trace.
-
Graph of Agents: multi-agent value comes from information flow
TLDR: Graph of Agents is useful because it treats collaboration as a test-time graph problem: choose relevant agents, score their answers, pass messages in the right direction, and pool the result.
-
SkillOpt: training the procedure outside the weights
TLDR: SkillOpt treats an agent skill as an optimizable text artifact. The model stays frozen, rollouts provide evidence, an optimizer proposes edits, and a validation gate accepts only real improvements.
-
LeanMarathon: long-horizon formalization as agent engineering
LeanMarathon turns paper-level Lean formalization into a recoverable multi-agent engineering system: blueprint, proof DAG, scoped workers, reviewer issues, and CI gates keep long tasks from drifting.