Videos UPwGaM2MKHY
The Log Is The Agent - Ishaan Sehgal, Omnara
Scene timeline
32 shot(s).
keyframes kept every frame deduplicated
What was stored
- cues
- 195
- whisperx 195
- chunks
- 27
- from 195 cues
- keyframes
- 19
- kept of 32 captured
- frames with text
- 19
- 111 lines read
- chapters
- 0
- from the source metadata
- keyframe bytes
- 2.9 MB
- word timings on 195 cues
Provenance
| stage | state | model | started | took |
|---|---|---|---|---|
fetch |
done | — | 2026-08-11 10:07 | 1m 08s |
stt |
done | — | 2026-08-11 10:08 | 31s |
chunk |
done | — | 2026-08-11 10:09 | 0s |
text_embed |
done | — | 2026-08-11 10:09 | 7s |
keyframe |
done | — | 2026-08-11 10:09 | 1m 26s |
ocr |
done | — | 2026-08-11 10:10 | 4s |
frame_embed |
done | — | 2026-08-11 10:10 | 4s |
Frames, and what the machine read
-
- The Log Is the Agent0.99
- Ishaan Sehgal · CEO, Omnara (YC S25)0.99
-
- What is your character?1.00
- game engine1.00
- playstation1.00
- controller1.00
- save file0.98
-
- Your character is the save file.0.99
- 40.57
-
- what people think the agent is1.00
- model1.00
- runtime / sandbox0.99
- tools1.00
- loop1.00
- framework1.00
-
- The agent is its data1.00
- Specifically: the log1.00
-
- What is the log?0.98
- Event History1.00
- example1.00
- User Input1.00
- user asks1.00
- → model responds1.00
- Model Input/Output1.00
- → tool called0.98
- Permissions1.00
- → permission request0.95
- → human approves0.98
- Tool call and tool result1.00
- → tool result1.00
- → turn completed1.00
-
- Every operation reads from or appends to the log0.99
- Log0.99
- Determine1.00
- Next1.00
- step0.88
- whatever you want0.99
- Handle Next Step0.99
- Append to Log1.00
- adapted from dex's 12-factor agents0.99
-
- Simplified Loop1.00
- while session_has_work:1.00
- state = reconstruct_from_log(session_id)1.00
- response = model.next(state)0.99
- append(response)1.00
- if response.requests_tool:1.00
- result = run_tool(response.tool_call)1.00
- append(result)1.00
-
- Databases learned this first0.99
- 目0.65
- Log1.00
- Tables1.00
- Indexes0.98
- Caches1.00
- 止0.96
- Materialized Views0.99
- Search1.00
- Analytics1.00
-
- Objections1.00
-
- Compaction is not the log1.00
-
- The log isn't the whole world0.99
- its the agents view of it1.00
- World1.00
- Agent Log1.00
- filesystem1.00
- event history1.00
- GitHub1.00
- a. what it did0.99
- email1.00
- b. what changed1.00
- browser1.00
- APls0.91
- database1.00
-
- Once the log is the primitive,1.00
- the properties fall out.1.00
-
- Multiplayer1.00
- SHARED SESSION LOG0.98
- Alex1.00
- Jordan1.00
- 00:240.86
- Designer1.00
- Maya1.00
- Product Manager1.00
-
- Migration / Model Portability1.00
- Claude1.00
- GPT1.00
- Qwen1.00
- Different models, same agent.0.99
Transcript
195 cues· 2,547 words· 14,053 chars
- 0:00 Hey, everyone.
- 0:01 I'm Ishan, the CEO of Omnara, and today I'm going to be talking about the log is the agent.
- 0:06 The basic idea of the talk is simple, and that is most people think of an agent as the model or the execution environment that it's running in, and I think that that's the wrong abstraction.
- 0:17 I think that the thing that actually gives an agent its identity is its log, and that's what I'm going to be arguing today.
- 0:26 So think about a character you've spent 100 hours playing in your favorite video game, in this case Skyrim.
- 0:32 What exactly is your character?
- 0:34 Is it the game engine?
- 0:36 Is it the PlayStation?
- 0:37 Is it the controller?
- 0:40 No, it's not.
- 0:41 Those things matter, and those things are what we'll interact with, and they'll run the character, but none of those things are your character.
- 0:48 Your character is data.
- 0:49 It's the save file.
- 0:52 And this is important because if your PlayStation bursts into flames, your character isn't gone.
- 0:58 You can buy another PlayStation, you can download your save file from the cloud, and you can resume exactly where they were.
- 1:06 And that's because the agent and its identity and history and its state is all captured in its data.
- 1:13 The character lives in the data.
- 1:14 And this is the framing that I want to bring to agents.
- 1:19 Today, when people talk about agents, they usually point at the wrong thing.
- 1:24 They'll say that the agent is the model or they'll say that it's the runtime.
- 1:28 And again, as I mentioned earlier, those things matter, but they're not the agent.
- 1:32 The agent is its data.
- 1:34 It's specifically the log.
- 1:37 So what actually is the log?
- 1:39 At the simplest level, the log is the append-only event history of the agent.
- 1:45 It's every user input, every model output, every tool call, tool result, permission, failure.
- 1:52 And the idea is that every state transition that the agent takes is written to the log.
- 1:58 This is important because it means that the identity of the agent isn't tied to the runtime or the model or the tools.
- 2:06 Those things are all just interpreting and appending to the log.
- 2:09 They're reading the log, acting on it, and writing the next event back.
- 2:14 And that's important because then just using the log on its own is enough to resume the agent.
- 2:22 Once you define the agent as the log, the rest of the system becomes a whole lot easier to reason about because every operation is either reading from or appending to the log.
- 2:33 The model is reading from the log and then determining the next action.
- 2:38 The tool runner is then executing that action and then it's appending that result.
- 2:43 And this is all operating in a loop.
- 2:46 Everything coordinates itself around the log.
- 2:49 In practice, a simplified loop can look something like this.
- 2:52 You can reconstruct the state from the log.
- 2:54 You can pass that state to the model.
- 2:56 The model can propose the next step and then append that response to the log.
- 3:00 If the response asks for a tool, you can run that tool and also append that response to the log, and then you can repeat.
- 3:06 The important insight is not that this loop is complicated.
- 3:10 The important insight is that the loop is disposable.
- 3:13 A worker can claim the session, read the log, advance the agent one step, write the result, and then just completely disappear.
- 3:20 And then that means that any other worker can pick it up later.
- 3:25 This pattern should feel familiar.
- 3:27 Databases had to learn this first.
- 3:29 For years, databases looked like these non-transparent systems that were hard to reason about with tables and indexes and materialized views.
- 3:36 But underneath every serious database is a log.
- 3:41 And
loading