screenless

Your team's questions, answered without you. Every quick question used to be a call or a huddle that pulled a developer out of their work. screenless gives your team a number for your Claude Code session instead: they call it, or message it on WhatsApp, and it answers from your code, tickets and docs, and does what you allow, right away, on your own machine. You get fewer interruptions; they stop waiting on you. And you can use it yourself, from a walk or the car.

Hear a demo call at screenless.sh.

How it works

1. Install — paste Install https://screenless.sh/llms.txt into this repo and invite my team. into Claude Code. It installs the CLI, verifies your number and invites your colleagues; or by hand, curl -fsSL https://screenless.sh/install | bash.

2. Arm a session — type /screenless in Claude Code. That session now answers the line. To keep it answering with your laptop closed, run it on a machine that stays on: screenless.sh/always-on.

3. Call or message — ring the number, or call it on WhatsApp. A voice talks with you; each thing you ask runs in a fork of your session on your machine, and the answer is spoken back during the call. Read, edit, test, commit, push, deploy, post to Slack: whatever the session can do at the keyboard. It tells you how longer work is going while you wait.

   Or send it a WhatsApp message, with screenshots and voice notes. Each conversation gets one fork of your session, carried on with every message (--resume), so a follow-up keeps its context; after 30 minutes of quiet the next message starts a fresh fork from the session as it is then. The answer comes back in the chat.

Only you get through. The line never answers a phone call on its caller id, which is easy to spoof: it hangs up and rings your verified number straight back, so only your phone can pick up. A WhatsApp call or message is tied to your account and is answered at once; the Worker only takes a WhatsApp message that Telnyx signed.

The voice holds no keys. It has no tools and no credentials; it talks, and your session acts. Your code, your MCPs, your logged-in browser and your Claude subscription stay on your machine. What passes through the service is the call itself: its audio, the transcript, and the short answers your session sends back to be spoken.

Your team

Everyone on a team shares the one number and reaches their own session. Around that:

• Teammates can listen in — share your session's brief (screenless watch --brief-for team) and a teammate who rings hears where it stands. What they ask is noted for after the call; it never runs on your machine while they are on the line.
• Say who may do what — a .agents/permissions.md in the repo defines levels, each with a gate — listen (heard, noted for later), read (answers during the call) or full (may have your session send, merge or ship) — and your own rules in plain words. No names in it, so it is fine in an open-source repo. Who has which level is set on the team page, or with screenless team level <email> <level>. Other agent tools, such as a Slack bot, can ask the line for a person's level. See the /screenless skill for the format.
• Nobody watching? It waits — call while no session is armed and the request is transcribed and queued for the next teammate's terminal running screenless watch, for up to a week.
• Ring out — screenless call "…" --to [email protected], or --all, phones one teammate or the whole team and returns each conversation as a transcript. It only ever reaches verified numbers on your own team.

Skills

A skill is a prompt that points the line at a job. screenless itself is the skill that arms a session; two more ship as worked examples of agents calling you, and you build the rest.

• call-when-afk — tell your agent you're stepping out and it stops pausing on questions. It phones you each one and continues the moment you answer.
• morning-pr-review (optional) — the nightly loop. At 03:00 it reads your repo's pull requests and tickets, calls each person about the few decisions that are theirs, and hands the transcript to your agent, which does the work. On Saturdays it also mails a weekly team paper: who shipped what, and the week ahead.

Install the skills into any coding agent — Claude Code, Cursor, Codex, and the rest — with one command via skills.sh:

npx skills add janwilmake/screenless

Install

curl -fsSL https://screenless.sh/install | bash

One command: the CLI lands in ~/.screenless, gets a launcher on your PATH, installs the skills into every coding agent it finds, and goes into screenless setup — phone verification by SMS, no card. Then, in Claude Code, /screenless arms the session. Every team starts with two weeks free (no card: unlimited WhatsApp chats, 2 hours of calls and meetings); then the team plan is $200/month, the founding price ($500, locked for 12 months): unlimited WhatsApp chats and 40 hours of calls and meetings, then 15¢/minute. Node 20+ required, never installed for you.

Manage your team, roles and billing at screenless.sh/team.

Status

Calling your session works on real phones today, in production at screenless.sh: phone calls with the ring-back, WhatsApp calls, live answers from a fork of the session, progress updates, barge-in, wideband audio. Ringing in to the queue, calling teammates, teams, invites and pay-as-you-go billing work too. WhatsApp messages to the session work too: answered in a fork that keeps the conversation, with screenshots and voice notes.

What is still early is the intelligence in the skills — the morning briefing's hard part, reading a queue of pull requests and picking out the few that genuinely need a person, is being built in the open. The nightly loop and weekly paper render and deliver but have not run unattended against a real repo for a full week.

Self-hosting

The hosted service at screenless.sh is the default and needs none of this. To run your own Worker and CLI — Telnyx, Cloudflare, Stripe, configuration, the full command reference, and the notes found the hard way — see SELFHOST.md.

License

MIT — see LICENSE.