You’ve had one of these weeks.

With Nightdesk

1. Nightdesk offers the terminal view. One tap zooms the picture to the terminal.
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.

With Nightdesk

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.

With Nightdesk

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.

With Nightdesk

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.

With Nightdesk

1. He takes a photo and shares it 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.

With Nightdesk

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.

With Nightdesk

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.

With Nightdesk

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.

With Nightdesk

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.

With Nightdesk

1. In the workstation’s terminal, through Nightdesk, she runs nightdesk-host send app-release.apk.
2. It lands in Download › Nightdesk on her phone, and she installs it from there.

With Nightdesk

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 their clipboards and sound shared.

With Nightdesk

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, with no ports opened on her parents’ router. 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.

With Nightdesk

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.

With Nightdesk

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.

With Nightdesk

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.

With Nightdesk

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.

With Nightdesk

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.

With Nightdesk

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, checks the dashboard, and is back before the cake.

With Nightdesk

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.

With Nightdesk

1. When the connection slows, the picture gets smaller instead of stuttering, and sharpens again as soon as it can.
2. A still screen sends almost nothing, so reading a log barely touches his data. Away from home the picture never takes more than 12 Mbps.

With Nightdesk

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.

With Nightdesk

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.

With Nightdesk

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.

With Nightdesk

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.

With Nightdesk

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.

With Nightdesk

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.

With Nightdesk

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 her eyes stay on the canvas.

With Nightdesk

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.

With Nightdesk

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.

With Nightdesk

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.