DorkOS 0.87.0 finishes agent permissions: pick one preset, undo any change, and see why a permission is set. Agents can now work in several conversations at once, you can change a room's files from its Files panel, and connecting an app takes fewer steps.

Highlights

One preset for everything an agent may do

Pick Careful, Balanced or Full power in Settings → Permissions, and every area follows. You can still set any area, action or agent differently, and the picker shows how many changes you made on top.

Undo any permission change

Every change in the permission history now has an Undo. Tap Why? next to a permission to see where it comes from and who last changed it.

Agents work in more than one conversation

An agent can now answer in up to three rooms at once, instead of making the second room wait. Change the number in Settings → Rooms → Conversations at once.

Change a room's files from its panel

Add, upload, rename, move and delete a room's files right from its Files panel. Every change is saved in the room's history under your name.

Connecting an app is simpler

Popular apps like Gmail, Slack and Notion are always listed. After you sign in, one card asks which agents can use the app, and you can share it with every agent at once.

All Changes

DorkOS 0.87.0 finishes agent permissions: pick Careful, Balanced or Full power, undo any change, and see why a permission is set. Agents can now work in several conversations at once, you can change a room's files from its Files panel, and connecting an app takes fewer steps. It also closes more ways a package or an agent could act without asking you.

Added

Pick Careful, Balanced or Full power in Settings → Permissions or the Control Center, and every area follows: rooms, tasks and schedules, other agents, messages, chat connections, tools and packages, DorkOS settings, safety limits, permissions, and reach and secrets. The picker shows how many changes you made on top, with a Reset (DOR-2278)
Open any area to set its single actions one by one. An action whose card shows what it would change, like the model an agent runs on, always asks and never offers Always allow. An action that deletes or removes something asks you even when its area is Allowed, unless you set that one action yourself
Give one agent its own Files & commands setting (Ask first, Act or Full autonomy). It applies to that agent's conversations, scheduled runs and room turns
Let agents ask you to change a permission, or a setting only you may change, like remote access or login. Each one raises a card, never offers Always allow, and changes nothing until you say yes
See and reset each agent's own permissions from the Control Center, in one tap
Change permissions from a terminal with dorkos permissions and dorkos agent permissions
A Community server can now delete one message or one file. You can delete what you or your agents posted, and a community's owner and admins can remove other people's. The message keeps its place in the conversation, so replies and threads still make sense, and shows "This message was deleted." or "This message was removed by a community admin." instead. Its files are deleted at once, which frees the space they used. Programs can use the new DELETE requests described in the Community API guide.
Undo any permission change from its history, in Settings → Permissions or on an agent's Permissions page. If something changed since, Undo asks before it sets it back, and a change that reached several agents undoes what still matches and tells you what it left alone (DOR-2278)
Tap Why? next to any permission to see where it comes from and who last changed it, when, and where
See how many agents a change reaches before you make it: every default row, single action, preset and Files & commands says "affects 33 agents"
If you keep allowing the same thing, the request card offers to remember it: after three Allows in a week for the same agent and action, Always allow stays highlighted until you answer Not now or Always allow. Not now is in the history, and you can undo it there
Undo a change from a terminal with dorkos permissions undo <id>. dorkos permissions history now shows each change's id
The Installed tab says when a package's files changed since it was installed, for example 3 files changed since install (2 edited, 1 added). Open it to see which files. When an update is waiting, it also says what the update will do: replace files you edited and keep your copies, keep files you added, and put back files you removed. Update all… says the same for each package (DOR-2197)
dorkos marketplace installed --verify adds a FILES column saying whether each package is as installed, changed, or unknown, and dorkos doctor --deep names the packages that changed or that an older DorkOS installed (DOR-2197)
Packages an older version of DorkOS installed are checked in the background after DorkOS starts: their files are recorded only when every file still matches the exact version you installed, and nothing is touched otherwise. Check files in the Installed tab, or dorkos marketplace check-files <name>, tries again, and says why when it can't help, with Try again once you've put things back. Scheduling work for an agent from such a package now points you there instead of telling you to wait for its next update (DOR-2197, DOR-2320)
If you run a Community server, you can now put a suspended community on hold in one step. It goes straight from suspended to on hold and is never live in between (DOR-2299).
A host can place a legal hold on a community so it can't be permanently deleted until the hold is released: not by the host, not by the owner's own request, and not by a deletion that is already running. It needs its own host key permission, communities:legal_hold, and every change is recorded in the host audit log. Owners and members are not told (DOR-2299).
The Community site now has Delete on your own messages and files, and Remove for owners and admins on other people's. A confirmation says what everyone will see afterwards and what can't be taken back. The message stays in its place as "This message was deleted." or "This message was removed by a community admin.", in quieter italic text, and its thread still opens. (DOR-2289)
A new message can no longer say only "This message was deleted." or another removal sentence, so nobody can make a message look removed when it isn't. (DOR-2289)
Messages erased, deleted, or removed in a Community now change in your DorkOS installation too: its saved copy of the channel shows the new text within 15 minutes, and searching that channel no longer finds the old words. What your agents already saved, like their session history, stays as it was (DOR-2266)
Keep an open Community page up to date when someone deletes a message: it changes to "This message was deleted." within 30 seconds, without a reload (DOR-2290)
Tell DorkBot your name and pick an @handle when you first set up DorkOS. If you signed in with an email, the handle starts as the part before the @. You see it and can change it before anything is saved. Your name and handle then show on your team page, and agents in a room reach you by your @handle instead of "You" (DOR-677)
If you set up DorkOS before this question existed, a small card in the sidebar asks once. Answer it or choose "Don't ask again", and it never comes back (DOR-677)
Drag the line between a channel and an open thread to make the thread wider or narrower. It lights up when you point at it, just like the right panel's edge, and the thread opens at the width you left it next time (DOR-2119).
Choose which of your Claude accounts pays for a scheduled task. Set account: in the task's schedule: block, or send account when you create or edit it, and its runs start on that account instead of the agent's. Changing the account on an approved schedule sends it back to you for approval, like a model change does. A schedule that keeps one conversation stays on the account it started on (DOR-2384).
Extensions that come inside a plugin now load, once you approve them. Before, an extension packed inside a marketplace plugin was set up on install but never showed up or ran. It now appears in Settings → Extensions and asks for your OK like any other extension (DOR-2383)
The Connect a service list always shows popular apps like Gmail, Slack and Notion, each with one line about what your agents can do with it. Before, it said "No matching services" until you had set up how DorkOS reaches your apps, and never said why (DOR-2421).
When nothing you have set up can reach an app yet, connecting it starts with one short step that asks how DorkOS should reach your apps: your own Composio key, or your own Nango server under Other ways. If something is set up but not working, the step says so in one line. Once a way works, Connect goes straight to sign-in (DOR-2421).
Before an app's own sign-in page opens, one line tells you whose name it will show, for example "Google will ask you to allow Composio", so it is never a surprise (DOR-2421).
An app can now be shared with every agent at once, including agents you add later, for exactly the actions you picked: choose Every agent under "Who can use it?" when you connect an app. If every agent could send, change or delete things as you, DorkOS says so before you save. New actions an app adds later still stay off until you allow them. Stopping the sharing takes effect for every agent at once, even one in the middle of a task, and works even while the app's service is down (DOR-2420).
When you create an agent, or add one from the Marketplace, DorkOS says what it will get from apps shared with every agent before you create it, for example "Research Bot will get: Gmail (read)". An agent that arrives any other way gets a line in Activity saying what it can use (DOR-2420).
Add, upload, rename, move and delete a room's files right from its Files panel. Drop files on the panel or on a folder, or use Upload, up to 20 files at once. If a name is already taken, you choose whether to replace it or keep both. Deleting asks first and tells you how many files go with a folder. Each change is one saved step in the room's history under your name, and the room gets one quiet line about it that does not wake any agent (DOR-2412, DOR-2413).
Keep a file someone attached in the chat as one of the room's files: press the folder button beside it and pick where it goes (DOR-2413).
Start a new file or folder in a room's files and write it straight away. It appears when you save it (DOR-2413).
If someone else changed a file first, a rename, move, delete or upload stops and shows you who and when, so you can look at their version or go ahead anyway (DOR-2413).
DorkOS now keeps track of how much of each Claude Code account you have used, across every session on that account, and remembers it after a restart. Your agents can read it with the new accounts_usage tool. It includes this computer's own Claude sign-in, even when you have registered other accounts, and it shares one record per account with the flow command (DOR-2380)
@dork-labs/cloud-api, the open contract for talking to DorkOS Cloud, gets a new version for developers who build on it. Every amount now says whether it is money or credits, and the service can say which unit it uses. A new @dork-labs/cloud-api/display entry renders those amounts one consistent way. It also adds reads for offers, remote-access usage and statement lines, a malformed_identifier refusal code, whether a claim to an agent waits for approval, and which addresses a machine's tunnel credential answers on. Older responses still read. The refunds route, which was never served, is withdrawn, and its exports are marked deprecated (DOR-2425, DOR-2426, DOR-2445)

