Your agents fleet,
on a server.

One command installs Claudete on any Linux box. Agents run on server hardware — you drive them from any browser.

install.sh

$curl -fsSL https://claudete.co/install.sh | sh

Self-contained — zero dependencies Checksum-verified x64 + arm64 Works with your Claude subscription

How it works

From bare VPS to full cockpit

No build steps, no config files — three commands and you're in.

Install

Detects your arch, verifies the checksum, and puts claudete on your PATH. Ships its own Node runtime — curl is all a bare VPS needs.

Authenticate

Open your browser

The server prints a private token URL. Open it anywhere for the full cockpit — tiles, tabs, Kanban, usage meters.

Capabilities

Everything the server does out of the box

One package, nothing to maintain. Installs clean, updates itself, stays locked down.

Self-contained

Node runtime and terminal engine in one 45 MB package. No apt installs, no version conflicts — glibc and curl are the whole dependency list.

One command, fully set up

Arch detection, checksum verification, PATH setup for bash, zsh and fish — plus a guided claude CLI install if it's missing. Always safe to re-run.

Runs as a service

… | sh -s -- --service creates and starts a systemd unit with lingering enabled. Survives reboots and logouts; bind host and port are plain env vars.

Self-updating

claudete update fetches the latest release, verifies its checksum, and swaps a symlink. Sessions, scrollback and settings stay put — no background daemon.

Secure by default

Binds loopback only, and every request needs the access token — it refuses to start exposed without one. Front with Caddy or nginx for TLS.

Any browser is the cockpit

The same process serves the web UI. Phone, laptop, borrowed machine — paste the token URL and your fleet is there.

Reference

Command reference

claudete start the server; prints your access URL

claudete --port N listen port (default 4000)

claudete --host H bind host (default 127.0.0.1, loopback-only)

claudete --print-token print the access token

claudete update checksum-verified self-update, state untouched

claudete --version / --help print the version, or the full flag list

Prefer env vars? CLAUDETE_PORT, CLAUDETE_HOST, CLAUDETE_DATA_DIR, CLAUDETE_DEFAULT_CWD, CLAUDETE_MAX_SESSIONS and more — every flag has one.

Remote access

HTTPS in two lines

Claudete spawns real shells — treat it like SSH and never expose the raw port. Tunnel over SSH or front it with TLS; the token handles the rest.

Caddyfile

claudete.example.com { reverse_proxy 127.0.0.1:4000 }

SSH tunnel

$ssh -L 4000:127.0.0.1:4000 you@server # then open http://127.0.0.1:4000/#token=…

Linux x64 or arm64 · glibc ≥ 2.28 (Debian 10+, Ubuntu 20.04+, RHEL 8+)
curl — everything else is bundled
claude CLI installed & authenticated on the box (the installer offers it)
Alpine/musl not supported

FAQ

Questions, answered

Does my Claude subscription work on a server?

Yes. Log in to the claude CLI on the box once; every instance Claudete spawns uses that login, just like your terminal.

Is it safe to put on the internet?

Keep the loopback default and front it with TLS, or just SSH-tunnel. It refuses to start on a public interface without a token — treat that token like an SSH key.

How do updates work?

You run claudete update when you choose. Checksums are verified before anything swaps; sessions and settings live in ~/.claudete, untouched.

Do I still need the Mac app?

No — any browser gets the same full UI. The Mac app is still the nicest way to run a local fleet; the CLI puts it on server hardware.

Does Pro work here?

Yes — activate your license in the web UI's settings, same as the desktop app. One seat covers the server.

Get started

Put your fleet on a server