clay-server weekly downloads statistics

Where minds work together.

A self-hosted workspace where people and coding agents work together across projects, sessions, and providers.

Clay Studio turns local coding agents into a shared, persistent team. Run different agents from one browser workspace, join a teammate's live session, keep project knowledge between conversations, and automate work without handing your workspace to another cloud.

Quick start

Requirements: Node.js 20+ and at least one supported coding-agent CLI installed and authenticated.

Clay Studio runs on your machine and serves the workspace to your browser. For access outside your local network, use a private network such as Tailscale.

Why Clay Studio

Work together

Projects, sessions, people, and agents share one workspace. Teammates can see live activity, enter the same session, hand off work, and respond to permission requests without gathering around one terminal.

Keep the context

Sessions do not have to be disposable chats. Mates retain their roles and knowledge, project instructions carry across supported runtimes, and decisions remain available when the next task begins.

Stay in control

The daemon runs on infrastructure you control. Sessions and knowledge live on disk in portable JSONL and Markdown rather than a proprietary database. Change coding agents without migrating the workspace around them.

Supported coding agents

Clay Studio currently includes integrations for:

Claude Code · Codex · Grok Build · Kimi Code · GitHub Copilot CLI · Qwen Code · Junie CLI · Antigravity CLI · OpenCode · Kiro CLI

Clay detects locally installed runtimes and exposes the ones available on your machine. Each runtime keeps its own authentication and may expose different models, modes, and capabilities.

Core capabilities

• Shared projects and live sessions. Organize several repositories in one sidebar, run sessions in parallel, and collaborate with presence, cursors, mentions, and handoffs. • Persistent Mates. Create AI collaborators with their own identity, instructions, knowledge, memory, direct messages, and roles in structured debates. • Cross-provider continuity. YOKE gives supported coding agents a common session interface and carries project instruction files across vendor boundaries. • Parallel and background work. Use git worktrees, paired sessions, spawned workers, scheduled tasks, and Ralph Loops without losing visibility into what is running. • A workspace on every device. Use the desktop browser or install the PWA on mobile. Receive push notifications for approvals, failures, and completed work. • Tools where the work happens. Browse and edit files, inspect diffs and history, open terminals, install skills, connect MCP servers, and manage project knowledge from the same workspace.

Your machine is the server

The normal request path is:

Clay Studio does not relay project traffic through a Clay-hosted cloud. Your code leaves the machine only when the selected runtime sends it to its model provider, just as it would when you use that CLI directly.

The d.clay.studio hostname used for local HTTPS is a DNS-only service: no application data passes through it. See clay-dns for the implementation and threat model.

Reverse proxies and tunnels

If your proxy rewrites the upstream Host header, open Server Settings → Network → Reverse proxy & tunnels and add your browser-facing origin, for example https://clay.example.com. Enter one HTTP or HTTPS origin per line, with a port when needed and no path or wildcard. Only server administrators can edit this setting in multi-user mode. Saving applies to new WebSocket connections without a restart; existing connections stay open until they reconnect, and authentication remains required. When Clay refuses a WebSocket because of its origin, the daemon log notes the refused origin (at most once a minute).

If the tunnel cannot connect yet, use a working local connection to configure it. Alternatively, stop the daemon, add "allowedOrigins": ["https://clay.example.com"] to the existing ~/.clay/daemon.json (or the daemon config in your CLAY_HOME), preserving its other fields, and start Clay again. Direct connections and proxies that preserve Host normally need no additional origins. Forwarded headers are not trusted automatically.

Common CLI commands

Run npx clay-server --help for the complete command reference.

Documentation

• Changelog

Community

The community-built Clay Stream Deck plugin turns physical buttons into a live dashboard for sessions, worktrees, and permission requests.

Building something with Clay Studio? Share it in GitHub Discussions.

Disclaimer

Clay Studio is not affiliated with the providers of the coding agents it supports. Product names and trademarks belong to their respective owners. The software is provided "as is," and users are responsible for complying with the terms of their selected providers.

License

Clay Studio as a whole is licensed under the GNU Affero General Public License, version 3 only (AGPL-3.0-only). Preexisting portions previously covered by the project’s MIT license retain the grants and applicable notices from that license; see LICENSES/MIT-legacy.txt and the licensing scope notice. Third-party components remain under their respective licenses.

Description from the npm listing.