# Fardesk – fast iPhone app to manage your Claude sessions

> Source: <https://fardesk.franzai.com/>
> Published: 2026-11-18 20:55:50+00:00

**Key takeaway:** Fardesk's fardeskd daemon discovers existing Claude Code sessions through Claude Code's hooks and local transcript files with no per-session setup, and hooks fail open so Claude Code keeps working if the daemon is down.

iPhone and Mac app · Open source · Apache-2.0

# Fardesk

Every Claude Code session on all your computers, on your phone.

See what every session on every machine is doing, reply to it, answer its questions and start new ones. A small daemon runs next to Claude Code on each computer and talks to the app over your own Tailscale network.

Your machines, your tailnet, your Claude login. There is no Fardesk server and no account.

## What you can do

The session that needs you is always on the computer you are not sitting at. Fardesk brings them all into one list.

- ### See every sessionOne list of every Claude Code session on every machine: working, waiting, idle or ended. Open one to read what it did: your prompts, its replies, edited files, commands and results, without thinking blocks or raw JSON. It also finds sessions you started yourself in a terminal.
- ### Reply and answer questionsType or dictate a reply, attach a screenshot, or pick an answer when a session asks you a question. A push notification tells you when a session finishes or needs you.
- ### Start sessions anywhereStart a new Claude Code session on any machine in any folder, with a first prompt, from your phone. No terminal, no SSH, no tabs. Stop, resume or take over a session from the same screen.
- ### Let a Coordinator run themThe Coordinator is an optional session on your hub that can list, read, message and start the others. Tell it in plain words what you want across all machines. It is off until you turn it on.

## Screenshots

The app is plain SwiftUI for iPhone, iPad and Mac, in light and dark mode. These screens show demo data from three machines: Studio, Laptop and Build server.

## How it works

Each computer runs a small daemon, `fardeskd`, next to Claude Code. The app talks to them over Tailscale. One always-on machine can act as the hub.

### Sessions you already run

Claude Code's hooks and its local transcript files tell the daemon about every session on the machine, including the ones you started in a terminal. No per-session setup. Hooks fail open: if the daemon is down, Claude Code works as if Fardesk were not there.

### Sessions Fardesk starts

New sessions run through the official Claude Agent SDK, under your own Claude Code login on that machine. "Take over" resumes a terminal session under the daemon with its full history, so you can continue it from your phone.

### Hub or no hub

With a hub, the phone pairs once and sees every machine behind it, and the Coordinator runs there. Without a hub, the app pairs with each machine directly. Either way there is no server of ours in the path.

## Security

A token for a Fardesk daemon can start Claude Code in any folder on that machine. That makes it a remote shell, by design. The defaults are built around that fact.

- Tailnet only
- The daemon listens only on its Tailscale address. It refuses any other address unless you configure TLS and allow it explicitly. Use a tailnet that only you use.
- One-time pairing codes
- The QR code you scan holds a short-lived, single-use code, not a permanent token. Each phone gets its own token, stored in the Keychain, and you can revoke it at any time.
- Permission prompts stay on
- Sessions started from the phone keep Claude Code's normal permission prompts. Skipping them is a setting you turn on yourself, per machine.
- Coordinator is opt-in
- The Coordinator reads other sessions' output, which makes it a prompt-injection target. It is off by default; when on, it has limited tools unless you grant more.
- Generic push
- Push notifications are optional. By default they say only that a session needs you and on which machine. Session text goes through Apple only if you choose that.
- Nothing phones home
- The daemon talks to your own machines and, if you set up push, to Apple. Diagnostics stay in a local file on your machine.
- Protect the hub
- The hub can reach every machine. Make it your best protected computer, and limit the daemon port to your own devices with a Tailscale ACL.

## Install with your agent

Fardesk is agent-first. Paste this prompt into Claude Code on one of your computers. The agent clones the repository, reads the install guide and sets everything up.

```
Set up Fardesk for me: https://github.com/franzenzenhofer/fardesk-open-source
This is an external open-source repository, so work carefully and precisely. Before you install anything:
clone it, read AGENT-INSTALL.md and every script it runs, do a code review and a security review of what will
run on my computers, and check that it fits my setup. Tell me what you found and wait for my OK.
Then follow AGENT-INSTALL.md and all security best practices. Ask me which of my computers it should cover
and which one is always on.
```