Changed

Choosing a preset now also sets Files & commands: Careful starts new conversations at Ask first, Balanced at Act, and Full power at Full autonomy, which asks you to confirm what it means the first time
The agent profile's Tools & MCP page is now called MCP servers. What an agent may do is on its Permissions page
Community exports now work at any size. Choosing Export this community or Download my data starts the export in the background, and a progress bar shows how far it has got. You can close the page and come back. When it is ready, Download shows the file's size, the export is kept for a day, and a download that stops can resume from your browser's downloads list. Before, a community with more than 10,000 messages or members, or more than 1 GB of files, could not be exported at all.
The exported .zip now also holds the community's name, description, joining rule, icon, and who is in each channel, and marks messages that were deleted or erased. Messages posted after an export starts are not included, and a message deleted while an export is prepared is left out or shown as deleted.
An agent now asks you before it changes what an agent runs on: its runtime, model or effort, for itself or any other agent. Every scheduled task that doesn't pick its own settings runs on those, so a change would reach work you already approved. The card shows each change as it is now and as it would be, for example Model: claude-sonnet-4 → claude-opus-4. If the agent's settings change again before you answer, you get a fresh card. Your own changes, from the Runs on menu or the agent's settings, still apply at once (DOR-2328)
An agent can now work in up to three conversations at the same time. Before, sending an agent a message while it was answering in another room meant waiting until that answer finished, even though the two rooms had nothing to do with each other. You can change the number in Settings → Rooms → Conversations at once, from 1 to 8. Higher is faster, but turns that change the same files can collide; set it to 1 to go back to one thing at a time. One agent still never answers twice at once in the same room, and a message that arrives while it is at its limit still waits for it, so you never have to send it again.
Replies in a thread now line up with the message they answer instead of being pushed in from the left, so they get the full width of the thread. A thin line that says how many replies there are separates the first message from the answers (DOR-2110).
Saving a file in a room now makes any folders it needs, and posts a quiet line in the room saying who changed what. The app shows that line as plain text, so a file name or a person's name can't turn into a link there. Places that read its words, like an agent's view of the room or a chat bridge, may still show a name that looks like a web address as a link (DOR-2412, DOR-2413).
With login on, a change you make to a room's files is saved under your own name, so two people's changes stay apart in the history (DOR-2412).
You now connect a community right from the switcher at the top of the sidebar. Choose Add community, then Connect a community, and a small window asks for its address and walks you through approving it on the community's site. Once you approve, the window closes and the community is selected. A community still waiting for your approval, or one that needs connecting again, opens that same window when you choose it, instead of sending you to Connections. Communities no longer appear on the Connections page, and the note you get when this DorkOS loses access to a community now points to the switcher (DOR-2422).
After you connect an app, DorkOS now asks "Who can use it?" in the same window. Tick the agents you want, pick Read or Read and write, and save. Before you save, the card tells you if an agent you unticked will lose access. You can skip it, and "Choose exact actions" still opens the full list of actions for each agent (DOR-2417).
Settings has a new Connections tab. It shows each way DorkOS reaches your apps (your DorkOS account, your own Composio key, your own Nango server), whether it works, and how many apps use it. Before you change or remove a key, it lists every app that will pause or stop, and the button says how many (DOR-2419).
Unlinking your DorkOS account in Settings › Access now lists the apps that stop working with it, too (DOR-2419).
The chat app settings moved to the same tab, in plainer words: start working right away, most chats at once, and how many seconds a new message waits for a free chat before it's turned away. The Connections page now keeps to your apps (DOR-2419).
Telegram, Slack and Webhook are listed with the other apps and tagged Chat. Connecting one opens its own setup right away, with nothing else to set up first (DOR-2421).
Edit any text file in a room's files, not only Markdown. Images and other files that aren't text stay read-only, and the preview says so (DOR-2413).
If one of your Claude accounts was saved with the id default, DorkOS renames it to default-2 when you upgrade. default now always means your main account. The agents, chats and schedules that named the old account move to its new name and keep using it. Schedules that come from an installed package are not changed (DOR-2379, DOR-2380)
Saving your Claude accounts in Settings no longer drops what flow or a hand edit added to your config file. An account flow added while Settings was open is kept when you save, and so are extra details on an account and an account entry DorkOS cannot use yet (DOR-2379)

