Clauster

Lost connection to the server — data may be stale. Retrying…

Before you start a session

These are your clauster doctor checks. are warnings — a session may still start; must be fixed before one will.

Active sessions

what Claude is running for you right now

No sessions match this filter.

{% if claustrum_enabled %} {% endif %} {# Pending interactive launch (#779): a pty spawn has no row (and no minted instance_id) until the POST returns — surface an explicit stub instead of leaving the click apparently ignored for the ready-wait seconds. #}

Nothing running yet — launch one from a project below.

{% if claustrum_enabled %} {% endif %}

Projects

a folder Claude works in — launch a session from any of them

Name

Type

Create empty Clone from git URL

run git init

Git URL shallow clone (--depth 1)

https / 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.

{% if projects %}

{% for p in projects %} {% set idx = loop.index0 %} {% include "_project_row.html" %} {% endfor %}

{% else %}

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 — create one or clone a git repo under {{ projects_root }} to get started.

{% endif %}

{% if reaper_ui_enabled %}

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…

{% endif %} {% if login_shepherd_enabled %}

Sign in to the runtime `claude` account

Fixes a logged-out or expired claude account without SSH. Pick a mode, open the authorize link in a new tab, approve it, then paste the code it gives you back here.

{# Non-interactive runtime-account auth (#848): apiKeyHelper / API key / OAuth-token deployments don't use the interactive flow above. Surface them next to it so an operator lands on the no-SSH config path. The secret-write plumbing already ships (#772/#773/#765); this only links to it, and stays fail-closed on the config_write.enabled gate. #}

Already authenticate non-interactively?

If this account uses an ANTHROPIC_API_KEY, a stored CLAUDE_CODE_OAUTH_TOKEN, or an apiKeyHelper command instead of an interactive login, set it in settings.json without SSH:

{# Runtime-account auth is account-wide, so it belongs in USER-scope settings.json — which the config editor only writes under the config_write.allow_user_scope opt-in. Offer the deep link (pinned to User scope) only when that's on; otherwise fail closed to a hint so an operator never saves the key into a project's settings.json where it wouldn't authenticate the account. #} {% if config_write_enabled and config_write_allow_user_scope %}

ANTHROPIC_API_KEY / CLAUDE_CODE_OAUTH_TOKEN — add an env row.
apiKeyHelper — add the key in Raw JSON mode.

{% elif config_write_enabled %}

Runtime-account auth belongs in User scope. Enable config_write.allow_user_scope to set it from the dashboard, or configure it over SSH.

{% else %}

Enable the Claude Code config editor (config_write.enabled + allow_user_scope) to set these from the dashboard, or configure them over SSH.

{% endif %}