WEBVTT

00:00:01.290 --> 00:00:02.640
Hi, I'm Lentil!

00:00:02.640 --> 00:00:06.691
Google's ax promises consistent agent state and automatic recovery.

00:00:10.017 --> 00:00:11.394
Ownership is per conversation.

00:00:11.394 --> 00:00:15.181
The lock is a Go map inside one process, and the

00:00:15.181 --> 00:00:16.558
reference deployment runs three.

00:00:19.092 --> 00:00:23.569
Google draws it as one controller, one event log, and the actors it drives.

00:00:23.988 --> 00:00:27.170
Both claims live in the two arrows at the top: one writer,

00:00:27.170 --> 00:00:28.761
and a log to recover from.

00:00:30.217 --> 00:00:31.248
A turn arrives.

00:00:31.248 --> 00:00:36.061
The server adds the conversation to an in-memory map, and refuses a second caller.

00:00:36.481 --> 00:00:38.857
Each step is appended to a shared log.

00:00:38.857 --> 00:00:41.233
When the call returns, the map entry goes.

00:00:41.233 --> 00:00:42.421
No lease, no fencing.

00:00:42.841 --> 00:00:45.081
But the map lives in one process.

00:00:45.081 --> 00:00:49.240
A second replica has its own empty map, and admits the same conversation.

00:00:49.660 --> 00:00:54.008
In the author's test, both replicas were admitted, and one ran the turn twice.

00:00:55.608 --> 00:01:00.128
Replay reduces the log to two fields: the last state and the harness.

00:01:00.128 --> 00:01:02.213
Nothing records which tools already ran.

00:01:02.633 --> 00:01:03.450
Post the turn.

00:01:05.787 --> 00:01:06.967
Get back tool calls.

00:01:08.718 --> 00:01:09.240
Run them.

00:01:09.240 --> 00:01:10.807
That's where the email gets sent.

00:01:11.427 --> 00:01:13.319
Only then does the cursor move.

00:01:13.319 --> 00:01:15.841
Crash between, and a resume reruns the tools.

00:01:17.175 --> 00:01:21.602
Measured: one interruption and one follow-up ran the work three times: fourteen

00:01:21.602 --> 00:01:24.184
irreversible actions, where six were asked for.

00:01:26.192 --> 00:01:29.953
Before, ax was a framework: you rewrote your agent as its service,

00:01:29.953 --> 00:01:31.206
speaking its message types.

00:01:31.865 --> 00:01:33.601
In September it deleted all that.

00:01:33.601 --> 00:01:36.494
Now your agent is just a command in a container.

00:01:38.350 --> 00:01:40.780
Making a decision cheap is a modelling problem.

00:01:40.780 --> 00:01:44.122
Making sure it's acted on only once is a systems problem.

00:01:46.733 --> 00:01:51.078
To recap: a per-process lock, a two-field replay, and effects that can repeat.

00:01:51.498 --> 00:01:53.599
Every source is in the full article.

00:01:53.599 --> 00:01:54.199
I'm Lentil.

00:01:54.199 --> 00:01:54.499
Bye!
