Goodboy 0.31.12

Every session page, run and agent reads the same way: one page, one dock, one word per state, and an error that says what to do next.

Improved

One page for every agent

Every door to an agent or a step lands on its page, in every kind of run. The page says who the agent is, why it started, its brief and what came back, and its composer targets that agent. The panel beside a chat reads Steps and keeps the error a Failed here points at.

A failed Auto child has one Retry, in the dock. Chat cards are named by noun, and Earlier in this reply folds only what is off screen.

One dock for every conversation

Session, agent, step and Auto conversations share one dock joined to the box. Permission asks and questions read one at a time, with a record left in the transcript, and Failed, Stopped and limit states read there too.

One labeled Stop names what it stops, such as Stop Auto and 2 agents. A message sent over an open permission ask denies it, with the text as the reason.

One word per state

Every state reads one word from one table, in the glance, rows, tails, the sidebar and the Agents panel. An error reads Failed, a limit reads Paused, and a stopped Auto or agent reads Needs you with one sentence.

An Auto that stopped replying raises the same sidebar mark, banner and dock badge as a failed agent. In Overview, one Auto is one block, with its agents folded under it.

Every run has one page

Preset and orchestrated runs share one head and one step list, and a step opens as its own page for both. The run page reads the step state in one word, and step verbs sit in the step head.

The Runs list groups by branch or by state, renames a row in place and says what each run needs. The Agents panel reads top down, and a folded parent says 1 of 2 helpers failed.

A blocked step reaches you

A halted step raises Needs you in Sessions, Overview and the glance, and the notification names the agent with Not finished. The run page shows one word and Open step N. The reason lives on the step page.

On the step page the dock is the only field. Text answers the step, no text asks it to go on, and the draft comes back if the send fails.

Context and linked work

Context is one column: goal, decisions with their marks, summary and explanations. Marks stay until Mark as read, in every window. Questions name their asker and run, and Answered folds behind its count when nothing waits.

Linked work lives in the rail, and a record opens with a way back. A record that left the session or lost its connection says so. The branch tab reads Changes.

Questions and artifacts by branch

Questions and Artifacts group by branch, the way Runs does. A branch with a waiting question goes first, answered ones fold into a count, and work with no branch goes to No branch.

Artifacts show their state as a word on the row, and used ones fold into a count. The Branch page links N runs and N questions, each landing with its group open.

The branch page shows one next step

The Branch page has one primary button picked by state: Mark ready, Merge, Fix comments, Fix checks, Remove worktree or Archive. Five tabs hold the facts: Pull request, Comments, Changes, Commits and Checks.

Merge asks for a confirm that names the target. Remove worktree says what goes and what stays, and has an Undo. Fix checks starts one agent and shows its work inline.

Errors say what to do next

Every reported error ends with what to do next: nothing was changed, your work is kept, check the state before trying again, try loading again, or a settings action. Turn errors read plain and name the agent's provider, with the raw text under Show details.

Each action keeps one name: Retry, Continue, Skip step, Decline, Mark as read and Fix with an agent. Reply replaces turn in the chat controls.

Five rows in every menu

Every menu behind the three dots holds five rows at most, in any state. Artifact, record, comment drawer, branch, commit, worktree and port menus were cut to five, and the least needed rows go first.

Every cut row stays on right click and in the palette. A nested port row keeps Stop and Force stop.

Titles come from the goal

Generated titles for runs, agents and sessions come from a closed title tag or from the words of the goal. A model thinking aloud no longer becomes a title, and a title you edited is never replaced.

A run with an old bad title shows the goal derived one, and your stored data stays as it is.

One hover shows one thing

A tooltip stays quiet while a hover card is open, on rail session dots, board cards and the project dot. Tooltips show plain text, so raw markdown markers leave the rail summary and session titles.

Session pages go back where they came from

A back row names the parent on every session page, and Back lands exactly on it, also from a deep link. Esc walks one ladder: leave a box with text, close the panel, then what the back row does.

Tools stay open when you move inside a session. Every door to a question opens it in Questions, and when nothing is left, Close returns to where you came from.

One head for every tool

Every tool drawer wears one head: icon, name, one action and an Open page arrow before Close. Ask moves above the line, a suggested script runs in one press, and Explore says how many files changed with one Changed only switch.

Messages and stops never get lost

Stop has one path, and a stopped step reads Stopped with Continue to resume it. A sent message is kept until the agent starts. If it cannot start, it stays above the box as Not delivered with Retry.

Closing the window with live work opens one sheet. Composer and question drafts survive a reload and an archive.

The plan reader loses nothing

The plan page has one filled button and one confirm when comments are not sent. A typed comment is kept as a draft on blur, Esc and a press. After a run, unsent comments go to the agent that ran the plan, or you copy them.

One overview line, notifications that land

Overview puts the status line and the summary in one block under the title. A notification opens the place it talks about, from the bell, the toast and the Notifications page, and its button names that place.

Fixed

  • A reload keeps the row, the scope and the archived page you were on.
  • The board reads every fact before its first paint, and a failed read shows one line with Retry above the lanes.
  • A waiting permission survives a reload and a relaunch, and Auto waits reach the board from a hidden window.
  • A plan needs you only for its own planner.
  • Opening Settings no longer moves the text you are reading, and a drawer reveal no longer pushes rows out of view.
  • Holding Enter no longer chains answers, and a late Send as message does not pull you back.
  • A notice with three or more actions wraps them under the text in a narrow window.
  • A queued pull request reads gray, apart from the blue of an open one.
  • Two mounts in a series no longer show a branch switch with a single group.
  • The agent cost footer now shows the same cost as the agent header.