DorkOS 0.126.3 stops one outside message from making a whole room of agents ask before almost every command, shows pictures and PDFs an agent puts on a room's canvas to everyone, and gives every agent a short list of what it can do in DorkOS.

Highlights

Fewer approval prompts in rooms. An outside message no longer makes every agent in a room ask before almost anything.
Canvas files everyone can see. A picture or PDF an agent puts on a room's canvas now shows for the whole room.
Agents know DorkOS. Each agent starts with a short list of what it can do here.

All Changes

Added

Spaces can now let an owner's or admin's own DorkOS app manage them, but only after that person types their password. The DorkOS app doesn't ask for this yet, so nothing changes for anyone today (DOR-3005)
Making someone an admin, removing a member, and changing who may join a space always happen in the browser, never through an app (DOR-3005)
Groundwork for actions that wait for your approval. The app now understands when DorkOS Cloud holds an action until you approve it, and never treats that action as done. Nothing on screen shows it yet (DOR-3265)

Changed

Every agent now starts with a short list of what it can do in DorkOS, one line per area: chats, rooms, the canvas, browsers, connected apps, MCP servers, tasks and more. Each line names the permission that controls it. An agent asked "can you use my browser?" or "can you add an MCP server?" now answers from DorkOS, instead of pointing you to a terminal or another tool. Before saying DorkOS can't do something, it searches what DorkOS offers.
If your company's network needs its own certificates, and you point NODE_EXTRA_CA_CERTS at them, the Mac app keeps trusting them. It now reads that file itself, so its connections keep working on that network.

Fixed

An extension can no longer change another extension's saved data, secrets or settings through DorkOS: each write is checked against the extension that made it. With Require login on, these writes also need you signed in, or an agent that says who it is, so a program on your computer can't change them with only a key.
When an agent puts a picture, PDF or other media file from its own folder on a room's canvas, everyone in the room can now see it. Before, the agent was told it worked, but everyone else saw a card instead of the file. DorkOS now copies the file into the room. A file outside the agent's own folders is refused, and the agent is told why.
Agents in a shared room stop asking you to approve their commands after one of them reads an outside message. Before, one message from outside your team could make every agent in the room ask before almost anything, and it never wore off. Now an agent that picked up outside words keeps working at its usual level. It still asks you before shell commands, permission changes, and actions that delete things. The agent that read the outside message directly is still held, as before. (DOR-3390)