HexLab

Season 1: The Attention Queue & a2a › Ep 3

Ep 3 · Waking Codex

Length 1:10

Today's goal: Codex can't be poked from inside its app. So how does an answer reach a Codex thread?

What you'll learn

  • Every sixty seconds, the server looks for answers meant for Codex.
  • It waits for ninety seconds unclaimed first, so the waiting command or the inbox gets the first chance.
  • It finds that exact thread's file, skips it if busy, marks the answer delivered, then resumes the thread headless.
  • If the turn never starts, the answer goes back and waits an hour.

Sources

  • attention repo · src/codex-deliver.mjs (grace, busy check, mark first)
  • attention repo · src/server.mjs (60 s tick)
  • codex-kit · lib/index.mjs (what counts as busy)
  • Our records: the Attention store's log.jsonl (the three failed resumes)
About our sources →