Daily Edition Sources +3

Crush Stops Writing To Vanished Shell Sessions

A public Crush patch moved shell-message persistence behind a session-existence check, turning a disappearing workspace edge case into tested agent reliability work.

Diagram Punk poster showing a Crush shell transcript blocked from writing to a missing session by a tested persistence guard.
Diagram PunkCrush stops shell transcripts from writing into vanished sessions.
repo charmbracelet/crush evidence
3 source signals 1 repo 2 linked commits
Evidence: 2 linked commits / June 30, 2026 / Daily Edition
Open Edition Evidence below

syf2211 authored commit a9e3a57 on June 30, adding persist_message.go and a regression test so Crush skips shell persistence when the session no longer exists.

The visible pressure is ordinary and important: an agent shell can outlive the workspace record it thinks it is writing to. The intervention pulls that edge case into a small helper and a test instead of letting persistence stay hidden in backend flow.

The public trail

The patch changed four files with 115 insertions and 19 deletions. The new test covers the missing-session path directly, while agent.go and app_workspace.go delegate message persistence into the new shell helper.

Related public work

Another same-day Crush patch by syf2211 fixed non-ASCII directory trimming in commit 188dea6. The pairing matters because both changes protect the human edge of agent tooling: shell output and file paths must not corrupt the operator's view.

Why it matters

For agent operators, this is a reliability story rather than a feature story. Long-running shell tools are useful only if the transcript they leave behind reflects a live session. The fairness limit is tight: the article credits public commits and public profile evidence only, not private motive or maintainer status.

Evidence Trail

Receipts below the story

The article above is the public narrative. This section keeps the source trail and limits on the same page.

Edition
DateJune 30, 2026
LaneDaily Edition
Confidence78%
Sources3
Reposcharmbracelet/crush

Primary Evidence

Evidence Limits

  • The article does not infer private identity, motive, employment, location, or maintainer authority.
  • No public issue thread carries the story; the visible trail is commit and test evidence.
  • The patch does not prove how often missing-session persistence occurs for users.
Letters & Corrections

Send a note to the desk

Corrections, missing context, or a follow-up lead.