[Source code on GitHub](https://github.com/franzenzenhofer/fardesk-open-source). There is nothing to fill in. The agent first reviews the code and its security for your setup and reports back; then it asks which of your computers to cover and which one is always on, shows you a plan, and only installs after your OK. Permission prompts and the Coordinator stay off unless you ask for them.

### What the agent does

1. Asks which of your computers it should cover and which one is always on, then checks each: Node, Claude Code, Tailscale, Xcode on your Mac.
2. Shows you a plan and writes one settings file, `fardesk.env` , from your answers.
3. Installs `fardeskd` on each machine and links them to the hub. Permission prompts and the Coordinator stay off unless you ask.
4. Builds the app for your iPhone and Mac with Xcode.
5. Prints a pairing QR code and checks that everything answers.

### What you do

1. Log in to Tailscale on each machine and on your phone.
2. Sign in to Xcode with your Apple account and connect your iPhone.
3. Confirm the one change to `~/.claude/settings.json` (the hooks).
4. Scan the pairing code with the app.

## Requirements

Everything runs on hardware and accounts you already have.

- iPhone, iPad or Mac
- iOS 26 or macOS 26. You build the app yourself; there is no App Store version.
- A Mac with Xcode
- To build the app. A free Apple account works, but the app must be reinstalled every 7 days and has no push. Push and TestFlight need a paid developer account.
- Tailscale
- On every computer and on the phone, all in one tailnet that only you use.
- Claude Code
- Installed and logged in on each computer. Your own plan or API key pays for your sessions, as it does today.
- Node 22 or later
- For the daemon, on macOS or Linux. tmux or Ghostty are optional, for typing into terminal sessions.
- An always-on machine
- Optional. A desktop Mac or a small Linux box makes a good hub.

## FAQ

## Why not just SSH, tmux or mosh?

If you have one machine and live in tmux, SSH from a phone terminal is enough. Fardesk is a list of every Claude Code session on every machine with its state, a push when one needs you, a readable view of what it did, quick answers to its questions, attachments and dictation. It also finds the sessions you started in a plain terminal, with no per-session setup.

## Is this a remote shell on my machines?

Yes. Anyone with a valid daemon token can start Claude Code in any folder on that machine. That is why the daemon listens only on your tailnet, pairing uses one-time codes, every phone has its own revocable token, permission prompts stay on and the Coordinator is opt-in. See [Security](#security).

## Plain HTTP?

Inside your tailnet the traffic runs over WireGuard. You can add TLS with `tailscale cert`, and the daemon will not listen outside the tailnet without TLS.

## What does it cost?

Fardesk costs nothing and has no service behind it. Your Claude plan or API account pays for your sessions, as it does today. The Coordinator is one more Claude Code session while you use it. Push and TestFlight need a paid Apple developer account.

## Is this allowed under Anthropic's terms?

Our reading of Anthropic's [Legal and compliance page](https://code.claude.com/docs/en/legal-and-compliance#authentication-and-credential-use) (not legal advice): you run the unmodified Claude Code binary with your own login, which the page does not restrict, and Fardesk never sees or forwards Claude credentials. For the sessions Fardesk starts through the Agent SDK, the page says to use API key authentication, so we recommend your own API key there. Fardesk is not affiliated with or endorsed by Anthropic.

## Does it work without a hub?

Yes. Without a hub, the app pairs with each machine directly. A hub gives you one pairing and one address for all machines, and it is where the Coordinator runs.

## Android? Windows?

No. The app is native SwiftUI for iPhone, iPad and Mac, and the daemon runs on macOS and Linux. The daemon's HTTP API is documented, so another client is possible; nobody has written one yet.

## Will it break when Claude Code updates?

It can. Fardesk reads Claude Code's local transcript and session files, which are not a documented API. The parser is tested against anonymised transcripts from the versions we ran, and it gets fixed when it breaks.

## Was it built by agents?

Yes. The author wrote the spec and made the decisions; Claude Code agents wrote nearly all of the code. The repository carries the gates: typecheck, lint, a duplication check, daemon tests against anonymised transcripts and Swift tests with a coverage floor.

## Where is the source code?

[Source code on GitHub](https://github.com/franzenzenhofer/fardesk-open-source). Fardesk is open source under the Apache-2.0 licence.

## Is it safe to let an agent install code from a stranger's repository?

Only if the agent reviews it first, and the install prompt asks for exactly that. Before it installs anything, Claude Code reads AGENT-INSTALL.md and every script it will run, does a code review and a security review (network exposure, tokens, hooks, the Coordinator, dependencies, anything that downloads code), checks that it fits your computers, and reports back. Nothing is installed until you say OK.
