Agentic experiences

Converse. Simulate. Search.

Agents can give us richer experiences than a chat window: conversations worth sharing, simulations we can walk through, and searches over the paths we didn't take. Each one is a way to learn faster, work faster, and create more value.

The problem

The useful part rarely survives the session.

Transcripts nobody opens

The question, the wrong turns, the moment it clicks. All of it sits in a log that is never read again.

Postmortems you nod at

Accurate, but flat. You read about the 2 a.m. incident. You don't feel it.

One path, never the others

Experience shows you what happened. It rarely shows what would have happened if you chose differently.

Three kinds of experience

Each one shows more of the problem.

None of these is new. This is my attempt to bucket the kinds of rich experiences we can build with agents.

Read it

Conversations

One path, captured. A good exchange with an agent is a record of thinking that someone else can pick up later.

Play it

Simulations

Walk the path yourself. The agent assists by playing the parts around you. You decide what to try.

Explore it

Search

See the paths you didn't take. Run the simulation many times, vary the choices, and the shape of the problem appears.

Today · Conversations as blog posts

Publish the conversation itself. Let readers bring their own agent.

Saves the exploration

Someone already paid for it. Readers start where the conversation ended instead of rediscovering it.

The reasoning is already done

The chain of thought is laid out in the transcript. Readers build on it instead of starting from scratch.

Any format you like

A summary, a checklist, another language. The reader's agent slices it, and the original stays there to check against.

Each post is authored before it goes out: reviewed, trimmed and scrubbed of anything private. Read them at golden-convo. The process is written down as skills, so anyone can share their own.

Next · Engineering experience as simulations

The hope: next time the pager goes off, it isn't the first time.

Much of what makes an engineer good is experience they can't easily hand over. Postmortems are accurate, but flat. So the incident becomes a playbook, and the playbook becomes something you can play.

  1. Real incidentthe 2 a.m. page
  2. Playbooksignals, decisions, outcomes
  3. Scenariothe agent assists
  4. You decidewhat to try
  5. See where it leadsthen try another call

Not a quiz. A small, safe version of having been there.

Where it leads · Search

Search isn't new. Agents bring it to messier problems.

Trying many options and keeping what holds up already powers these fields. Agents bring the pattern to situations that were too messy to simulate before, like an incident. It is only as good as the simulation behind it.

Policy simulations

See how a rule plays out before it reaches real people.

Hyperparameter and architecture search

Explore settings and new architectures for neural networks, LLMs included. For example, karpathy/autoresearch.

Engineering incidents

Replay an incident many ways and see which calls hold up.

How I plan to build

A careful core. A community that extends it. A place to share what it makes.

Platform

A place to share the content, and the knowledge in it.

Extensions

Rich content in many formats. I build the first ones, then open it to early users.

postssimulationsplaybookswhatever comes next

Core

Often a deterministic tool, high quality and built to be extended. How we play with it can be agent-assisted.

The work so far

Built in the open.