> For the complete documentation index, see [llms.txt](https://dsg-3.gitbook.io/dsg-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dsg-3.gitbook.io/dsg-docs/cinema-proof-agent/runtime-and-integrations/dashboard-and-shared-browser.md).

# Dashboard and Shared Browser

One customer screen for chat, connection, exact-plan approval, shared browser control, and five live governance views.

The customer-facing workflow is centered on `/dashboard`.

## One screen

```
/dashboard
   │
   ├─ Agent Chat
   ├─ Connect Agent
   ├─ Remote ON / OFF
   ├─ Shared Browser — User + Agent
   ├─ Inline exact-plan approval
   │
   └─ LIVE MONITOR
        ├─ ACTION
        ├─ PLAN ALIGNMENT
        ├─ PERMISSION
        ├─ EVIDENCE
        └─ EXECUTION / AUDIT
```

## Shared Browser model

Cinema uses one account-scoped browser state for direct user interaction and approved Agent execution.

```
                 SHARED BROWSER SESSION
                         │
             ┌───────────┴───────────┐
             │                       │
          USER INPUT              AGENT INPUT
             │                       │
             └───────────┬───────────┘
                         ▼
                   SAME PAGE STATE
```

Agent actions remain plan-bound. Remote OFF revokes Agent remote authority; it does not have to destroy the user's browser/login context.

Low-level Agent mutations are serialized on the Azure-native path. Do not assume a stronger global USER+AGENT arbitration guarantee unless the specific runtime path proves it.

## Chat behavior

Dashboard chat is transport to a real paired Agent. Cinema does not fabricate a local Agent response to make the UI appear connected.

The Agent may propose a plan. The Agent cannot approve the user gate on the user's behalf.

## Credential boundary

Passwords, OTP values, CAPTCHA answers, and passkeys are not intended to be transported as ordinary Agent MCP action payloads. Browser state and credentials never replace plan authorization.