DorkOS 0.131.0 fixes the bar at the top that stayed in place after you left a page, lets agents set how their own scheduled tasks run, and makes messages easier to read. This upgrade only goes one way, so read Going back first.

Highlights

The bar at the top follows you. It now changes when you leave the page you first loaded.
Agents can set how their own scheduled tasks run. On Claude Code, up to their own level, and you can undo a raise. If other people can message your agents, read the Added section below first.
Messages are easier to read. Long paragraphs stop at a comfortable width, and lines have more space.
One way only. This upgrade can't simply be undone. Going back means restoring the backup it saves.

All Changes

Going back

This upgrade only goes one way. DorkOS saves a backup first, in ~/.dork/backups/. If you came from 0.130.0, it's named dork-<date>-<time>-pre-20261102213849_dor3088_todos.db.

To go back to 0.130.0, always restore that backup. Quit DorkOS, delete dork.db-wal and dork.db-shm from ~/.dork/, copy the backup over ~/.dork/dork.db, then install 0.130.0. You lose anything written since the upgrade. Going back without the restore looks fine until an agent's promise fails.

Going back can undo things you changed since the upgrade. If you removed access or revoked a connection, do it again.

Fixed

The bar at the top now changes when you leave the page you first loaded. Before, clicking through to a chat left the old page's bar in place until you reloaded.
A chat started from another chat now reports back when it finishes, even if it ran background commands along the way. If that work is still going after 15 minutes, it says so. A report that can't get through tries again for about 40 minutes, and follows an agent that moved to another account. A restart can still lose a report that's waiting.
DorkOS checks that a linked copy of a project (a git worktree) really belongs to an agent's project before a chat there runs as that agent, and a chat's agent stays the same once it's set.

Added

Agents can now set how their own scheduled tasks run, up to their own level, and you can undo it.

On Claude Code on Trusted, when an agent raises its own task's mode or rewrites its prompt from its own chat, the task usually keeps running. A raise, or a rewrite above Never ask, gets a notice with Undo. On other runtimes or on Careful, it asks you first.
It waits for you if another agent asks. It doesn't check who messaged the chat, so someone else on Telegram or Slack, or a page the agent read, can lead it to make this change, and the change lasts after that chat ends. If other people can message your agents, turn this off. Scheduled runs and heartbeats can't raise a mode.
To turn this off: dorkos config set tasks.agentModeControl false. Agents then can't change a task's mode, and if one rewrites its task's prompt, the task stops and waits for you. Modes already set stay as they are.
If a task's SKILL instructions change outside DorkOS, the task usually keeps running at no looser than Never ask, so some steps may fail. You get a notice.

Also added:

On Claude Code, an agent can move its own seat in a room or DM to another Claude account, from another chat, not while it's answering there. Its account must be at 80% of its usage or more. It can't pick your main account or one you keep out of automatic moves, and it can't move when its usage can't be read. The room gets a line each time.
A correction to the 0.126.4 note: adding an MCP server for every agent is by API, because there's no page for it yet. As the owner, send POST /api/mcp-servers with enabled: true, or the server stays off.

Changed

An agent's text is a little heavier, messages have more space between lines outside compact density, and long paragraphs stop at a comfortable width while code and tables use the full width.
On a phone, messages have more room, because the side margins are smaller.
Pointing at a message in a chat no longer tints it grey. Rooms keep their tint.
Day labels are plain centred text, times lose their leading zero on a 12-hour clock ("2:03 PM"), and there's a little less space between turns.
Menus, pop-ups, tooltips, dialogs and phone sheets now share one look.
Menus have even rows with no lines between groups, and they're easier to tap on a phone.
Tooltips wait a moment before showing, so they no longer flicker as you move past buttons. They don't show on touch screens, except the reason a button is greyed out, and they're no longer a bright white chip in dark mode.
Phone sheets stand out from a dark page, with a real grabber on sheets you can drag away, and left-aligned titles.
On a computer, dialogs open on their first field if they have one, and never on a Delete or Close button.

Known issues

With login off, a promise you add to an agent through the app can limit what that agent's heartbeats may do, and nothing says why. It also can't be dropped from its row. Mark kept closes it and lifts the limit.
Approving a task from its row doesn't show its mode. Use its approval card, which does. Turning on a package's schedule that shipped off doesn't show its mode either.
A task an agent makes can start at a mode where commands that need approval get refused, with no card. It looks ready, then its runs show Needs attention. If you expected those commands to run, you can change its mode under Edit, then Advanced settings.
New schedules start at Full autonomy unless you've changed your default. The mode is under Advanced, so check it before you save.
The notice can say you started a change that someone else's Telegram or Slack message led to. If you don't recognise it, check the chat.