pitwall v0.2.0

• Shared sessions: one session holds tabs on this machine and on [[hosts]] with window = true, so a tab on box never needs a session switch. The sidebar's + asks which machine a new tab opens on, pitwall new --host box opens one from a shell, and rows, group headers and a row of machines under the header say where each tab runs and how each host is. Remote panes get a tag with the host's name and a ring in the host's color; while a host is down its tabs stay dimmed and read Offline with when they were last seen, typing is off and their answers wait, on rows and on the board, which says the host is unreachable. A tab closed while its host is down closes there once it is back, also when two windows close tabs at once. Killing a shared session waits until every host with a part is up, and ends the tabs here only once each host shows its part gone, also when the window that killed it closed first; pitwall session kill leaves shared sessions to the window. A new task runs on the machine of the folder picked for it, takes that machine's branches and issues, and is refused when that machine's daemon is too old for its schedule or account profile. pitwall new --host refuses --issue, and --guard or a preset's variables on a host daemon too old to keep them. See docs/remote.md, Shared sessions.
• A new tab's folder may start with ~/, the home folder of the machine its daemon runs on.
• The README and site open on one image of three views: the panes, the board and the review view.
• scripts/release.sh guesses only the next patch of the newest release: after v0.2.0 it picks v0.2.1. Cut v0.2.0, or any new minor, with sh scripts/release.sh v0.2.0. The README and site show the current sidebar, the board and the palette, and list the board, confirm close, jump to last prompt and resumes that survive a restart.
• Remove the greyed-out comments button from the sidebar footer. It came from aide and never did anything.
• The board: every agent tab as a card in columns by what it needs from you (Needs you, Failed, Working, PR open, Done, Queued), opened from a button beside the inbox button or with Ctrl+Shift+M (Cmd+Shift+M on macOS). Approvals show the whole command with Allow and Deny; long commands and ones the guard denies send you to the tab. Workers fold into their orchestrator's card unless they need you. Scope it to a group, the ungrouped tabs or a host. A window needs a daemon of this version to show an approval's command.
• Ask before a GUI close stops an agent working or waiting on you mid-turn, including chats and popup agents. The dialog names the tab and agents and asks once, including for several panes. Closing a pinned tab or its last pane uses only the unpin dialog. Closing one pane in a pinned split uses the agent dialog when its agent is mid-turn. Killing a detached tab keeps its two-click confirmation. Turn the check off with [appearance] confirm_close = false or Settings, Appearance, Confirm close.
• Jump to the pane you last sent an agent prompt with Ctrl+Alt+U, or Cmd+Option+U on macOS, across tabs and sessions, including open popups. Only your own prompts count; messages from other panes and automatic messages keep the destination. Rebind jump_last_prompt in Settings. Prompt times stay in memory until the daemon restarts.
• Pane usage-limit auto-resumes keep their saved schedule across daemon restarts and saved shutdowns for the same stopped agent session, including overdue resets. Restored resumes cancel with a visible error after two minutes without a ready agent. Cancelled and consumed limits do not repeat; interrupted working turns get the normal restart message. A crash before typing can still require a manual continue. Chat resumes remain in memory and do not depend on saving pane state.
• Keep the pane's agent status and resume session when it runs another agent during a turn.
• Keep the pane's agent status and resume session when it runs another agent, such as claude -p from its Bash tool, even between turns. pitwall now tells the two apart by the process tree on Linux and macOS, not by session id, so a new agent in the tab is never locked out: Codex after Claude's /exit, a second Claude from the same script, or a new session after a turn that ended without a hook.
• Removed Jev and every decision feature: approval suggestions, risk flags, triage, turn check, check runs, stuck agents, the custom command provider, pitwall jev and the Decisions and Decision stats settings pages. Notifications send at once in the normal order, the jump key follows state order, and TYPESAFE_API_KEY does nothing. A [decisions] table still loads with a note and stays in your file. pitwall no longer reads ~/.local/state/pitwall/decisions.jsonl or ~/.config/pitwall/credentials; delete them when you like.