How to Use Beam.win: The Beginner's Guide to Beaming Your Agents' Mac Windows to Your Desk

CodexFuse Team · 2026-11-03T01:57:48.258Z · 15 min read min read

You have a second Mac — maybe a headless Mac mini in the closet — grinding away at builds and AI agents while you work at your desk. The usual way to check on it is full screen sharing: the entire remote desktop shrunk into a box. Beam.win takes a different approach. It pulls a single app window off that Mac and puts it on your desk Mac as a real, native window, with its own Dock icon and a place in ⌘Tab.

This beam win mac tutorial answers the question of how to use Beam.win, walking through the whole beginner arc: what Beam.win is, what you need, how to install it on two Macs, how to beam your first window, how to run it on a headless Mac mini driving AI agents, how much it costs, and the mistakes beginners make. If your workflow involves a coding agent on a remote Mac, this guide pairs well with CodexFuse's REST API tester: beam the browser the agent is driving while you probe the API behind it, side by side on one desktop.

What Is Beam.win, Exactly?

Beam.win is a Mac app by Noats that hands you an app window from another Mac, on your own desktop, at its own size, with its own Dock icon and a place in ⌘Tab. You install Beam on both Macs, sign in once, open the picker on the Mac in front of you, choose a window on the other Mac, and it opens on your desktop as a live window you can type into.

The distinction the maker draws is against screen sharing. Screen sharing hands you a picture of someone's desktop; Beam hands you the window itself. Drag a corner of the beamed window and the real window resizes over there; type, and shortcuts land on the other Mac.

It launched on Product Hunt on October 18 as "Run AI agents on one Mac and use its windows on another." The pitch is aimed squarely at the two-Mac desk: the Studio or Mac mini in the other room runs builds and agents, and you reach into it one window at a time instead of taking over a whole desktop.

One name note before anything else: this guide is about Beam.win, the Mac window app by Noats. It is not Microsoft's old "Beam" game-streaming service that was built into the Windows 10 Creators Update in 2017 — a different product with the same name.

How Is Beam.win Different From Screen Sharing and Universal Control?

Beam.win sits between screen sharing and Apple's Universal Control, and beginners confuse all three. The one-sentence version: screen sharing gives you the whole remote desktop, Universal Control shares your keyboard and mouse between Macs on the same desk, and Beam brings the other Mac's window to you.

Here is the decision table, based on the maker's own comparisons:

Agent work tends to be watched more than touched: a browser being driven, a test run scrolling, a terminal waiting for a yes. A tool built around one window at a time fits that rhythm better than one built around taking over a whole desktop.

What Do You Need Before You Install Beam.win?

You need two Macs, both running macOS Sonoma or later, with Beam installed on both. The maker supports Apple silicon and Intel Macs, and one plan covers every Mac you sit at — you pay for yourself, not your Macs.

Both Macs must be able to reach each other: the same Wi-Fi is enough, or the same Tailscale tailnet if the other Mac is in another city. And the Mac in the closet should ideally stay awake, with its normal macOS permissions, login, and FileVault authentication in place before you move it somewhere inconvenient.

The free tier needs an internet connection for its daily minutes. The paid plans — Monthly, Yearly, and Lifetime — keep working for up to 30 days offline on your own network, since your Macs talk to each other directly.

If your second Mac runs agents inside containers, CodexFuse's Docker beginner guide covers the environment those agents usually live in. If the agents are coding agents, the Claude Code beginner guide covers the one most likely driving the browser you will be beaming.

How Do You Install Beam.win on Two Macs?

Download Beam from beam.win — the free tier needs no card — and install it on both Macs. Sign in once, and your Macs find each other. Approve the new Mac when prompted so the connection is pinned to Macs you trust.

On the remote Mac, complete the macOS permission requests Beam shows during setup: Screen Recording and Accessibility. If that Mac is headless, you can plug in a screen for this step or grant the permissions once over SSH, then remove the screen.

Then verify before you relocate the hardware. The maker's own setup guide recommends this five-minute check, plus a reboot test:

