How can we help?

Contact hasaamb@gmail.com or open a GitHub issue.

Set up the current direct build

1. Install Claude Code from its official source and confirm your account has Remote Control access.
2. Open Terminal in your project folder. Run claude auth login if you are not signed in.
3. Run claude in that folder and accept workspace trust. Complete Remote Control’s one-time consent when prompted.
4. Stop any Remote Control session you started manually before starting it in Beamlet.
5. In Settings → Connection, choose your starting folder and Claude Code executable. Press Start Remote Control.
6. Once Online, use Open in Claude, Copy connection link or Connect your phone.

Already signed in, but Beamlet asks for login?

Check command -v claude and claude auth status --json in Terminal. Make sure Beamlet uses that installation and the account eligible for Remote Control. Do not send tokens or passwords to support.

Stuck on Starting?

Complete sign-in, workspace trust and Remote Control consent in Terminal first. Check your selected folder and internet connection. Organization policies or an unsupported CLI version can prevent Remote Control from starting.

Does my Mac need to stay awake?

Yes. Remote Control runs on your Mac. The optional keep-awake setting applies while the connection runs and the Mac is plugged in. Closing the lid can still cause sleep.

What happens when I quit?

Beamlet requests shutdown of its owned process. It does not intentionally stop unrelated terminal sessions. Closing the Settings window only closes that window.

Report an issue safely

Include your Beamlet, macOS and Claude Code versions, the steps to reproduce and the displayed error. About → Connection diagnostics lets you inspect and copy recent events. Review and redact anything you share; public GitHub issues are visible to everyone. Never include credentials, working connection links or private QR codes.

See Claude Code’s current Remote Control requirements for supported accounts and configurations.