Skip to content

Troubleshooting

Shivang edited this page Oct 5, 2026 · 2 revisions

Troubleshooting

Start with diagnostics

With the desktop app running:

boss status --json
boss doctor --json

If the command is missing, install the CLI from Toolbox → Tools → Install BOSS CLI. Record the app version, OS, relevant plugin versions, and the exact action that failed.

A browser, terminal, editor, or tool is missing

Check that its plugin is installed and enabled in Toolbox, compatible with your host version, and available to your account. For agent tools, check Toolbox → MCP for disabled tools and verify that the client is attached to the endpoint displayed by this app instance.

No sessions appear at cli.risaboss.com

  1. Confirm the browser and host use the same BOSS account.
  2. For a terminal, confirm sharing is active on the host terminal.
  3. For a BossConsole window, check Share automatically after sign-in, Use media relay, and the status in sharing settings.
  4. Check host capture eligibility: current window-sharing publishing requires macOS 14+ and Screen Recording permission.
  5. Keep the host running and reachable, then refresh the live-session list.

Stopping a share pauses automatic sharing until a later sign-in or explicit re-enable. A saved opt-out stays off.

“Application sharing is unavailable”

Read the status shown in BossConsole's sharing settings. Check capture permission, host OS support, sign-in, and relay availability. Grant capture permission to the exact app instance you are using; a debug build and a released app can have different permission state. Restart when macOS requests it.

“Connecting encrypted media” or “Unable to connect”

Reopen the session from cli.risaboss.com or BossConsole's Remote Connections. An old session can have expired or been replaced after stop, logout, sleep, or a restart.

Use a current browser with the required encrypted media transforms. If your browser reports an unsupported transform, try a current Chromium-based browser. The viewer does not silently fall back to unencrypted media.

If the problem persists, include the visible status and app/browser versions in a bug report. Never paste sign-in links, sharing URL fragments, access tokens, or media keys into a public issue.

Viewing works but input does not

Check whether the viewer actually holds control, whether Allow my devices to take control is enabled, and whether another viewer or local takeover has taken the controller lease. Use Take control to request or retry it.

Click inside the shared surface before typing. Application sharing does not currently enable guest control, clipboard synchronization, file transfer, or audio; native system menus and IME can have separate limitations.

Poor resolution or frame rate

Check the viewer's bottom-bar client and remote measurements. Host capture/encode, the relay path, and viewer receive/decode can each limit smoothness. Compare the reported resolution and frame rate while interacting, and include those measurements when reporting a reproducible problem. A good local network indicator alone does not establish host encode or client decode performance.

A development run ignores local.properties

Environment variables take precedence over system properties, which take precedence over local.properties. Inspect configuration names without printing credential values. Confirm the debug app is using ~/.boss_debug and that plugins were installed into that instance's plugin directory.

File a useful report

For ordinary bugs, open an issue with reproduction steps, expected/actual behavior, versions, and sanitized diagnostics. For a vulnerability, email security@risalabs.ai.

Sources: CLI diagnostics, sharing settings.


Continue: Home · ← Security and privacy

Clone this wiki locally