AGENT WORKSPACES

DorkOS fixes ignored to-do permissions and separates agent browser sign-ins

By IDAKIM Digital · Published November 9, 2026

The November 8 release also restores some Linux Codex starts and adds centrally managed MCP-server connections, with explicit compatibility limits.

DorkOS 0.134.0 makes Blocked and Ask settings apply to agents’ to-do tools; its notes say those saved choices previously had no effect. The release also closes a route where an identified agent could change a to-do through the web API without a permission check. The signed-in browser given to an agent now excludes DorkOS’s own sign-in and local-address sites. Connections gains an MCP-server tab with per-agent access controls, although SSE servers do not reach Codex or OpenCode agents and existing chats can retain a server until they stop. On Linux machines also used by Claude Code, Codex chats start again at Ask first and Workspace write; Full access remains a documented unresolved problem. The database changes are additive, but downgrading loses the newly enforced to-do behavior. These fixes are described by the vendor, not tested by IDAKIM Digital.

Why it matters

Review effective permissions after an update instead of relying on what a settings label used to imply. Test both tool and API access paths. Keep the documented Linux Full access limitation visible, and review revocations before restoring an older database or release.

Source: DorkOS · November 8, 2026

Product claims are attributed to the linked publisher. IDAKIM Digital has not independently tested these claims.