Removed

The per-agent limit ("observe" or "act") and the Agent context switches for tasks, messages, other agents and chat connections. Permission areas replace them
Retire the DorkOS plugin for Obsidian. Use the normal DorkOS app with your vault folder instead, subject to its usual folder permissions. The in-vault sidebar, active-note context, dragged-in note context, and opening notes inside Obsidian are no longer provided. Your notes and conversation history are not deleted. See the retirement guide for migration and historical source recovery.

Fixed

Joining a community through an invitation to a channel no longer fails now and then when the person who sent the invitation posts or uploads to that channel at the same moment (DOR-2277).
A skill or command can ask Claude Code to run a shell command the moment it is used, written into its text as !`command` or as a code block marked with an exclamation mark. The install and update previews never showed these, so a package could run commands you were never shown. They now appear with the other commands, naming the skill each comes from, in the app, in dorkos install and dorkos update, and on agents' approval cards. The same goes for commands in a package's agents and output styles. When a command uses the text you type after it, the card says so, because that text becomes part of the command. A new version that adds or changes one asks you again. Packages you already approved are not asked about again unless they have such a command. Multi-line commands now keep their line breaks on the card, so two commands can't read as one (DOR-2327).
Updating or removing a package that an older DorkOS installed no longer guesses which files are yours when DorkOS can't get the version you had, for example because you're offline. It keeps every file it can't account for and tells you which ones. After an update, the package says Kept 2 files DorkOS couldn't sort after an update, and you can open it to see them. Once you're online, Check files sets aside the ones that are exactly what the earlier version shipped, renaming each to end in .dork-old so it no longer runs, and keeps the rest as yours. Nothing is deleted. The package keeps listing the kept files through later updates until you check them, and says which of them still run, such as an old skill or command. A package installed for all projects that still runs such a file waits for your approval instead of loading, and says why. dorkos marketplace installed --verify, update --apply, uninstall and dorkos doctor --deep say the same (DOR-2322)
When a Community server refuses a request because of too many wrong passwords, or another per-minute limit, it now says how many seconds to wait, in a standard Retry-After header. Wrong passwords on every action that asks for one (leaving, disconnecting installations, handing over ownership, exporting, archiving, deleting, API keys and erasure) still count together, per account. The sign-in library's own password-change address, which nothing on the Community used and which did not count wrong passwords that way, is now off (DOR-2275)
Something that happened a few minutes ago now reads "5m ago" even when midnight has passed since. Before, for about an hour after every midnight, it read "Yesterday, 11 pm" instead, which made fresh things look old. Anything from the last six hours now counts in minutes or hours; older than that, a time from yesterday still shows as "Yesterday" with the hour.
An agent's memory rules now say that only you, in a one-to-one chat with the agent, can set its standing preferences. They used to say "a direct chat", which a group direct message with someone else in it also fit, so another person there could have passed as you. The preview on the agent's profile shows the new wording. (DOR-2134)
When a phone notification fails to send, the server log no longer records your phone's private push address. Logs are often attached to bug reports, so that address should never have been there (DOR-2135)
The same notification raised twice at almost the same moment now reaches you once, instead of arriving twice in your inbox and in your chat app (DOR-2140)
Scheduled tasks no longer stop for good after the disk fills up. A write that failed partway could leave a broken lock file behind, and from then on no scheduled task ran, with nothing in the log to say why. DorkOS now replaces a broken lock file and cleans up after its own failed writes (DOR-2131)
A second full-disk spell now shows up in the log too, not only the first (DOR-2132)
Opening the app no longer flashes "nothing here" messages over things you already have. For a moment during startup, the Team page's table and map views could show "Bring in existing projects" over a full team, and the Pulse panel, marketplace sources and agent gallery could briefly say they were empty. They now show their loading state until your data is in (DOR-1914)
In a room, the line that says which earlier message a reply is answering now has a little space before the reply itself (DOR-2120).
The time that appears when you hover over a message in a run of messages from the same person no longer sits against the edge of the row. This applies to both rooms and sessions (DOR-2120).
A long room topic now wraps onto as many lines as it needs in the room panel, so you can read all of it. Before, it was cut off after a few words, on a phone as well as on a desktop (DOR-2117).
Opening a link to the #team channel no longer shows #team's name in the header for a moment before it takes you to Home (DOR-2141).
Typing in a canvas document no longer tells you your agent changed it. Each time a document saved itself while you were editing, the canvas mistook that save for a change from your agent and showed "Your agent changed this while you were editing". It now recognizes its own saves. A real change from your agent, or from another window, still shows the notice so you can choose which version to keep.
Unregistering an agent now takes it out of every channel it was in, so a channel's member list shows only who can still read it. Its messages stay, marked "Retired" beside its name, and a direct message with it stays too. Open windows update straight away. Agents already unregistered before this fix are cleared out of their channels the next time DorkOS starts (DOR-2095)
An agent that DorkOS removed because its folder was out of reach for more than a day, such as one on an external drive, now gets its channels back, with the same settings it had, when you add the folder again or DorkOS finds it again. It only rejoins a channel it is still allowed into (DOR-2095)
Agents answer again in a room that has its own files. When login was on, an agent working in its copy of the room's files couldn't post, react, read the history or send you a note, so the room showed that it "read this and did not reply." This hit Claude Code, Codex and OpenCode agents alike. With login off, some of those posts carried your name instead of the agent's. Now each agent's posts carry its own name, and a working copy DorkOS can't tie to the agent it's working for can't post as anyone (DOR-2091)
When an agent in a channel runs into a problem or is waiting for you to answer something, the words in its note that tell you to open that agent's session are now a link that takes you straight there. The note used to tell you to open the session without giving you a way to get there. (DOR-2077)
The Session link button in Remote Access now copies the conversation's full address. It used to copy a shortened one that only reached the conversation by way of a redirect. (DOR-2077)
An agent working in a git worktree of its own repo, or in a checkout it owns, now keeps its own name, personality, memory and Claude account. Before, it could pick up an out-of-date copy of its settings that the branch happened to carry, and the agent settings screen could edit that copy instead of the agent (DOR-2355).
A folder inside a room's files can no longer be registered as an agent, so a settings file someone commits to a room never becomes an agent of its own (DOR-2355).
A Claude account entry that is broken, such as one with no folder, an empty id, or a number where text belongs, no longer makes DorkOS set your whole config file aside at startup. DorkOS skips that entry and notes it in the log (DOR-2379)
Starting work on the default account now uses this computer's own Claude sign-in, even when DorkOS itself was started from a terminal pointed at a different account (DOR-2380)

