DorkOS 0.82.0 puts your own DorkOS and every community you've joined behind one switcher. Marketplace packages now install and update the version they say they will, and sending us feedback is simpler. Communities are still early.

Highlights

One switcher for all your communities

The switcher at the top of the sidebar takes you between your own DorkOS and each community you've joined. It remembers where you were in each one, and ⌘⇧K opens it even while you're typing.

Package updates you can trust

DorkOS now notices when a marketplace package has a new version, and installs exactly the version its listing names. If an install is cut short, you get the old version back.

A simpler way to send feedback

You write in one box, with your screenshot and anything you pointed at inside it. If you close the form by accident, your draft is still there.

All Changes

DorkOS 0.82.0 lets you move between your own DorkOS and every community you've joined from one switcher, and marketplace packages now install and update the version they say they will. The feedback form is simpler too. Communities are still early.

Added

Move between this DorkOS and each community you've joined from the switcher at the top of the sidebar. On a phone, it opens as a sheet from the top bar, with your settings and account still at the bottom. The switcher remembers your order and where you left off. Messages from one community never show up in another, even after you sign in as someone else. Press ⌘⇧K (Ctrl+Shift+K on Windows and Linux) to open it, even while you are typing in a message box.
When you switch from a community back to this DorkOS, you land on the page you last had open here. Reloading and your browser's Back button still take you to the address in the bar.
Community rooms now reopen at the message you were reading. Each room and thread keeps its own place.
The switcher shows mentions of you apart from other unread messages in each community. When a community can't be reached, its counts are marked as last checked.
Community channels now follow what you're allowed to do there right now. If a community's server can't be reached, you can still read saved messages, but posting waits until it's back. Archived communities stay read-only. If a community removes your access, or you leave it on its site, DorkOS notices within seconds and clears its private messages until you reconnect. If you had it open, you go back to your own DorkOS. Other communities are not touched.
Hand a new community to its owner with one link. When a host administrator creates a community, they now get an owner claim link to copy and send. The owner opens it, creates an account or signs in, and lands in their new community as its owner. The link works once and lasts 24 hours. The secret sits after # in the link, so the browser never sends it with a page request, and the page removes it from the address bar before loading anything else. (DOR-2181)
The context switcher now has a Manage menu for the community you have open. Invite people, Community settings and Leave community open that community's own site, at the right page, where it checks your sign-in. The DorkOS app's own settings stay under Workspace settings, so the two never mix. Disconnect asks first, then removes only that community from this app. You stay a member (DOR-2185).
Add community in the switcher now offers three separate paths. Connect a community links this DorkOS to a community you are already in. Join with an invitation opens an invite link you were sent on the community's own site. Run your own community opens the guide for setting up your own community server (DOR-2185).
Not signed in? The form asks for your email, so we can tell you when your report is fixed. It remembers the address in this browser for next time (DOR-2232)
On a phone, the You tab now has Send feedback, Your reports and Documentation as rows of their own, and the command palette has a Your reports entry (DOR-2232)
Close the form by accident and your draft is still there when you open it again. Press ⌘↵ (Ctrl+↵ on Windows and Linux) to send, and the thank-you links to Your reports (DOR-2232)
Sending the same report twice within a minute is caught, so it doesn't get filed twice (DOR-2232)
Reload without losing your invitation. If the page reloads while you are joining a community, it still shows the community, who invited you, and any channel the invitation includes, and you can still create an account or sign in. The invitation link itself is still never saved by the page. (DOR-2181)
See what rejoining brings back before you rejoin. If you were a member before, the invitation lists what returns (your name and handle) and what stays removed (your old role, earlier channels, agents, and connected DorkOS installations). (DOR-2181)
If you run a Community server, you can now give a program its own key instead of your password. Create one under API keys on the host page, choose what it may do (read community records, create communities, or suspend and resume them), and copy it once. A key can never read messages, files, or members, and it cannot create other keys. You can replace a key without downtime, or revoke it at once. A headless server can create its first key from the command line with node dist-server/host-keys.js (DOR-2253).
If you run a Community server, you can now set limits for each community on the host page: the most members and the most file space, each shown beside what it uses now. Lowering a limit never removes anyone or anything. It only stops new members or new files once the community is full. Exports never count, so an owner can always download their data. A program with a host key can also give one person more or fewer agents than the server's default, and read how much each community uses without seeing any names or messages (DOR-2254).
Sign out of a community site from the browser you are using. Find it in Settings, under Account, or on the page where you choose a community. Only that browser is signed out. Your memberships stay, and your connected DorkOS installations keep working. (DOR-2181)
Disconnect all your DorkOS installations from a community at once. In Settings, under Account, confirm your password and every installation you connected there stops reading and posting until you connect it again. You stay a member, and your installations in other communities are not affected. (DOR-2181)
dorkos update checks every package you have installed in one go. That includes packages installed for a single agent. A package installed in two places now shows up as two lines, each saying where it lives, like flow [Alpha]. With --apply, it lists what it updated and anything it couldn't update, with the reason. Programs can ask the same question with GET /api/marketplace/updates and apply updates with POST /api/marketplace/updates, either for named packages or for exactly the installations a check listed. A package folder you linked in from your own copy is checked but never replaced; its line says to update the source instead (DOR-2194)

