Sokudo v0.19.1 is here. This post rounds up everything shipped since v0.18.0, two releases, v0.19.0 and v0.19.1, and the headline is the chat conversation: every answer now opens with a byline that says who answered and how long it worked, shows its steps as rows in plain words, and reads as plain prose, with swarm workers folded under their lead. Alongside it, the in-app browser's network log follows Chromium's, skills install straight from a GitHub repository, and fixes land across Windows, Linux and macOS, among them language servers that no longer keep a laptop busy over folders your project ignores.
The chat conversation, redesigned
The video opens on a chat called Shop Product Detail, with the Current Tasks pane on the right. Krisna, the Lead Software Engineer persona leading this chat, has answered in plain prose. Under the answer, a card for 11 files changed lists the changed files with their line counts, with Show 5 more files and a group of other files with errors, and its footer says what the language servers checked, beside Review and Undo. Then the message "approved and merged, can continue" goes out.
The new answer opens with a byline, "Krisna · Lead Software Engineer · Working for 0:06", and its clock ticks while the turn runs. Each step lands as a row in words, such as "Reading a task · TASK-285" and "Reading task comments · TASK-285", then the git commands it ran, with short lines of prose in between. When the turn ends, the byline settles to "Worked for 2m 06s" and the answer reads as prose. An Execute plan card, ready to start with one ticket, spawns a worker for TASK-285 in a fresh git worktree, then settles into a single row: "Started 1 worker · Open agent status". Under the lead's answer, the worker gets a byline of its own, "Bagas · Senior Software Engineer · Working for 0:02 · TASK-285", and in Current Tasks, TASK-285 moves to In Progress with Bagas on it.
Steps in plain words
Tool rows read in words with their results, for all eight CLIs: lines read, matches found, tests passed, search results. Sokudo's own tools have their own labels and icons, no raw JSON reaches a row, and a row opens from anywhere on its line, not only from its chevron. A markdown table keeps whole words in every column and scrolls sideways when it is too wide to fit.
Cards that settle into rows
Plans, spec documents, clarify questions and the other decisions an agent asks of you share one card, and once you answer, the card settles into a row, the way the Execute plan card does in the video. A plan has a title, and an SQL proposal says what it changes.
What a turn produced, whether file changes, a slide deck, query results, an E2E run or a worker's result, shares one card style. The file changes card lists only what the turn's own tools wrote, so Undo leaves files changed elsewhere alone.
Swarm workers under their lead
A swarm folds under its lead's answer, and running workers' live output stays visible. A worker reads like every other answer: a byline naming its ticket, its steps as rows while it runs, and its verdict as plain text, with no box of status text below. Only what a worker produced, its changed files and runs, sits on a card, and a finished E2E run shows once, as the card inside the worker's row.
In a swarm without a lead, a reviewer's verdict sits on the card of the work it reviewed, as a numbered review round marked changes requested or approved, with the reviewer's own words one click away. A card that a revision replaced keeps the review that sent it back, the rework collects its own, and a replaced card always reads as replaced: dimmed, with Merge and Discard locked.
Also new since v0.18.0
- A network log that follows Chromium's. The in-app browser's network log has the type filters and filter syntax of Chromium's Network panel, sortable columns, a waterfall, and a status bar with requests, bytes and load times. Request details have Chromium's tabs (Headers, Payload, Preview, Response, Cookies, Timing, Initiator), and you can copy a request as cURL, PowerShell or fetch, replay an XHR, or save all as HAR, with secrets masked. The toolbar reads like a browser's at every width, and Annotate folds to an icon in a narrow pane.
- Install Skill from GitHub. Paste owner/repo or a github.com link, a folder link included, to see the skills a repository holds and install them. Nothing in the repository runs, and only public repositories work for now. All eight CLIs are install targets, and the Universal copy lands in
~/.agents/skills, which most of them read directly. - Database Manager refinements. The namespace picker filters a long list, the SSH tunnel field opens the Remote SSH manager in place, a new source opens with the database you typed already ticked, and every result grid has a pagination pill. The main tabs get the same right-click menu as chat tabs, a database chat shows each SQL suggestion once, and a database chat on codex gets its result cards.
- Find in the diff. On the Changes page, Cmd+F (Ctrl+F on Windows and Linux) finds text in the open diff, and the git history loads older commits as you scroll.
- Each workspace keeps its terminals. Every workspace has its own terminal panel, and terminals survive a window reload. The notification panel scrolls inside the window, and every window shows worker notifications from every workspace, one banner per event.
- The Docker engine reinstalls a missing VM image. A managed engine whose VM image went missing reinstalls itself at launch, keeping your containers, images and volumes, and engine updates are offered for any installed managed engine.
- Open Chat from Agents Status. Every ticket row in Agents Status has an Open Chat button that opens the worker's chat and scrolls to the worker's row, whether the worker is still running or done.
- Chevrons that agree. The merge review dock, the follow-up queue, the background jobs dock and the Database Manager's results strip above the composer point their chevron down when closed and up when open, like every other collapsible in Sokudo.
Bug fixes, performance and stability
Language servers do less work. They no longer receive live changes from folders your workspace's .gitignore leaves out, just as indexing already skipped them, so a PHP app or a build writing into an ignored vendor, storage or cache folder no longer feeds them every few seconds and keeps a laptop busy and hot. On a busy workspace they no longer restart each other every few seconds, which stalled the window, and when the Java language server cannot start because its Java refuses to run, Sokudo says so once, with what to do, instead of trying six times in silence.
In the chat, a reply that starts with a curly quote, an emoji or a CJK letter no longer fails the turn, and a turn cut off while the computer slept says so. An opencode turn no longer fails at start with "server not ready" while opencode is still registering its MCP servers, a CLI whose interpreter is missing shows as not installed instead of failing to start, and on Windows a long prompt to agy no longer fails when agy is installed through a .cmd launcher.
In the in-app browser, a click on Sokudo after you clicked into a page lands on the first press on macOS, the browser menu opens on the first press, zooming no longer crashes a tab on macOS and Linux, and a page that never starts loading says so and offers Try again. The command palette no longer jumps to the top while you scroll. On Windows, a machine without the WebView2 runtime gets a download link instead of a failed start, and a Docker engine that is still coming up is no longer restarted in a loop. On Linux, when the window's graphics process crashes right at startup, Sokudo relaunches itself with safer graphics settings instead of asking you to restart it by hand.
Every app below v0.19.1 takes this release as a required update. As always, Sokudo updates itself. The public beta is open at sokudo.dev, so try v0.19.1 and tell us what you want to see next.
- Changelog
- Product
