Sandbox
@chadbyte/clay

Self-hosted workspace for coding agents and sessions

Clay Studio runs on your machine and opens a browser workspace for managing projects, live sessions, and agent activity. It ties together local coding-agent runtimes, shared project context, permissions, notifications, and file tools so work can continue across conversations and providers.

393 stars54 forksJavaScriptUpdated 7d ago
Who it's for

Builders who want their agent work to stay shared, persistent, and under their own control.

What it delivers

You can run multiple agents in one workspace, keep context between sessions, and hand work off without moving to another cloud.

What it does

Shared projects and live sessions

Organize several repositories in one sidebar, run sessions in parallel, and join or hand off a live session with presence and mentions.

Persistent mates

Create AI collaborators with their own identity, instructions, knowledge, memory, direct messages, and debate roles.

Cross-provider continuity

Use YOKE to give supported agents a common session interface and carry project instruction files across vendor boundaries.

Parallel and background work

Use git worktrees, spawned workers, scheduled tasks, and Ralph Loops while keeping visibility into what is running.

Workspace tools

Browse and edit files, inspect diffs and history, open terminals, install skills, connect MCP servers, and manage project knowledge from the same place.

Local control

Run the daemon on your own machine, keep sessions and knowledge on disk, and avoid routing project traffic through a Clay-hosted cloud.

How to get it

  1. 1Requirements: Node.js 20+ and at least one supported coding-agent CLI installed and…
    npx clay-server
    # Open the URL or scan the QR code from another device

README

Clay Studio symbol
Clay Studio

Where minds work together.

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

npm version npm downloads GitHub stars License: MIT

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.

npx clay-server
# Open the URL or scan the QR code from another device

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:

Browser → Clay Studio daemon → selected coding-agent runtime → model provider

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.

Common CLI commands

npx clay-server              # Start on the default port (2633)
npx clay-server -p 8080      # Use a different port
npx clay-server --add .      # Add the current directory
npx clay-server --list       # List registered projects
npx clay-server --shutdown   # Stop the daemon

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

Documentation

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

MIT

Files in the repo

Repository payload24 top-level entries
  • .claude-local
  • .github
  • bin
  • clay-dns
  • design
  • docs
  • lib
  • media
  • native-host
  • scripts
  • test
  • .gitignore
  • CHANGELOG.md
  • CLAUDE.md
  • CONTRIBUTING.md
  • DESIGN.md
  • LICENSE
  • LIVE_MARKDOWN_DEMO.md
  • package-lock.json
  • package.json
  • README.md
  • release.config.js
  • screenshot.gif
  • test-loop-output.txt

Discussion (0)

Ask about usage, or say what you built with it

Sign in to join the discussion.

No comments yet. Be the first to say what this is good for.

More tools

JuliusBrussee/
caveman

🪨 why use many token when few token do trick — Claude Code skill that cuts 65% of tokens by talking like caveman

105k
1 add
MemPalace/
mempalace

The best-benchmarked open-source AI memory system. And it's free.

59k
stablyai/
orca

Orca is the ADE for working with a fleet of parallel agents. Run any coding agent with your own subscription. Available on desktop, mobile and remote runtime.

66k

A cross-platform desktop All-in-One assistant for Claude Code, Codex, OpenCode, OpenClaw, Grok Build & Hermes Agent. Only official website: ccswitch.io

132k

Never stop coding. Free MIT AI gateway: one endpoint, 352 providers (150+ free), 1200+ models Kimi, Claude, GPT, Gemini, GLM, DeepSeek, MiniMax. Works with Claude Code, Codex, Cursor, OpenCode, Cline & Copilot. Quota-aware auto-fallback, RTK+Caveman compression saves 15-95% tokens, MCP/A2A, Desktop/PWA. Built by 550+ contributors

64k
headroomlabs-ai/
headroom

Compress tool outputs, logs, files, and RAG chunks before they reach the LLM. 20% fewer tokens for coding agents, 60-95% fewer tokens for JSON, same answers. Library, proxy, MCP server.

71k