Changed

The Send feedback form is simpler. You write in one box, and your screenshot, the part of the app you pointed at, and the buttons to add them all sit inside that box. Diagnostics and the conversation are small switches under it, each with a preview (DOR-2232)
The page with the reports you've sent is now called Your reports, in the help menu, its tab and its title (DOR-2232)
The help menu has three items now: Send feedback, Your reports, and Documentation. Report a bug is part of Send feedback (pick Bug), and the public GitHub option is a link at the bottom of the form (DOR-2232)
Pointing at part of the app no longer writes code names into your message. It shows up as a small picture named by the words on it, like "Set up a daily run", and the box asks what's wrong with it. You need to add a few words before you can send (DOR-2232)
When joining fails, the page now says plainly that membership was not added, tells you if your new account was still created, and offers one next step: try again, open the link again, or ask for a new invitation. (DOR-2181)
The community chooser works fully by keyboard and screen reader, explains why a suspended community can't be opened, and tells you when a community link you opened isn't available to your account. With no memberships yet, it tells you how to join. (DOR-2181)
DorkOS no longer installs a package whose .dork/manifest.json and .claude-plugin/plugin.json state different versions, and says which file says what. Packages you already have stay installed and can still be updated or removed.
dorkos marketplace validate now fails when a marketplace entry lists a version that the package's own plugin.json contradicts, since Claude Code would quietly ignore the entry's.
When a community is full or out of file space, you now get a plain message that says so, and an invitation to a full community says it before you sign up (DOR-2254).
The DorkOS app now names a community's agent limit when you add an agent. An older DorkOS app talking to an updated Community server shows "That no longer matches the community" instead; update the app to see the plain message (DOR-2254).
Each connected installation now says what it can do (for example "Can read and post") and asks before it disconnects. The question says what ends and that you stay a member. (DOR-2181)
Leaving a community now lists what ends (your membership, its channels, and the installations and agents you connected there) and what stays (your account, your other communities, this browser's sign-in, and your past messages). A wrong password now says so and that you are still a member. Other refusals, like needing to transfer ownership first, now give their real reason. (DOR-2181)
DorkOS now tidies its store of downloaded marketplace packages on its own. After each download it keeps what your installed packages need, plus an update that is waiting to be installed, and removes the rest. Before, the store only grew, and checking for updates often would have filled your disk over time. (DOR-2249)
If DorkOS can't read one of your projects, for example on a drive that isn't plugged in, it removes nothing from the store until it can, and dorkos cache list tells you why. (DOR-2249)
dorkos cache prune now follows the same rule and no longer takes --keep-last-n. The old option could delete the exact copy an installed package came from. (DOR-2249)

Fixed

A closed community no longer accepts new invitations or members. Setting a community's admission to Closed already cancelled the invitations that were out, but an owner or admin could still make a new one and someone could join through it. Now no one new can be invited or join until the owner switches admission back to Invite only, and people who are already members keep their access. In the community's settings, the invite panel says the community is closed instead of offering a button that would not work (DOR-2178).
When an agent asks for a service by a name DorkOS doesn't know, such as "composio-emails", the refusal now tells it how to search for the exact name, and lists close matches when there are real ones (DOR-2231)
When no services are set up in DorkOS yet, an agent's request now says so and names the one step for you: open Connections in the DorkOS app and set up Accounts (DOR-2231)
Agents are now told that signing in to a service's command-line tool in a shell does not give DorkOS access. Before, nothing said so, and an agent could spend a turn installing one (DOR-2231)
A service an agent can find in DorkOS's service list is now a service it can ask for. Before, a request could be turned away while your linked DorkOS account was reconnecting, or when the list was too long to check in one go (DOR-2231)
Asking for a Messaging-only service like Telegram now tells the agent that you set it up under Messaging, instead of sending it back to search again (DOR-2231)
A screenshot attached to a bug report from the browser now shows the conversation you were reading. If you had scrolled through a conversation, the screenshot showed an empty list, or one message under a large blank space, even though the messages were on your screen. This happened both when you captured the whole app and when you pointed at one part of it. The desktop app was not affected. When a report includes diagnostics, it now also shows each error's actual message instead of {} (DOR-2230).
Bug reports now scrub private details from the diagnostics they carry. Folder paths that include your user name, secret-looking keys and passwords, and the query part of web addresses are removed before a report is sent, including from the crash details attached to a report (DOR-2230).
dorkos community deploy works with the current Fly CLI again. It created your Fly app and then stopped, saying it could not tell whether the app had been made, and left the app behind. It also refused to start at all if your Fly organization already had any apps in it. It now recognizes the app it just made by its name and the organization you picked, and it reads your existing apps without tripping over details the Fly CLI leaves blank. It still never takes over an app in a different organization. Setting up file storage would also have failed at the next step, because the launcher gave Fly the organization's short name where Fly needs its ID; it now looks up the ID first (DOR-2169).
Disconnecting this DorkOS from a community now ends its access on the community too, not just the copy on your computer. Before, the community still listed this DorkOS as connected after you disconnected it. If the community can't be reached when you disconnect, DorkOS still disconnects here and tells you, so you can finish under Connected installations on the community yourself.
When a community turns down a request, you now see why instead of "Community unavailable." For example, adding an agent past the community's limit says you've reached the limit on active agents. "Community unavailable" now means only that the community couldn't be reached or had a problem on its side. A private channel you haven't joined still looks exactly like one that doesn't exist.
dorkos update and the Update button now notice new versions of marketplace packages. Before, they always said everything was up to date. (DOR-2244)
When DorkOS can't check a package for an update, it says so and why (for example, "couldn't reach github.com"). It no longer calls that package up to date.
dorkos update with no package name now checks every package where it is installed, including packages installed for one agent. A problem with one package no longer stops the rest, and naming a package that isn't installed still ends with an error.
The installed list now shows the version Claude Code actually runs, even for a package whose own files disagree about its version.
A message you started in a community channel and did not send is now still there when you switch to another community, or back to this DorkOS, and then return. Files you attached to it come back too. Before, switching away threw the message away. It stays in that one channel of that one community, is never shown anywhere else, and is thrown away if you sign out or that community's connection ends (DOR-2241).
A marketplace package now installs the branch, tag or exact commit its listing names. Before, many installs quietly took the repository's newest code instead, and a package pinned to a commit or kept on another branch could fail to install. (DOR-2248)
The commit DorkOS records for an installed package is now always the code that was actually installed, so the version shown and the update check can be trusted. (DOR-2248)
A package kept in one folder of a larger repository now installs even when that repository's default branch has another name, like master. (DOR-2248)
When a branch, tag or commit doesn't exist, the install stops with a plain message saying so, before anything is downloaded. (DOR-2248)
If DorkOS stops in the middle of installing a package over an older version, you get the older version back. Before, a crash at the wrong moment could leave you with neither version, because DorkOS later deleted the saved copy of the old one instead of putting it back. (Updating a package is not covered yet; that fix is on its way.)
A package that was half-installed when DorkOS stopped is cleaned up the next time DorkOS starts, instead of showing up broken. If you have since put something of your own in its place, DorkOS leaves it alone.
When two copies of DorkOS work on the same project, one no longer undoes an install the other is still in the middle of. If you try to install a package while the other copy is installing it, DorkOS tells you how many minutes to wait.
A leftover saved copy of a package no longer shows up as a second copy of it: not as a second Shape, not as a second agent in the health check, not as extra skills for your coding agents, and not as a second copy of a scheduled task.
Small grey text on a community site is now dark enough to read against every background, and links inside text are underlined, so you can tell them apart without relying on colour. (DOR-2182)
Every button and field on a community site is now at least 44 pixels tall on a phone, including the menu button that opens the channel list and the owner claim field in host administration. (DOR-2182)
The on/off switch on each messaging connection in Connections now says which connection it turns on or off, so a screen reader no longer reads it as just "switch". (DOR-2182)
The two buttons at the bottom of a confirmation, like "Keep connected" and "Disconnect", are now full-size touch targets on a phone. (DOR-2182)
Warning and error text is easier to read. The red used for error messages and for buttons like Delete and Reset was too faint against the background in both light and dark mode. It is now a slightly deeper red in light mode and a slightly brighter one in dark mode, so every error message and red button label meets the standard contrast level for readable text. Red buttons in dark mode now use the same deeper shade the main Delete button already had.
Updating a package with --project no longer moves a package that is installed for everything into that one project. Each package is now updated where it is installed (DOR-2194)
A marketplace whose server stops answering no longer stalls an update check for minutes. After 15 seconds the check falls back to the last copy DorkOS saved, or says it couldn't reach the server (DOR-2194)
A self-hosted community server now shuts down cleanly when it is told to stop twice, for example when you press Ctrl-C and your process manager sends its own stop signal too. Before, the second request crashed the shutdown, so the server exited with an error and printed a stack trace even though nothing was wrong. It also stops within about five seconds when people have channels open, instead of waiting for them to leave, and a second Ctrl-C while it is stopping ends it at once (DOR-2221).
A file or data export that finished downloading no longer breaks the next request if your access to its channel ended at that moment. The download was already complete, but the community cut the connection afterwards, so whatever the app or browser sent next on it failed. You still can't download any more of a file once your access has ended (DOR-2250).
The community list no longer waits for a slow community. Before, if one community took a long time to answer, the whole list waited for it, sometimes for ten seconds or more, every time it refreshed. Now each community gets under a second.
A community that doesn't answer in time keeps the unread and mention counts it last reported, marked with when they were last checked. If it hasn't answered for a while, it shows as offline: you can still read what's saved, and it comes back on its own at the next refresh. A slow answer never makes DorkOS ask you to reconnect. (DOR-2223)

Security

Limit password guesses everywhere a community site asks for your password: leaving, disconnecting all installations, handing over ownership, exporting the whole community, archiving, restoring or deleting it, and creating or replacing a host API key. After 5 wrong passwords in a minute, that account's password-protected actions are refused for the rest of the minute, even with the right password. Other people are never locked out by someone else's guesses, even when everyone reaches the server through the same proxy. A wrong password now always says "That password is not right." and that nothing changed. A server owner can change the number with COMMUNITY_REAUTH_ATTEMPTS_PER_MINUTE. (DOR-2181)