You’ve had one of these weeks.

How

1. Nightdesk offers the terminal view. One tap fills the phone with just the terminal, in large, sharp text.
2. One finger scrolls back through the output; a tap puts the cursor where he wants it.
3. He writes the next instruction in Write, and it arrives in one piece.

All three screens read and answered before the bill comes.

How

1. She opens Write and types the prompt with her phone’s own keyboard, or dictates it, autocorrect and all.
2. She taps Send. It lands in the terminal on her desktop in one piece, and the agent starts.

By the time she sits down at work, the agent is well into it.

How

1. He opens Write in Nightdesk and says it with Keyey, the voice keyboard he also built. It types on the phone itself and gets the names right.
2. He taps Send. The whole prompt lands in Claude Code on the Mac in one piece, and it starts.
3. When it asks before running the tests, 1 is a key above the dock.

Talking is faster than typing, and Claude Code gets the whole thought.

How

1. He taps Stop. Nightdesk sends Esc, and Claude Code halts.
2. Mode switches it to plan mode, and Write tells it what to do instead.

Stopped with one tap, from the corridor.

How

1. Home in Nightdesk is a deck of her computers. She swipes to one and taps Link.
2. The agent keys follow the tool in front: Claude Code’s on the Mac, Codex’s on Linux.
3. Switch computer jumps to the other one without going back to Home.

Both agents answered from one app, with no SSH in between.

How

1. He photographs the board and shares the picture to Nightdesk’s Send to computer. It lands in Downloads › Nightdesk on the Mac.
2. Through Nightdesk he asks Claude Code to read that picture and draft a plan from it.

The plan is waiting when he gets home, drawn from the real sketch.

How

1. Nightdesk finds the commands the tool would offer: the project’s .claude/commands, her own in ~/.claude/commands, Codex prompts in ~/.codex/prompts.
2. They’re in the agent keys’ list next to the built-in ones. A tap types one; a long press types it and sends it.

Each command is one tap, spelled right every time.

How

1. In the waiting room he links to his Mac and opens Windows. The Simulator is there, with a picture of it; one tap brings it to the front.
2. His phone is the trackpad. He taps through the sign-in screen in the Simulator, and it holds.
3. Back in the terminal, he taps 1 on the agent keys, and Claude commits.

Seen, tried and committed before his name is called.

How

1. On her way out she adds a line to the prompt: “when the suite is done, notify my phone with the result.”
2. The suite finishes while her train is in a tunnel. Her phone isn’t linked, so Nightdesk on her desktop keeps the notification for it.
3. At the next stop she opens Nightdesk. As it links, the phone buzzes: “All 412 tests pass. Ready for review.”

No checking in. The news finds her.

How

1. Nightdesk is linked on his phone. In Write he asks Codex: “build a debug APK and send it to my phone.”
2. Codex runs the build, then hands the file to Nightdesk. It lands in Download › Nightdesk on his phone.
3. He installs it under the table, opens settings, and the crash is gone.

The fix is tried on a real phone without leaving the meeting.

How

1. She links to the tower over mobile data. Nightdesk goes through the relay by itself.
2. TensorBoard is open on its desktop, and she pinches in on the curve. A terminal with nvidia-smi shows the GPU; live stats show the processor, memory and temperatures.

Loss still falling, GPU at 98%. She finishes her workout.

How

1. Nightdesk for Linux gives the server a GNOME desktop of its own, with nothing plugged in.
2. His phone is the monitor, the keyboard and the trackpad. He finishes the setup from the couch.

No spare monitor, no cables, no closet floor.

How

1. Home for the holidays, she put Ubuntu on the PC and pasted one command: Nightdesk for Linux. It starts by itself whenever the PC does.
2. From the library she links through the encrypted relay. Live stats show the GPU busy and how hot it runs.
3. When a run has died, she starts it again in the terminal, with Ctrl and the arrows on the key bar.

Her thesis runs on a GPU she already owns.

How

1. Nightdesk for Mac has Connect to a Computer… in its menu. He pairs the Linux box once, with its code.
2. Its desktop opens in a window on the Mac, with the Mac’s keyboard and trackpad and one clipboard between them.

His home workstation, full size, on the office monitor.

How

1. On the MacBook she chooses Connect to a Computer… and clicks the Mac Studio. It links through the relay, over the client’s Wi-Fi.
2. The Studio’s desktop fills the window, and its sound plays on the MacBook. She trims the cut and starts the export.
3. She drops the client’s new logo on the window to send it across, and copies the share link on the Studio into her email on the MacBook.

The change is in before she leaves, and the export runs at home at full speed.

How

1. He runs nightdesk-host view. A Chrome window lists the Mac mini under Nearby, and he types the code from Nightdesk’s window on the Mac.
2. The Mac’s desktop opens in that window. Ctrl works as ⌘, so his hands don’t relearn anything.
3. He archives the build in Xcode, closes the window and is back in his editor.

The Mac stays on the shelf, and Tobias stays on Linux.

How

1. His phone is the trackpad: slide to move, tap to click, two fingers to scroll.
2. Controls has volume, play and pause, and Spotlight, one tap each. The key bar has ⌘ and the arrows.

Nothing to charge, and nothing to go looking for.

How

1. Once, he saves the Mac’s password in Nightdesk. It stays on his phone, encrypted with a key only his fingerprint or PIN opens.
2. When the lock screen is up, the phone says so. He touches the sensor, and Nightdesk types the password in.

