Mobile, desktop and web interface for Claude Code

Chat

The CLI's own slash commands in the composer, a quick chat in a side panel for a throwaway question, and a queue that holds what you send while Claude is still working.

Questions come as forms

When Claude needs something it asks in the chat: choices, text fields, toggles, and longer questions as pages you move through. Its replies carry galleries, audio, PDFs, live previews and blocks it draws.

Attachments and dictation

Send any file or photo from your device and it lands on the PC before the prompt runs; images reach Claude as real vision input. The microphone writes what you say into the composer.

Rewind

Take a conversation back to an earlier point, preview exactly what would change on disk, and choose whether the conversation alone rolls back or the code with it.

Tabs

Several chats open at once, each with its own session, project and environment. A tab bar on desktop, a switcher on mobile, and they come back where you left them.

Files

A file manager over the shared folder: upload with per-file progress, create, rename, sort, multi-select, and preview in place, from images with zoom to Markdown, source code and HTML.

Notes

A Markdown editor with a live preview that doubles as a scratchpad. Save, export or share the note as a file, and what you type stays between sessions.

Terminal

Shells on the machine hosting the backend, each in its own tab. They run on the server, so closing the app does not take them down, and a key the server prints is the only gate.

SSH hosts

A lightweight SSH client for the targets you save: address, port and the credentials you log in with, then an embedded terminal with a keepalive.

Browser

A browser in the same panel, driven by Claude and watched by you, running in a Chrome already installed on that machine so a page that needs your session stays logged in.

Monitor

CPU, GPU, memory and storage as live graphs, with VRAM and temperature on NVIDIA cards, the server's own logs streaming in, and a remote restart of the backend.

Network

Whether the machine really has internet, live upload and download, every interface, the Wi-Fi networks in range and a speed test. A change that would strand it is refused outright.

Discord

The desktop app can show on your profile what you are working on: the action, the elapsed time, the model, the environment. Each piece is a switch of its own and the content never goes out.

The CLI

See the active version, switch where it comes from, update it and read the official changelog without leaving the app.

Plugins, MCP and skills

Browse any marketplace and install plugins, then enable, update or uninstall them. Add and remove MCP servers, read the skills they provide, and view or delete Claude's memories, globally or per project.

Accounts

Several Claude logins on one backend, signed in from the app itself. They share history, plugins and skills, so switching only changes who pays for the turn.

Model providers

An account can point the CLI at an address of your own instead: a model served by Ollama on your machine, or a gateway like OmniRoute standing in front of hundreds. The models it serves become the list you pick from, effort levels and context window included.

Plan usage

Your subscription tier and a bar per limit window, the current session, all models and the per-model weekly caps, each with its reset time.

Your own prompt

Standing instructions edited from the app that ride along every conversation, on top of the conventions the backend already ships with.

Built-in helpers

The backend wires a few of its own into the agent. Ask how the README you left running in another project is going and it summarises that session without you having to open it.

Local

The backend listens on port 8723 with no auth. From the same machine that is localhost; from another device it is the PC's tailnet address, with Tailscale signed in on both.

Tailscale Funnel

One flag publishes the backend over HTTPS, generates the token, prints the URL and a scannable QR to pair the phone with, and closes the funnel again on exit.

Your own proxy

Behind Caddy or nginx on a VPS: the same URL, token and QR, but the HTTPS comes from the proxy you already run. One machine can serve several backends, each with its own hostname and token.

Started for you

The desktop app can launch the backend itself: point it at the folder, pick how to run Python and which mode, and it comes up on startup with its status in view.

Web

Nothing to install, runs in the browser