Skip to content

fix(browser): allow ordinary task authority to switch desktop panels #81

Closed

Description

@trmosala

Description

desktop_set_panel is advertised and allowed by the plugin, but the native router rejects it whenever an authority object is present. The production bridge supplies an authority object for ordinary tasks as well as delegated tasks.

Priority: high. Reviewed CookieMonster CM-Split-v2 at dafdcd4171466050c984d524ca0d1a09d31f100e; links use the identical remote V2 source on Ubuntu 26.04.1 x64, Bun 1.4.2.

Steps to reproduce and evidence

Called the production routeBrowserRequest with a valid set_panel/review request and createBrowserDelegations().authority(sessionID) for a normal task. It returned access_denied: Browser operation interrupted or unavailable. The request parser accepted the same payload.

Acceptance criteria and verification

  • Distinguish ordinary task authority from delegated authority explicitly; do not reject merely because authority exists.
  • Preserve task ownership, paused/access-disabled checks and delegated restrictions.
  • Add bridge-to-router coverage for review, hidden and authorized browser panel selection.

Source and related work

packages/desktop/src/main/browser/router.ts, packages/desktop/src/main/browser/bridge.ts, packages/desktop/src/main/browser/delegation.ts, packages/cm-browser/src/plugin.ts.

Activity

  1. trmosala commented on Oct 21, 2026

    @trmosala
    OwnerAuthor

    Merged into CM-Split-v2 as 290d7d6353c0c7a4a356af780b5687f2dcfe5cfc through PR #96. Its tree exactly matches reviewed source 68ab9205709350385471eb2d383b3cff3c18e678.

    Implemented in PR #96, reviewed source 68ab9205709350385471eb2d383b3cff3c18e678.

    Ordinary authority is distinguished explicitly from delegated authority. Bridge/router coverage permits ordinary review, hidden and authorized browser panels while preserving task ownership, paused/access-disabled denial and delegated restrictions.

    Final verification is deferred at the user's explicit request to finish and close the implementation issues before one final test pass. This closure records implementation completion, not a claim that the final combined/platform checks have passed. Any failure in that pass will be recorded against the relevant issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions