Fleet Settings

Supervisors known to the manager. Metadata is durable: an offline supervisor keeps its alias and description and reappears fully named.

No supervisors yet. Add one below, or launch a supervisor daemon that announces itself to this console — see the instructions at the bottom of this page.

Add a supervisor

The supervisor is probed over url:// before being admitted to the registry.

Launch your own supervisor daemon

A supervisor daemon runs on your own machine and serves AI-CLI sessions over url://. Started with --register-with pointing at this console, it announces itself every ~60 seconds and appears in the list above automatically — no manual add needed. You only need coursier and a JDK (17+); the daemon downloads from kotlin.directory.

Real AI CLI sessions (recommended)

The launcher detects the AI CLIs installed on the host (Antigravity agy, Claude Code, Codex, Gemini CLI, OpenCode) and advertises their model catalog. At least one AI CLI must be installed and authenticated.

coursier launch aicli.hostsupervisor:launcher-fatjar:0.0.1 \
  -r https://kotlin.directory \
  -- --register-with https://aiclisupervisor.wasmserver.com/

Fake/demo sessions (no AI CLI needed)

The fake-model service-server build serves an echoing fake model, so the whole console workflow can be exercised without any AI CLI installed.

coursier launch aicli.hostsupervisor:service-server-fakepty-fatjar:0.0.28 \
  -r https://kotlin.directory \
  -- --register-with https://aiclisupervisor.wasmserver.com/

Both announce over HTTPS (an HTTPS request can wake this lazily-started console, which relays the announcement to the durable manager). Daemons reachable over the P2P fabric can announce directly to the manager instead with --register-with url://aiclisupervisormanager/. The daemon itself registers as url://vpn.<hostname>.aiclisupervisor/ on the fabric; that is the address this registry records and the one you would type into the add-by-URL form above.