Find the logs
BeyDock writes the helper process's messages to a log file for each device:
~/Library/Application Support/BeyDock/logs/sidecar-<device>.logFor this Mac the file is sidecar-local.log. For an SSH host it is named after the host address, such as sidecar-my-server.log, with other characters replaced by underscores. Each line has a timestamp. A log rolls over at 5 MB and the previous one is kept as .1.
Settings › General › About shows the version and build. Include it when you report a problem.
Common problems
"Node.js not found"
BeyDock runs a small helper with Node.js. Install Node, for example with brew install node, then reopen BeyDock.
A session says the account isn't signed in
Click Sign In in the band above the message box, or open Settings › Accounts and use the … menu. Sign-in runs in Terminal with the provider's command line tool, so that tool must be installed. For SSH hosts, sign in on the host with Sign In on the host name. Models for Codex, Antigravity and OpenCode appear only after the provider signs in.
I can't switch accounts in a session
Only Claude and Codex sessions can switch, and only to another account of the same provider. See Accounts, models and limits. To bring in another provider, use Delegation.
Limits are missing or out of date
Limits appear after an account's first reply. OpenCode has no plan limits. For the menu bar and widgets, check Settings › Menu Bar › Refresh in background. Opening the Usage Limits… panel refreshes that account.
Antigravity skipped a command
Antigravity can't ask for approval mid-turn, so its permission mode decides. Choose a more permissive mode, such as Accept edits or Full access, before you send the message. See Permissions and approvals.
Rewind or Fork is greyed out
Antigravity and OpenCode can't cut a conversation. Claude and Codex can, once there is a reply and the agent is idle. The slash menu shows the reason.
Hub servers are missing in a running session
Sessions that are already open pick up Hub changes when they restart. Only Claude refreshes the connection live. Also check that Settings › Connections › Use BeyDock Hub is on and that the server is available for that provider.
An SSH host won't connect
- Make sure you can run
ssh <host>in Terminal without a password prompt. - In Settings › Devices, click Test and read the message.
- On the device page, use Connect or Retry Now in the Background process box.
- If it says an update is needed and the helper can't update itself, use Restart Now. This stops running sessions and workflow runs on that host, and you can resume the sessions afterwards.
- If the host ends your processes when you log out, turn on Keep running after host restarts.
With Lid Closed doesn't work, or widgets are empty
Both need a build signed with a developer certificate. For closed-lid mode, also allow BeyDock in System Settings › Login Items when asked. See Keep Awake.
Memory use is high
Each open session keeps an agent process. Under Settings › General › Memory, set Close idle sessions after to a time such as 15 minutes. Your next message resumes a stopped session in a second or two. Sessions with running tasks, pending approvals or scheduled wake-ups stay open.
FAQ
Can I move a session to another provider?
No. A conversation belongs to its provider. Use Delegation to hand a task to another provider.
Where are my secrets stored?
Secrets for Hub servers go to the macOS Keychain and aren't written to files. BeyDock never asks for your provider passwords. Sign-in happens in the provider's own tool.
Where are my analytics stored?
Only on this Mac. Under Settings › General › Analytics you can choose how long detailed data is kept and clear it.
Does closing the window quit BeyDock?
Not by default. BeyDock keeps running in the menu bar. Change this under Settings › Menu Bar.
How do I get BeyDock?
BeyDock is in early access. Request a build on the Download page, and the build is sent to you by email.