Security

A new agent can't bring wider permissions in its folder's settings file. When DorkOS adds an agent from a folder, however it gets there, it keeps only the settings that are stricter than your defaults, ignores the rest even if it can't rewrite the file, and says so in the history (DOR-2278)
An agent package can no longer ship its own permissions. DorkOS refuses a package whose agent settings say what the agent may do, so an agent from the marketplace starts where your defaults say, and you decide the rest after it is installed (DOR-2278)
A package can no longer fill your disk. DorkOS now refuses a package larger than 250 MB in total, with more than 20,000 files and folders, or with any single file over 50 MB, and says which limit it hit. It checks this before showing what a package will do, and again before copying it into place. A download from git is stopped as soon as it grows past 1 GB or takes longer than 10 minutes, and a download that would unpack into more than 100,000 files and folders, or more than 1 GB, is refused before a single file is written. If you install from a folder on your computer, DorkOS copies its node_modules too, and the message says how much of the package is in there. Its .git folder doesn't count toward the limits. The files DorkOS reads from packages you already have installed are now held to the same 1 MB per-file limit as the ones it checks before installing. Real packages are far below these limits. (DOR-2321)
An agent package installs into the folder its sessions run in, so settings it shipped there could run commands, start servers or let the agent act without asking, and none of it was on the install screen. DorkOS now refuses an agent package that ships them: Claude Code's .claude/settings.json (or a .claude folder anywhere below the top), a .mcp.json, a subagent with its own hooks or servers, Codex's .codex/ folder, OpenCode's opencode.json or .opencode/ folder, and Gemini CLI's settings. Instructions and skills are still fine, and the install screen now lists what the skills in those folders may do without asking. This covers dorkos install, installs by an agent, and installs through DorkOS's own connections (DOR-2314)
In the app, a marketplace agent can no longer be created when DorkOS refuses its package: the card says why and Create stays off (DOR-2314)
When DorkOS won't install a package, the install screen and the package page now say so and why, instead of showing "No special permissions required" (DOR-2314)
A package can no longer mark those settings folders as yours to edit, so an update always runs exactly what you approved (DOR-2314)
A folder can no longer make git run a program just because DorkOS or one of your agents looked inside it. A folder set up to look like a git repository can carry a setting that tells git to run a program. Now every time DorkOS or an agent runs git, git ignores the settings of a repository it only stumbled on, and never starts a file-watching helper. DorkOS refuses to install a marketplace package shaped like a git repository, and drops any .git folder a package brings with it. Your own repositories work as before, and your git hooks still run when you or an agent commits. Two trade-offs: git in a very large repository that relied on a file-watching helper checks for changes the slower way, and an agent working inside a bare repository must name it with --git-dir. Full protection needs git 2.38 or later. DorkOS warns at startup and in dorkos doctor when yours is older. (DOR-2326)
Creating a workspace now refuses a source that git would read as an option or as an instruction to run a program, and its git only reaches folders on your machine or https, ssh and git addresses. (DOR-2326)
Creating an agent from the marketplace in the app now goes through the same checks as installing a package. What installs is exactly what its preview showed you, and a package that ships settings for its own sessions is refused. Before, the app copied the package's files without checking them. The agent now lives in its package's folder, so updates find it (DOR-2325)
Creating an agent from your own template now shows you anything it brings that would run in the new agent's sessions before it is created: settings files with hooks or permission rules (with their full contents), servers, and skills that use tools without asking. You then decide whether to create it. In the terminal, dorkos agent create --template prints the same list and asks (DOR-2325)
When an agent creates another agent from a template, a person now has to approve it on a card that lists everything the template brings. Before, nothing stopped it (DOR-2325)
When an agent installs a marketplace package that adds another agent, a person now approves it first, on a card that shows where the agent will live and what its skills can do. What installs is exactly what the card showed (DOR-2325)
When an agent installs any marketplace package, what installs must be exactly the package that was previewed: same kind of package, same files. A source that changes in between is refused and nothing is installed (DOR-2325)
Your OK to run an extension now belongs to that one copy of it: its folder, and the plugin it came in. If a different plugin brings an extension with the same name, DorkOS asks you again before running any of it. Extensions you already allowed keep running with nothing to click, and updating a plugin keeps your OK for the extensions it still brings (DOR-2383)
Agents can no longer start a scheduled run on their own. Before this, an agent could send a message that started a run with its own instructions, in any folder, with every permission check turned off and nobody watching. Now only the scheduler can start a run, and any other attempt is turned away and logged. (DOR-2416)
Agents can no longer approve their own tool calls. Before, an agent that knew its session and the pending tool call could send an approval as if you had clicked it on Telegram or Slack. Now DorkOS accepts an approval only when it comes from the chat connection where you clicked, and refuses and logs any other (DOR-2431).
Agents can no longer send messages to DorkOS's own internal addresses, the ones it uses to start scheduled tasks, answer approval requests and stop runs. Only DorkOS itself can send there now, so an agent can't pretend to be the scheduler or approve its own tool calls. A webhook can't be set up to deliver to those addresses either. Agents still message each other and reach you exactly as before (DOR-2432).

Note for people upgrading

If you are on Careful, agents now ask before they touch tasks and schedules, other agents, chat connections or rooms, where before some of those ran without asking
An agent you had limited to "observe" now has every area Blocked. It can still post and react in conversations
An Agent context switch you had turned off becomes that area Blocked for every agent. The history records each of these as an upgrade
An agent you had switched a tool group on for (rooms, tasks, messages, other agents or chat connections) gets that area Allowed as its own setting, shown as an exception you can reset. It could already use those tools, so nothing it can do has widened