This release adds 2 notable features for engineering teams evaluating rollout.
✓ No known CVEs patched in this version
Topics
+4 more
Summary
AI summaryFixed split cards after clearing a session and added session renaming.
Changes in this release
| Type | Severity | Summary | CVE |
|---|---|---|---|
| Feature | Low |
Sessions can be renamed via board UI or `name <callsign> <suffix>` command; renaming is additive and preserves mail delivery to old names. Sessions can be renamed via board UI or `name <callsign> <suffix>` command; renaming is additive and preserves mail delivery to old names. Source: llm_adapter@2026-07-15 Confidence: high |
— |
| Bugfix | Medium |
/clear no longer splits a card into two separate cards; the new session continues the existing card with all state preserved. /clear no longer splits a card into two separate cards; the new session continues the existing card with all state preserved. Source: llm_adapter@2026-07-15 Confidence: high |
— |
| Refactor | Low |
Schema migration adds nullable columns `cleared_at`, `succeeded_by`, and `custom_suffix` to the `sessions` table. Schema migration adds nullable columns `cleared_at`, `succeeded_by`, and `custom_suffix` to the `sessions` table. Source: llm_adapter@2026-07-15 Confidence: high |
— |
Full changelog
claude plugin install fleetdeck@fleetdeck
Fixed
-
A
/clearno longer splits your card in two. The current Claude Code CLI does not keep the session id across a/clear— it ends the old id and mints a new one, which starts in the same directory a few milliseconds later. Fleet Deck believed the opposite, so the old card kept the tmux pane (and therefore the terminal, watch and kill chips) while going permanently silent, and a second card appeared for the new id with no pane at all: you clicked terminal on one card and watched the status updates land on the other. A board-spawned worker that ran/clearstranded its own pane the same way. Now the new session id continues the card: same callsign, same pane, same ticket, same mailbox, same armed move-to-tmux, and the file ledger comes along too (so a session can't raise a file conflict against its own past self). The retired id is archived and can never be resumed — its transcript is a closed chapter. A fleet that already has a pair split this way is healed at boot, so upgrading is enough to put the pane back on the card that is doing the work.The correlation is deliberately narrow, because a wrong merge would be worse than the bug: two sessions clearing in one directory at once refuse to merge, an unrelated new session is never swallowed, a straggler hook cannot resurrect a retired id into a second card wearing the same callsign, and hooks arriving out of order still land one card.
Added
- Rename a session. The animal is the fleet's — the ID part is yours:
wren-a9e1→wren-docs-review. Rename from the board (a✎chip on the card or in the drawer) or from Compose withname <callsign> <suffix>;name <callsign> clearreverts to the automatic name (the ticket name if the card has one, else the birth name). A hand-typed name outranks branch ticket auto-detection — automation never renames over a human — while an explicitticketcommand still takes the name over. Mail addressed to the old name keeps arriving, as with any rename. New endpoint:POST /api/sessions/:session_id/name.
Upgrade note: additive schema migration — three nullable columns (cleared_at, succeeded_by, custom_suffix) on the sessions table. The daemon upgrades itself on your next session (0.7.0's takeover), and the /clear heal runs on that boot.
Full changelog: https://github.com/lacion/fleet-deck/compare/v0.7.0...v0.7.1
Weekly OSS security release digest.
The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.
No spam, unsubscribe anytime.
Share this release
About Fleet Deck
All releases →Related context
Beta — feedback welcome: [email protected]