Twitter/X

@mattpocockuk (post dated 2026-08-05) recommends an interview of @dexhorthy by…

2026-08-05 · 18:01 UTC ·@mattpocockuk ·1 min read

Brief

mattpocockuk highlights a 2026-08-05 interview of @dexhorthy by @GergelyOrosz, relaying Dex's claim that AI coding agents develop session-level "trajectories"—persistent habits and state that affect future behavior. He gives a concrete example (his podcast generator inheriting catchphrases and metric fixation like "wow, 400 bookmarks") and warns codebases tend to accumulate negative state, fixable only via better steering and environment changes.

Why it matters

@mattpocockuk (post dated 2026-08-05) recommends an interview of @dexhorthy by @GergelyOrosz in which @dexhorthy argues AI coding sessions have a "trajectory": agents pick up habits during a session (e.g., if it verifies the app with cURL once, it will likely repeat that step later).

Key details

  • Persistent state across sessions causes bad behaviors: Pocock reports his personal podcast generator (built from his feed) reuses past transcripts, producing recurring catchphrases and an over-focus on meaningless metrics—example quote: "wow, 400 bookmarks on this post!"—and warns that codebases accumulate state and "most trend down."
  • According to the post, the only ways to fix a bad trajectory are better steering of the agent and changing the environment the agent operates in; sometimes you must clear context to change trajectory.
Source evidence

I saw @dexhorthy interviewed by @GergelyOrosz recently - great chat, worth checking out

He talked about how AI coding sessions have a "trajectory"

I.e. the agent tends to pick up habits during the session. If it verifies the app by cURL once, it'll probably do it when you request the next change.

Sometimes you need to clear the context just to change trajectory.

I've even seen this when you have state that's retained across sessions. I've got a personal podcast generated from my feed. All previous podcast transcripts are available for it to view. So it picks up recurring catchphrases, and annoying traits. It's started over-focusing on meaningless metrics (wow, 400 bookmarks on this post!). My podcast is on a bad trajectory.

The "trajectory" metaphor gets really scary for codebases. Codebases are stateful - they accumulate state over sessions. So every codebase has a trajectory, and most trend down.

The only way to fix a bad trajectory is with better steering, and by changing the environment the agent works in.

Cool stuff. Thanks Dex