1. Launch Beam on both Macs and connect them to the same local network, or join both to the same Tailscale tailnet.
2. Sign in on both Macs, approve the new one when prompted, then open the picker on the Mac in front of you and find the other Mac.
3. Choose an app window from the other Mac and beam it. Confirm you can see and use it from the Mac in front of you.
4. Look at small, still text, then scroll or play moving content. Confirm the text stays sharp and the motion stays smooth.
5. Restart the other Mac, complete its normal login and FileVault authentication, launch Beam there, and confirm the restarted machine appears in the picker again.

On a headless Mac, also run Beam's doctor command. It checks the permissions and the network on that Mac — the equivalent of testing the garage door opener before you drive away for a week. Do all of this while both computers are still within reach.

How Do You Beam a Window? The Five-Step Beginner Arc

Beaming is a loop: point, pick, open, use, decide. The whole thing takes seconds once both Macs are connected.

1. Point: on the Mac in front of you, open Beam's picker and find the other Mac. Its windows list even if it has no display attached.
2. Pick: choose the one window you want — a terminal, a browser an agent is driving, a build log. Hidden windows and password managers never even reach the picker, on either side.
3. Open: the window opens on your desktop at its own size, with its own Dock icon and a place in ⌘Tab. The app itself keeps running on the other machine.
4. Use: type, resize, scroll. Drag a corner here and the real window resizes over there. Drag a file onto it, or copy and paste, and the file lands on the other Mac. Toggle the speaker and that app's audio — just that app — plays on your Mac.
5. Decide: leave the window where it is so anyone at the other Mac still sees it work, or bring it over completely with "all the way over" — it leaves the other Mac's screen, and a small note there says where it went.

You never have to think about picture quality. Beam chooses for you: it keeps text sharp for code and terminals when a window is still, then keeps motion smooth for video, animation, or scrolling when the contents move. If you want control, you can override it in Beam's settings — but the default handles the mixed workday on its own.

How Does Beam.win Work on a Headless Mac mini Running Agents?

This is the setup Beam.win was built for, and it is where most beginners start: a Mac mini with no monitor, no keyboard, and a job — builds, agents, local models. This is the beam.win agents mac mini pattern the Product Hunt launch is aimed at.

A headless Mac has no display, and apps still need one to render. Beam gives the mini a virtual display on its behalf, at Retina density, so its windows list in the picker like any other Mac. Two caveats travel with that: full-screen apps and apps with custom window chrome may behave differently on the virtual display than on a real one, so test your actual apps before depending on them.

The classic beginner move: an AI coding agent is driving a browser on the mini. Instead of opening a full screen-sharing session, beam just that browser window and park it beside your editor on the desk Mac. You watch the agent work in a real window at full size while you keep editing — like watching the pot through the oven window instead of opening the door every two minutes.

A beam win headless mac setup usually pairs with a few things: the mini's agents run in containers (covered in the Docker beginner guide), the agent itself may be Claude Code (see the Claude Code beginner guide), the code it edits should be version-controlled (the Git beginner guide), and if the mini hosts local models, the Ollama beginner guide covers that lane.

Can You Beam More Than One Window — or a Whole Screen?

Yes. Beam lets you beam several windows at once: the build from the Studio and the logs from the mini, side by side on one desktop. And when one window is not enough, you can grab an entire screen or the whole Mac — the window-by-window model is the default, not the limit.

Your windows keep their identity through ordinary macOS moves. Minimizing a source window, hiding its app with ⌘H, or moving it to another Space keeps the same beamed view alive — the window still exists, it has just left the visible desktop. Pressing ⌘W is the action that ends it: the window is gone, so the shared view is gone too. That is why the maker calls a beamed window a live view of the window you chose, not a snapshot of pixels.

And if someone at the other Mac minimizes something you are watching, the beamed window stays available — you can restore the source window from the other Mac whenever you want to see it there again.

How Do You Reach a Mac in Another City?

Beam cannot cross networks on its own. Two Macs on different networks with no shared tailnet cannot reach each other — that is the maker's stated limit, and it is the most common reason beginners think Beam is broken.

The answer is Tailscale on both Macs. Same Wi-Fi is all Beam needs locally; with both machines on the same Tailscale tailnet, the other Mac can be in another city and the picker works the same way. Set the tailnet up before the remote Mac leaves your local network, and run the connection check while both Macs are still on the same Wi-Fi.