One touch instead of a long password, and no typos.

How

1. Display in the dock draws his displays the way they stand on the desk. He taps one to show it.
2. Going to a window from Windows takes him to whichever display it’s on.

The right display, one tap away.

How

1. Three fingers up opens Mission Control, as on a trackpad.
2. Or Windows lists every open window with a picture of it, by app or by desktop, with search. She taps one, and the Mac slides to its Space and brings it forward.

Any window, wherever it hides, in two taps.

How

1. She links to the Mac and, in its menu bar, picks Nightdesk › Send to Phone…, then the file.
2. It lands in Download › Nightdesk on her phone, checked. If the link drops halfway, it picks up where it stopped.

The contract is on her phone before the meeting starts.

How

1. He steps under the awning and links to the desktop from his phone.
2. The key bar puts Ctrl, Esc, Tab and the arrows above his keyboard. He runs the script and checks the dashboard.

Back inside before the cake.

How

1. She links to the Mac and picks Phone screen: the Mac gets a screen in the tablet’s exact shape, with no black bars.
2. The keyboard works the way it does on the Mac: ⌘Tab, ⌘Space and the rest go straight through. A mouse works too.

Her whole Mac, edge to edge, in a weekend bag.

How

1. When the connection slows, the picture gets smaller instead of stuttering, and sharpens again as soon as it can.
2. A screen where nothing moves sends no video, so reading a log uses next to no data. Away from home the picture never takes more than 12 Mbps.

A readable log, and a data plan that survives the crossing.

How

1. She links her phone and picks Extra screen, so macOS sees one more display.
2. In Keynote she puts the presenter display on it: notes, timer and the next slide in her hand. The arrows on the key bar move the slides.

Notes in her hand, and her eyes on the room.

How

1. Screen in the dock › Phone screen: the Mac gets a screen exactly the shape of his phone.
2. The diff fills the phone from top to bottom, sharp, and scrolling glides under his finger.

Every pixel on the phone is the diff.

How

1. He links his phone to the MacBook and walks the room. The phone is the trackpad: he scrolls the code on the projector to the line in question.
2. Write types a whole snippet into the editor in one piece, and the key bar has ⌘, Tab and the arrows for the rest.

He answers each question from where it was asked.

How

1. From the window’s toolbar she opens the Studio’s Control Deck too, makes it a compact panel and keeps it on top. It floats over the full-screen window, clear of the tracks.
2. Logic is in front on the Studio, so the panel shows Logic’s page: play, record, cycle, the metronome and the mixer, each one Logic’s own shortcut. A click never takes her out of the window she’s working in.
3. The next page is a mixer: Logic sees a controller named Nightdesk, and she rides the strings with the panel’s faders.

Every key she needs is one click away, and the session never leaves the screen.

How

1. His old phone, on a stand by the keyboard, becomes a Control Deck: as many keys as he likes, on pages he swipes.
2. In VS Code the keys are VS Code’s, with its icons. Switch to the terminal and they turn into Claude Code’s.
3. Each press gives a small, firm click, so it feels like a button and not a screen.

The keypad stays in the cart.

How

1. The Air opens the Studio’s Control Deck in Nightdesk and fills its screen with keys. Only keys: the Studio’s screen stays on the Studio.
2. The Agents page has a key for each session, named by its repo: amber while it works, pulsing pink when it needs him, green when it’s done.
3. When billing turns pink, he clicks Yes on the Air and billing carries on. ⌘1 puts his Dev page back.

He sees which agent needs him without leaving the window he’s in.

How

1. His deck has a page of sixteen pads. GarageBand sees a controller named Nightdesk and plays them on its drum kit.
2. He taps the beat in from the couch. Each pad clicks under his finger, so he keeps time without looking.

The beat is in GarageBand before he can forget it.

How

1. With VS Code in front, her deck shows Command Palette, Toggle Terminal and her test runner, with VS Code’s icons.
2. When the DJ app comes to the front, the page changes by itself, and the app maps the deck’s crossfader and two EQ knobs like any controller, this one named Nightdesk.

One phone for both jobs, and one less gadget in the bag.

How

1. Her old phone, on a stand by the trackpad, is a Control Deck. She makes a page of keys, each one a Figma shortcut she named herself, and pins it so it stays while she switches apps.
2. A fader on the same page is the Mac’s volume, for the call at noon. Every press clicks under her finger, so she never looks down.

Her eyes stay on the canvas.

How

1. Bitwig sees a controller named Nightdesk, which Nightdesk for Linux makes as an ALSA MIDI port.
2. He maps the XY pad to cutoff and resonance and plays the sweep with one finger, while the knobs click through their detents.

A filter sweep under one finger, no mouse involved.

How

1. Her old phone stands by the monitor as a Control Deck. When Steam comes to the front, its Games page comes up by itself, and it stays while the game she started is playing.
2. Push to talk stays down for as long as her thumb rests on it, so she talks between rounds without the keyboard. The overlay, a screenshot and the volume are a tap away.
3. Quit game waits for a one-second hold, so a stray tap never ends the match.

The keyboard stays out of reach, and she never needs it.

How

1. She builds her deck once. On the Linux machine it adapts by itself: ⌘ becomes Ctrl, Mission Control becomes Activities.
2. Or she gives each computer its own layout, and the right one is there when she links.

One layout to learn, on every computer she works on.