v0.20.5

Release 0.20.5

v0.20.4

What's Changed

• feat(events): add notify-only Events pipeline with local reminders by @chrisjowen in #196
• chore(release): 0.20.4 by @chrisjowen in #202

Full Changelog: v0.20.3...v0.20.4

v0.20.3

What's Changed

• feat(settings): add read-only Settings → Firstmate page by @chrisjowen in #200
• chore(release): 0.20.3 by @chrisjowen in #201

Full Changelog: v0.20.2...v0.20.3

v0.20.2

What's Changed

• feat(mates): show a Fleetyard second mate's link as This Mac → Fleetyard → machine by @chrisjowen in #198
• chore(release): 0.20.2 by @chrisjowen in #199

Full Changelog: v0.20.1...v0.20.2

v0.20.1

What's Changed

• fix: keep last report, PR and next step visible for lost and relaunched workers by @chrisjowen in #197

Full Changelog: v0.20.0...v0.20.1

v0.20.0

What's new

• One decision in both places (#192): a held decision now has one id, its task's, across the chat and the Decisions page. When Firstmate asks a held decision in the chat with decision-form id=<task>, the chat shows that decision's own card, so answering it in either place shows it answered in both. Other chat forms are marked "Quick question · not a tracked decision".
• Clearer decision cards (#192): each card is headed by a short question with a line of context, links its task (and the task it came from), lists the reports, docs and patches it rests on in a closable reader, and shows the preview and screenshots as thumbnails that open over the page. Firstmate's own words and the hold's internals sit under Details.
• Other and Dismiss everywhere (#192): every card and chat form takes an answer in your own words, and any decision can be dismissed with a reason, which asks Firstmate to close it as dismissed.
• Chat with Firstmate about this (#192) opens the main chat with a message about the decision started, and keeps it as Following up: still listed, no longer counted as waiting, on every browser, until you answer it or put it back.
• Worker chat on every task (#191): a read-only Chat tab on each task shows the worker's conversation, with opt-in crew discussions for local workers.

npm i -g @chrisjowen/wheelhouse@0.20.0 · https://www.npmjs.com/package/@chrisjowen/wheelhouse/v/0.20.0

v0.19.4

What's new

• On deck states as icons (#187): each line on the home page's On deck rail now leads with its state as a small nautical icon instead of a word tag on the right. A ship sails on a moving wake while its worker is busy, sits becalmed when it is not responding and aground when stuck, and rides at anchor when idle. A lighthouse sweeps its beam while checks run, and a danger buoy marks a failed step. A gold signal flag means it is waiting on you. A spyglass means it is with reviewers, a compass means Firstmate is deciding, a mooring buoy means queued, and a moored ship means landed.
• Quick tooltips (#187): point at an icon, or move to its line with the keyboard, and its state shows at once in Wheelhouse's own tooltip. Screen readers still read the state.
• Stuck and failed work flashes (#187) so it stands out. Every icon stays still when your system asks for reduced motion.

npm i -g @chrisjowen/wheelhouse@0.19.4 · https://www.npmjs.com/package/@chrisjowen/wheelhouse/v/0.19.4

v0.19.3

What's fixed

• Workers stay visible after a merged PR (#185): when a task's first pull request merged and its worker carried on with a follow-up in the same task, Wheelhouse showed it as Landed, so it dropped out of Under way, "in play" and its project's counts while the worker was busy. A worker that reports work after its merge now stays in play until the task is done; once it opens a new pull request, its passage follows that one.
• Every terminal type (#185): workers on Firstmate's other runtime backends (hc, herdr and the rest) are listed like tmux ones, with their live view. Where Firstmate did not observe a worker's terminal, the task still shows and says the live view is not available for that terminal type.
• Finds hc and herdr (#185): Firstmate's scripts also look in ~/.local/bin, so a Wheelhouse started without it on PATH no longer reports those workers' terminals as gone.

npm i -g @chrisjowen/wheelhouse@0.19.3 · https://www.npmjs.com/package/@chrisjowen/wheelhouse/v/0.19.3

v0.19.2

What's new

• Every skill in the / menu (#183): the chat's / menu now lists every skill and command the Firstmate session can run. That covers Firstmate's own, your personal ones (skills/ and commands/ in $CLAUDE_CONFIG_DIR, else ~/.claude), and enabled plugins' skills as plugin:skill. As in Claude Code, a skill is offered unless its front matter says user-invocable: false, so skills no longer need user-invocable: true to appear. Where two share a name, the one Claude Code runs is kept.
• See where each one comes from (#183): the menu groups commands under Firstmate, Personal, Plugin <name> and Built-in. Groups stay together while you type.

npm i -g @chrisjowen/wheelhouse@0.19.2 · https://www.npmjs.com/package/@chrisjowen/wheelhouse/v/0.19.2

v0.19.1

What's new

• Never silently stuck in the terminal (#181): when Firstmate's session waits on you in its terminal for something the chat cannot show (a sign-in error to retry, a first-run screen, a dialog Wheelhouse does not know, another agent's prompt), the chat says so with a Firstmate is waiting for you in the terminal card showing the last lines of its screen and Open terminal, which opens the drawer with the keyboard in it. The status reads Waiting on you in terminal, the menu marks Firstmate Needs you, the ship's bell rings, and your message waits instead of being typed into that screen.
• Sign in from the chat (#181): an agent's sign-in screen (Claude Code's sign-in link and Paste code here, Codex's browser or device-code sign-in, Pi's login) shows as a Sign in card that opens the sign-in page and types the code you paste back into the session, only while that same sign-in is on screen.

npm i -g @chrisjowen/wheelhouse@0.19.1 · https://www.npmjs.com/package/@chrisjowen/wheelhouse/v/0.19.1