Key Takeaways

  • Most terminal agent tools wipe local scratchpads or compact context windows, throwing away the human reasoning behind code changes.
  • Amp writes an immutable thread link directly into Git commit metadata by default, preserving the prompt lineage alongside the code diff.
  • Quinn Slack argues that AI agents underperform on real codebases because they lack knowledge of why systems were built, not because underlying models lack intelligence.
  • Preserving prompt history changes code review from line-by-line inspection into artifact verification against the original constraints.

The Context Amnesia of Terminal Agents

Most coding agents operate with complete amnesia. When a software engineer boots up a command-line agent to refactor a service or squash a bug, the tool creates scratch files, summarizes context to avoid token limits, and deletes temporary data the moment the terminal closes. The resulting pull request shows the code diff, but the rationale behind the changes disappears.

Quinn Slack, co-founder of Sourcegraph and founder of Amp, argues this design throws away the most valuable data in modern software engineering.

“Every single thought that a human has had about what you're building is precious,” (play from 26:47) Slack says. “And also, every single token that a model has produced is precious. And we set out with the goal of never wanting to lose any of the human ingenuity and thought, and we never want to lose any of the inference, either.” (play from 26:53)

When a team member inspects that commit six months later, standard version control shows only the modified lines and a terse commit message. It does not record what alternative architectures were attempted, what errors the model encountered, or what explicit boundaries the human engineer set. The new engineer, or the next agent assigned to touch the repository, has to guess at the original design goals.

Why Commits Need Immutable Thread Records

Amp approaches the problem by treating agent sessions as immutable, permanent engineering records. By default, Amp inserts a direct web link to the prompt thread into every Git commit message.

“We do this because the intent, what you are trying to do, is so important, and that is the thing that agents are starved for,” (play from 27:35) Slack says. “That's why we make it by default so that when it commits, it adds little URL to the thread because if all the agent can go off of is the commits, that is usually not as good as if it can see what the human intent was.” (play from 28:08)

This structure turns agent conversations into searchable, versioned engineering assets. As the Changelog hosts noted during the interview: “To be able to go back to a thread from 7 months ago, and it's immutable, it's it is what it is, but to be able to recall it or even to mine it for ideas... that to me is like a really interesting primitive.” (play from 24:46)

Without that record, the next agent called to fix a regression operates blind, unaware of why the previous code was structured that way. Slack states the consequence plainly: “There's no world in which agents can do well if they do not preserve and use the human intent.” (play from 28:57)

From Syntax Review to Artifact Verification

Attaching immutable prompts to version control shifts how engineering teams review software. Line-by-line code review made sense when humans typed every token and needed colleagues to spot syntax bugs. With agents generating hundreds of lines in seconds, reading raw diffs becomes a bottleneck.

Verification replaces line review. Instead of inspecting every line, engineers review whether the output satisfies the prompt criteria without introducing unintended side effects. When the full prompt session is permanently linked to the commit, reviewers can audit the conversation itself: did the engineer test the boundary conditions, did the agent try a flawed approach first, and did the model comply with performance constraints?

What to Do With This

Update your team's Git commit hook or pull request template by Friday. Require every developer who uses an AI coding tool to paste the transcript link or export the raw session history directly into the pull request body. Treat lost prompt history as a missing design document.