When you are apart, everything still goes straight between your Macs, encrypted. There is one more option for reaching out: a share link opens one window in any browser, on any device, and guests join free. It is view only unless you allow control, and it expires on a timer you set from an hour to a week. And if a device has no Beam app at all, windows open in a browser tab too.

What Does Beam.win Cost?

Beam.win's pricing, as listed on its homepage this month, has three personal tiers plus a team plan. Note the correction for anyone who saw the Product Hunt launch copy: there is no $18 figure in the current pricing. The subscription is $12 a month billed monthly, $84 a year (about $7 a month), or $199 once for Lifetime.

Three pricing facts beginners miss. First, sharing your Macs is always free, and so is joining a link — you pay for the Mac you sit at, and one plan covers every Mac you use. Second, the free tier gives you every feature, just 20 minutes a day of them. Third, teams are $12 a person a month or $84 a year, with every seat 20% off from 10 people — one invoice, a team page to add and remove people, and every Mac they use comes free.

If Beam does not work for you and the team cannot put it right, the maker offers a refund — the support address is [email protected].

Is Beam.win Private?

Beam.win is private by architecture, in the maker's words. Your windows, keys, clipboard, and sound go straight between your Macs, encrypted, and never through the company's servers. Your account knows your Macs and your plan — never what is on them.

Two details make that concrete. Hidden windows and password managers never even reach the window picker, on either side, so they cannot be beamed by accident. And the only other call home is a roughly daily update check carrying the app name and version.

The daily-minutes check on the free tier needs a connection, which is the one case where being offline matters. Otherwise, paid plans work for up to 30 days offline on your own network.

Seven Beginner Mistakes to Avoid

Almost every Beam.win beginner hits at least one of these. The fixes are all in the maker's own docs.

Sources

Every fact in this guide comes from one of these pages, all checked this month:

• Beam.win homepage — what it is, requirements (two Macs, macOS Sonoma or later, Apple silicon or Intel), current pricing ($12/month, $84/year, $199 Lifetime, Free 20 minutes a day), privacy, share links, offline behavior, support.
• Beam blog: "Frame rate or sharpness: Beam chooses for you" (updated October 31) — the setup flow, automatic picture quality, the five-step verification check, and the reboot test.
• Beam blog: "When a shared Mac window disappears" — window identity: minimizing, hiding, and Spaces keep the view alive; closing ends it.
• LockerGnome hands-on (October 23, 2026) — maker Noats, the doctor command, the Retina-density virtual display on headless Macs, Screen Recording and Accessibility permissions, the Tailscale requirement, the daily update check, and pricing.
• Product Hunt launch page (October 18) — "Run AI agents on one Mac and use its windows on another"; the launch description of Terminal, browser, and app windows as native windows.

Frequently Asked Questions

Is Beam.win free?

Yes, partly. The free tier is $0 forever with no card: host as many Macs as you like, join any share link, and get 20 minutes a day of everything — every feature. Unlimited use is $12 a month, $84 a year, or $199 once for Lifetime.

Does Beam.win work with Windows or Linux?

No. Beam.win is Mac-to-Mac only, and both Macs need macOS Sonoma or later, on Apple silicon or Intel. The one exception is viewing: a share link opens one window in any browser, on any device, and guests join free.

Can Beam.win reach a Mac in another city?

Yes, with Tailscale on both Macs. Beam cannot cross networks on its own — same Wi-Fi works locally, and the same Tailscale tailnet covers everything else. The traffic stays encrypted and direct between your Macs either way.

What can Beam.win see about what I am doing?

Nothing. Windows, keys, clipboard, and sound go straight between your Macs, encrypted, never through the company's servers. Your account knows your Macs and your plan — never what is on them — and hidden windows and password managers never even reach the picker.

Is this the same Beam that Microsoft put in Windows 10?

No. Microsoft's "Beam" was a game-streaming service built into the Windows 10 Creators Update in 2017. Beam.win is a different, unrelated product: a Mac window-beaming app by Noats, launched in October 2026.