guide

Keep your session answering, laptop closed or not.

screenless answers with the Claude Code session where you typed /screenless, on that machine. When the machine sleeps, nobody gets a live answer: calls and messages wait until it is back. Two ways to keep it answering.

The sturdy way: an always-on machine

A small Linux server for a few euros a month, or a Mac mini at home. This is how screenless's own maker runs his session, on a server in Finland.

Install Node.js 20 or newer, git and tmux, then Claude Code:
```
npm install -g @anthropic-ai/claude-code
```
Clone your repo, and connect the MCP servers you want the session to have (Linear, Slack, your tracker), as you did on your laptop.

Start a session that keeps running when you disconnect:

tmux new -s claude
cd your-repo
claude          # log in when it asks; it prints a link

Paste the install prompt. It sets screenless up on this machine and asks you for a fresh code for your number; your team is already invited.
```
Install https://screenless.sh/llms.txt into this repo and invite my team.
```
Type /screenless. Then detach with Ctrl-b followed by d: the session keeps answering. tmux attach -t claude takes you back to it.

Treat that machine like your laptop. It now holds your Claude login, your repo access and your MCP tokens: SSH keys only, no other users, and a firewall that only lets SSH in. It has no browser of yours, so work that needs your logged-in Chrome waits for your laptop.

The quick way: a laptop that does not sleep

Fine for a working day; it answers as long as the laptop stays awake and online.

On a Mac, in System Settings → Battery → Options, turn on Prevent automatic sleeping on power adapter when the display is off. Or keep a terminal tab running caffeinate -is, which holds it awake on power for as long as it runs.
Closing the lid still puts a MacBook to sleep, unless it is plugged in with an external display and keyboard (clamshell mode).
On a Linux laptop, set the lid to do nothing: HandleLidSwitch=ignore in /etc/systemd/logind.conf.

Answer from one place

Run /screenless in one session per person. With two, say your laptop and the server, a call goes to whichever checked in last, and a WhatsApp conversation's memory stays on the machine that answered it. Once the server answers, stop the one on your laptop.