Claude, within reach.
Remote Control in your Mac’s menu bar. Ready when you are.
Download for Mac · Get started · Website · Feedback
Native SwiftUI / macOS 14+ / Free & open source
You shouldn’t need a dedicated terminal window just to keep Remote Control running.
Beamlet gives claude remote-control a small, native home: start it, see its status, open your session, and stop it when you’re done. Pick up the conversation in Claude on your phone or in a browser while the work runs on your Mac.
| What you get | |
|---|---|
| One-click connection | Start and stop Remote Control from the menu bar. |
| Status at a glance | See starting, online, reconnecting, offline, and attention states. |
| An easy handoff | Open in Claude, copy the session link, or show a QR code for your phone. |
| Your workspace | Choose the folder where Claude starts and the CLI installation Beamlet uses. |
| Your routine | Optional launch at login, automatic connection, and attention notifications. |
| Thoughtful recovery | Limited retry attempts after unexpected exits. Pressing Stop keeps it stopped. |
| Stay available | Optionally keep your Mac awake while connected to power and running Remote Control. |
Download Beamlet 0.1.0 — Public Beta. Unzip the download, drag Beamlet to Applications, and open it. The universal app is Developer ID signed and notarized by Apple. See the release notes for beta testing coverage; there is no Mac App Store version.
You need macOS 14 or later, Claude Code, and an account with Remote Control access. Beamlet is free; Anthropic’s account requirements still apply.
In Terminal, go to the folder you want to use and run claude. Sign in with /login if needed, accept workspace trust, then exit Claude. Run:
claude remote-controlAccept its one-time Remote Control consent. Once it connects successfully, press Control-C to stop that terminal session.
Open Beamlet → Settings → Connection and choose that same starting folder. Beamlet detects common Claude installations; you can choose an executable manually if yours is elsewhere.
Use a project folder or a dedicated development folder—not your home directory. Claude’s workspace trust and permissions still apply.
Click Start Remote Control. Once Online, choose Open in Claude, Copy connection link, or Connect your phone.
After setup, Beamlet manages the process without a dedicated terminal window. Keep your Mac powered on and connected to the internet.
Beamlet on your Mac → your installed Claude Code → Claude on your phone / browser
Beamlet manages the process it starts. Claude handles authentication, permissions, project access, and the conversation. There is no separate Beamlet account, AI subscription, or cloud backend.
Closing Settings leaves Beamlet running in the menu bar. Stop ends its managed connection. Quit Beamlet requests shutdown of the process it owns. It does not intentionally stop unrelated sessions you started in Terminal.
Does my Mac need to stay awake?
Yes. This is a connection to work running on your Mac. The optional keep-awake setting applies while Remote Control runs and your Mac is plugged in. The display can sleep; closing the lid can still put the Mac to sleep.
I’m signed in, but Beamlet asks me to sign in again.
Check the installation and account in Terminal:
command -v claude
claude auth status --jsonSelect that executable in Settings → Connection. If it reports that you are signed out, run claude auth login. Being signed into the Claude desktop app does not necessarily mean the CLI is signed in.
Why is it stuck on Starting?
Run claude remote-control manually in the same folder to complete any sign-in, workspace trust, or consent prompts. Stop it before starting Beamlet. Account eligibility, organization policy, CLI changes, and network problems can also prevent startup. See setup and support.
What happens to my data?
Beamlet stores preferences locally and keeps bounded connection diagnostics in memory. It has no added analytics or automatic diagnostic uploads. Claude Code connects to Anthropic under its own policies; this is not a claim that Claude activity stays entirely on your Mac. Keep session links and QR codes private. Read the privacy policy.
Why GitHub instead of the Mac App Store?
Beamlet launches your existing Claude Code installation. The App Store’s sandbox restrictions block that external-executable design. Direct distribution preserves the workflow. The experimental store target is retained for research and is not a working distribution option. Technical findings.
Use Xcode with Icon Composer support (Xcode 26 or later) and XcodeGen. Development here uses Xcode 27. Older supported macOS versions and Intel hardware still need release QA; a universal build alone does not establish that coverage.
git clone https://github.com/BlockchainHB/Beamlet.git
cd Beamlet
bash scripts/build-local.shOpen build/Beamlet.app. This command creates an ad-hoc-signed local development build, not the signed release artifact.
For the Xcode project, run xcodegen generate, open Beamlet.xcodeproj, and select the Beamlet scheme.
swift test --build-system native --sdk "$(xcrun --sdk macosx --show-sdk-path)"
python3 Tests/Runner/test_runner.py .build/debug/BeamletRunnerThe app uses SwiftUI and AppKit, a testable Swift connection-state core, and a small C process runner. See architecture decisions and the direct-release guide.
Found a rough edge? Open an issue with your macOS, Beamlet, and Claude Code versions plus steps to reproduce. Review diagnostics before sharing; never post credentials, private code, session URLs, or QR codes.
Small, focused pull requests are welcome. For changes to process ownership, recovery, or connection parsing, include a test that demonstrates the behavior. Keep the app native, quiet, and easy to understand.
Built by Hasaam. Free under the MIT License. Dependencies retain their own licenses.
Independent community utility. Not affiliated with or endorsed by Anthropic. Claude and Claude Code identify compatibility; no Claude subscription is included.