Blackcrab v0.1.3

Blackcrab 0.1.3: steadier sessions and cleaner transcripts

Blackcrab 0.1.3 is a focused quality release for the parts of the app that
people touch every day: switching between conversations, reading long
transcripts, and keeping local Claude Code sessions connected reliably.

This release is not a broad feature drop. It is the kind of update that makes
the existing app feel calmer under real use.

Conversations keep their place

The biggest fix in 0.1.3 is conversation continuity across mode switches. When
you move from grid mode into a single conversation, then back to the grid, the
app now keeps better track of which backend panel owns each conversation and
which transcript should receive new events.

That matters most when a response is still running. Previously, switching views
could leave the grid showing an older snapshot, or cause the next single-mode
open to hit a "session is being used somewhere else" warning. Blackcrab now
tracks panel ownership and transcript state more deliberately so active
sessions can continue without fighting over the same saved conversation file.

Transcripts are easier to scan

Long Claude Code sessions can get noisy fast. Tool calls, command output,
thinking blocks, file reads, patches, and permission flow all compete with the
actual conversation.

In 0.1.3, transcript blocks use more compact drawers. Tool output folds by
default when it is not an error, while failures stay visible. Summaries now show
useful context, such as paths, command descriptions, line counts, task counts,
and whether a background command is involved.

The goal is simple: you should be able to skim a session, find the important
parts, and expand the raw details only when you need them.

Claude session startup is cleaner

This release also tightens how Blackcrab prepares Claude Code sessions. The app
refreshes Claude auth state before spawning a session, while avoiding direct
injection of keychain access tokens into spawned processes.

That keeps session startup aligned with the local Claude Code CLI and reduces
the amount of credential handling Blackcrab needs to do itself.

Update health is now measurable

Blackcrab can now send anonymous app and updater events to the landing site's
analytics endpoint. These events cover app launches, update checks, update
starts, completed updates, and update failures.

The setting is visible in Settings and can be turned off. The privacy docs and
README were updated to explain what is sent and why: the data is meant to help
understand whether releases are installing successfully, not to inspect local
sessions or Claude traffic.

Upgrade notes

There are no manual migration steps for 0.1.3. Users on 0.1.2 should be able to
install the update normally through the app or download a fresh installer from
GitHub Releases.

As usual for an early desktop build, the release is still macOS-first, with
GitHub Actions also producing Windows and Linux artifacts for testing.