What changed

1.0.3 2026-09-09 current

Fifteen changes have piled up since 1.0.2. Most of them are the My work panel; the rest fix places where the window tried to tell you something and could not.

My work — the dashboard

• The seven stacked strips are now a card grid that takes its columns from the width. Standing beside an editor, that is seven screens of scrolling you no longer do.
• Right now — the whole queue as one ring, with the total in the middle. It is the number you used to get by adding two tiles together.
• The next two weeks — one cell per day. A list of due dates cannot answer “is next week flat, and are five of them piled on Thursday?”
• Where it is stuck — the columns crossed with age. Forgotten before anyone started it is a backlog; forgotten while somebody is on it is a standup question.
• By who raised it — half the queue is review requests, and that is a question about people.
• Hovering a chart opens a second layer. It shows the make-up, the share and the ticket names as rows rather than as a sentence, and the same thing stays on every element as an aria-label.

My work — tickets

• Ticket detail is two columns now, the way Jira draws it: prose (title, description, conversation) and fields (status, assignee, priority, dates) are read differently.
• The comment thread is read and written here. A two-line description with the decision down in the comments is the ordinary shape of a ticket, and until now those two lines were all that was shown.
• Title, description, priority, labels and due date can be edited, and only the changed fields are sent. A form that submits every visible field turns fixing one typo into a write that also reverts somebody else’s edit.
• The list carries an issue type mark — bug, story, task, epic, subtask. A type a project made for itself keeps its own name and gets a neutral mark.
• The “this sprint” toggle is now a cycle dropdown. The backlog and past sprints are visible too.

The window

• The message under the header is now a card like the toasts. A red rule had nothing about it that read as a notice, so the one thing saying why the button you just pressed did nothing was the thing you looked past.
• File marks are the language’s own — a logo where there is one, a letter tile where there is not.
• A file from outside the workspace opens when you drop it in, read-only.
• Long lines leaked out of the diff, and side-by-side cut them off outright. Both fixed.
• “Needs attention” was announced several times over before a turn had even ended. Fixed.

1.0.2 2026-09-09

Twenty-three changes piled up since 1.0.1. It is also the build where the app updating itself actually happens for the first time — the verifying key is compiled into the binary, so 1.0.0 could not ride this channel, and 1.0.1 → 1.0.2 is that first leg.

Terminal

• While Korean was being composed, old output turned up behind the input line. Fixed.
• Shift+Enter submitted instead of breaking the line, and Cmd+←/→ sent no bytes at all. The terminal encodes both itself now.
• Paste went in twice. Fixed.
• Right-click has a menu — copy, select all, paste, clear the screen, split the group.
• Scrollback now defaults to 1MB. An agent that redraws its screen spends most of its bytes on colour and cursor moves, so 256KB was far shorter than it sounded.

Where the window froze

• Re-reading scrollback, pasting, taking a review baseline — everything that waited on the thread that draws the window has been taken off it. The four-pane layout that came out with three panes went with it.

My work

• Sprints arrived. A row says which cycle it is in, and the bar grows a toggle only when a cycle is actually running.
• Bitbucket Cloud loads again. Atlassian removed the endpoint it used on 2025-02-20, and signing in had answered 404 ever since.

Opening it for the first time

• The three steps are laid out where you are. Working out what to press first in an empty window is no longer the state you start in.

Smaller things

• The notices at the bottom right were redrawn, and the settings gathered into cards.
• Dark-theme text colour is set from a target contrast rather than from the floor.
• “Check for Updates” is in the menu bar.
• finished is out of the default notifications — waiting had already arrived when the agent handed the turn back, and the process going away is the same news one beat later, so one thing was being announced twice.

1.0.1 2026-09-08

The first build anyone could actually get. 1.0.0 was built too, signed and notarised, but its release files sat in a private repository and answered 404 to anybody without a token.

• The download address hands over a file now. Installers go out to a public repository.
• The in-app updater is in the app from this build on. The verifying key is compiled into the binary, so 1.0.0 cannot ride this channel.
• The icon has a plate behind it.
• “Go to file” opens onto a list of files. The empty screen went to text search.

How an update arrives

The app checks for a new version itself. When there is one the window asks in a banner, and the download and the restart both happen <strong>after you press</strong> — it does not fetch on its own and it does not restart on its own. “Check for Updates” in the menu bar asks right now.

• What comes down is one signed file. The verifying key is inside the app, and a signature that does not match is not installed.
• Version numbers only go forward. A build that went out wrong is not rolled back; it is fixed and goes out under the next number.
• On 1.0.0 you cannot ride this channel — take it from Download and install over the old one. Installing over the top is a valid update from any version.