# Known limitations

Account for these current client boundaries when choosing where Foxora work runs, and recheck the latest release notes for changes.

- Web cannot grant Desktop operating-system permissions or change another device’s browser mode.
- Signing in on a second device does not automatically copy the first device’s local projects, task history, browser profile, or conversation memory.
- Foxora Browser and Background automation require the optional Browser Pack; My Chrome requires Foxora Connect.
- CLI headless output is human-readable text and does not currently define a `--json` output contract.
- Desktop and CLI are versioned separately, and the connected engine can carry its own build identifier.

These are product boundaries, not proof of an outage. Use **Settings → System**, **Settings → Browser**, and `foxora doctor` to distinguish missing setup from a failing service.

**Expected result:** the task is placed on a client and device that can provide its required data, permissions, and output format.