v{{ version }}
{{ projects_root }}
Lost connection to the server — data may be stale. Retrying…
Before you start a session
Active sessions
what Claude is running for you right nowNo sessions match this filter.
{% if claustrum_enabled %}
{{ hosted_row() }}
{% endif %}
![QR code for the session deep link]()
{# bg-dark/text-white: terminal-style log view, intentionally dark in both
themes (a console reads as dark) — not a theming straggler to "fix". #}
{% if pty_screen_enabled %}
{# Read-only live terminal (#534). The xterm.js Terminal is created on open and
disposed on hide; it lives in a module-level registry, NOT Alpine state, so its
internals are never wrapped in a reactive Proxy (cf. #310/#315). The wire is
cells-only + redacted server-side — no raw ANSI ever reaches the browser. #}
{% endif %}
{{ detached_row() }}
{{ external_row() }}
desktop
Running
Open in Claude
{# Running but no connect URL yet: explain the transient capture gap instead
of silently dropping the headline "open on your phone" affordance (#427
UX-02). Both modes get a URL (pty's is scraped from the reassembled pty
screen, #665), so this is always a spinner placeholder, never a permanent
"no link" state. The chip is VISUAL only (aria-hidden); the screen-reader
announcement comes from a persistent aria-live region below, because a
live region toggled in via x-show (display:none→visible) is silently
skipped by NVDA/VoiceOver. #}
{# Persistent live region — always mounted, empty when idle — so the
announcement fires on a content change, not a display toggle (#427 UX-02). #}
{% if pty_screen_enabled %}
{# Read-only live terminal (#534): pty bridges only — standard bridges have no PTY.
The whole control is server-gated on pty_screen_enabled (no markup when off). #}
{% endif %}
{# Live-session list (#570): a STANDARD remote-control bridge can host several
concurrent sessions, and the row's "Open in Claude" link is only the bridge
CONNECT URL — not a per-session jump. Expand to list every live session under
the bridge with a direct per-session deep link + uptime. Shown from the first
live session (hasBridgeSessions); pty bridges are single-session and keep their
own link. Short-UUID labels only — friendly names deferred. x-text everywhere
(NEVER x-html): the sessionId is untrusted CLI output. #}
paused
( buffered)
{# The reconnecting/lost banners are mutually exclusive: the state machine sets one
and clears the other on every transition, but gate the info banner on
`!lost` too so a missed clear (e.g. an Alpine reactivity edge, cf. #310/#315)
can never stack BOTH banners at once — the warning always wins.
NB: keep `d-flex` OFF the x-show element. Tabler's `.d-flex` is
`display:flex !important`, which overrides the inline `display:none` that
x-show sets to hide — so a d-flex banner stays visible regardless of state
(the false "Live tail dropped/disconnected" banners bug). Put the flex layout
on an inner wrapper instead, like the connLost banner above does. #}
⏳ Live tail dropped — reconnecting…
{# Liveness-aware copy: only claim the bridge "may have stopped" when the snapshot
says it isn't alive. A live-tail WebSocket can drop while the bridge keeps
running (an idle proxy reaping a quiet socket) — saying it died would falsely
alarm the operator, so word that case as a transient tail drop. The
running/starting test mirrors the reconnect liveness gate in openLogs. #}
Live tail disconnected — the bridge may have stopped.
Live tail disconnected — the bridge is still running; click Reconnect to resume the tail.
Live terminal
{# Restart/disconnect affordance: a pty bridge restart writes a final "exited"
frame (the view freezes on the old session) and a dropped socket reads
"disconnected" — both resolve by toggling the view to reattach to the new
spawn. NB d-flex stays OFF the x-show element (Tabler !important; cf. #538). #}
{# role="alert" (assertive) matches the sibling log-tail disconnect banner — this
"session ended / toggle to reattach" message needs action, like that one. #}
Session ended — toggle Live terminal to reattach.
Live terminal disconnected — toggle to reconnect.
Nothing running yet — launch one from a project below.
{% if claustrum_enabled %}
{{ hosted_row(filtered=False) }}
{% endif %}
{# No live-session-filter x-show here: the Recent zone is decoupled from the
chips so ended rows always show and match recentCount() (#421). #}
{{ detached_row(filtered=False) }}
desktop
Stopped
{# `!!` coercion: a busy-map key absent on first paint renders this DISABLED
under Alpine 3.15.x inside an x-for clone — coerce to a concrete bool. #}
Projects
a folder Claude works in — launch a session from any of themhttps / ssh only · private/LAN hosts need
clone.allow_private_hosts in clauster.yml · cloning only fetches files (nothing runs).
Cancel this clone? The partial download is discarded — you can start it again.
A clone is already in progress (started in another tab) — showing its live progress here.
ships
— its code runs when you launch a session here. Review it before starting.
{% for p in projects %}
{% set idx = loop.index0 %}
{% include "_project_row.html" %}
{% endfor %}
Welcome to Clauster
Clauster spawns Claude Code into your project directories and lets you drive each session from claude.ai/code or the Claude mobile app — no SSH session, no terminal on the host.
Point projects_root at a folder whose subdirectories are projects, then
create or clone one below. Each becomes a card you can launch a bridge in.
No projects yet
Clauster runs Claude in a project directory under {{ projects_root }}.
Create one or clone a git repo to get started — or drop a directory there and it appears here.
Clean up leftover environments
When a session ends, its cloud environment can linger in the
claude.ai/code "New session" list with nothing running in it. Remove those here. The cloud
Default — and any environment still backing a live session — is never touched.
Scanning…