npm - clay-server - Versions diffs - 2.19.0-beta.1 → 2.19.0 - Mend

clay-server 2.19.0-beta.1 → 2.19.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (4) hide show

package/README.md CHANGED Viewed

@@ -1,137 +1,109 @@
 # Clay
-<p align="center">
-  <img src="media/phone.gif" alt="Clay on phone" width="300">
-</p>
-<h3 align="center">Turn Claude Code into a team workspace. Any device, one command.</h3>
+<h3 align="center">Claude Code in your browser. Bring your team, or build one.</h3>
 [![npm version](https://img.shields.io/npm/v/clay-server)](https://www.npmjs.com/package/clay-server) [![npm downloads](https://img.shields.io/npm/dw/clay-server)](https://www.npmjs.com/package/clay-server) [![GitHub stars](https://img.shields.io/github/stars/chadbyte/clay)](https://github.com/chadbyte/clay) [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://github.com/chadbyte/clay/blob/main/LICENSE)
-Clay gives Claude Code a browser UI that runs on any device. Use it from your phone, run it on macOS, Windows, or Linux. Invite teammates, manage multiple projects from one sidebar, and get push notifications when Claude needs you. HTTPS and push notifications work out of the box with zero config. Built on the official Claude Agent SDK, not a terminal parser. Your machine is the server. No cloud relay in between, no extra network surface.
----
-## Getting Started
-**Requirements:** Node.js 20+, Claude Code CLI (authenticated).
+Everything Claude Code does, Clay does in your browser. Plus multi-session, file browser, scheduled agents, mobile notifications, and more. Invite your team to work together in the same session, or build an AI team from scratch. **Your machine is the server.** No cloud relay, no middleman.
 ```bash
 npx clay-server
+# Scan the QR code to connect from any device
 ```
-On first run, it walks you through port and PIN setup.
-Scan the QR code to connect from your phone instantly.
-For remote access, use a VPN like Tailscale.
-<p align="center">
-  <img src="media/start.gif" alt="Clay starting from CLI" width="600">
-</p>
 ---
-## Multi-session, multi-project
+## What you get
-Add a project in the browser and an agent attaches to it.
-Run backend, frontend, and docs simultaneously. Switch between them in the sidebar.
+### Everything the CLI does
-The server runs as a background daemon. Sessions persist even after you close the terminal.
-Mermaid diagrams render as diagrams. Tables render as tables.
-Code blocks highlight 180+ languages.
-Browse project files in the file browser — changes reflect live while the agent works.
+Your CLI sessions, your CLAUDE.md rules, your MCP servers. **All of it works in Clay as-is.** Pick up a CLI session in the browser, or continue a browser session in the CLI. Same SDK, same tools, same results.
 <p align="center">
   <img src="media/split.gif" alt="split-screen workflow" width="700">
 </p>
----
+### Everything the CLI doesn't
-## Multi-user
+**Multiple agents, multiple projects, at the same time.** Switch between them in the sidebar. Browse project files live while the agent works, with syntax highlighting for 180+ languages. Mermaid diagrams render as diagrams. Tables render as tables.
-Invite teammates and give them access to a project. They talk to Claude Code directly in the browser — no terminal, no setup on their end.
+**Schedule agents with cron**, or let them run autonomously with **Ralph Loop**. Your phone buzzes when Claude needs approval, finishes a task, or hits an error. Install as a **PWA for push notifications**. Close your laptop, sessions keep running.
-Add a CLAUDE.md and the AI operates within those rules: explains technical terms in plain language, escalates risky operations to seniors, summarizes changes in simple words.
+<p align="center">
+  <img src="media/phone.gif" alt="Clay on phone" width="280">
+</p>
-If someone gets stuck, join their session to unblock them in real time. Permissions can be separated per project and per session. Real-time presence shows who's where.
+### Bring your whole team
----
+**One API key runs the whole workspace.** Invite teammates, set permissions per person, per project, per session. A designer reports a bug in plain language. A junior dev works with guardrails. If someone gets stuck, **jump into their session** to help in real time.
-## Mates
+Add a CLAUDE.md and the AI operates within those rules: explains technical terms simply, escalates risky operations to seniors, summarizes changes in plain words. Real-time presence shows who's where.
-Build your team, even if you're solo.
+### Build your team with Mates
-Mates are AI teammates you create through conversation. Interview them, give them a name, avatar, and role. A code reviewer, a marketing lead, a writing partner. They remember how you work together and carry context across sessions.
+Not *"act like a design expert."* Mates are AI teammates shaped through real conversation, trained with your context, and built to hold their own perspective. Give them a name, avatar, expertise, and working style. **They don't flatter you. They push back.**
-They sit in your sidebar next to your human teammates. DM them, bring them into projects, let them work autonomously. In a multi-user workspace, your whole team, human and AI, works in one place.
+They live in your sidebar next to your human teammates. @mention them in any project session when you need their take, DM them directly, or bring multiple into the same conversation. Each Mate builds persistent knowledge over time, remembering past decisions, project context, and how you work together.
-<!-- screenshot: sidebar with Mates visible -->
+#### Debate before you decide
----
+Let your Mates challenge each other. Set up a debate. Pick a moderator and panelists, give them a topic, and let them go. You can raise your hand to interject. When it wraps up, you get opposing perspectives from every angle.
-## Mobile & notifications
+"Should we rewrite this in Rust?" "Should we delay the launch to fix onboarding?" "Should we position this as enterprise-first or PLG?" Get real opposing perspectives before you commit.
-Phone, tablet, couch. All you need is a browser.
-Pick up a terminal session in the browser. Continue a browser session from another device.
-One QR code to connect. Install as a PWA for a native-like experience.
+### Your machine, your server
-When Claude asks for approval, your phone buzzes. You also get notified on completion or error. No need to keep the browser open.
+Clay runs as a daemon on your machine. **No cloud relay, no intermediary service** between your browser and your code. Data flows directly to the Anthropic API, exactly as it does from the CLI.
-<p align="center">
-  <img src="media/push-notification.jpg" alt="push notification" width="300">
-</p>
+PIN authentication, per-project permissions, and HTTPS are built in. For remote access, use a VPN like Tailscale.
 ---
-## Automation
+## How a bug gets fixed
-The scheduler kicks off agents at set times.
-Have it check open issues and submit PRs every morning at 8 AM.
-Or compile world news and email you a digest every day.
+**Without Clay:**
+Designer finds a bug → writes up a ticket on Asana → dev asks clarifying questions → PM prioritizes → dev opens terminal, fixes it → shares a preview → QA checks → deploy
+<br>*7 steps. 3 people. 2 days.*
-Take it further with Ralph Loop, an autonomous coding loop built into Clay. The agent works, commits, and a judge evaluates. If it fails, a fresh session starts over with no memory of the previous attempt. Only the code carries over. Based on [Geoffrey Huntley's Ralph Wiggum technique](https://ghuntley.com/loop/).
+**With Clay:**
+Designer opens Clay in the browser, describes the bug in plain language → senior joins the same session, reviews the fix together → merge
+<br>*2 steps. 2 people. Minutes. The designer never touched a terminal.*
 ---
-## Security & Privacy
+## How Clay compares
-Your data flows directly from your machine to the Anthropic API, exactly as it does when you use the CLI. Clay adds a browser layer on top, not a middleman.
+*As of March 2026.*
-HTTPS is enabled by default with a builtin certificate. PIN authentication and per-project/session permissions are built in. For local network use, this is sufficient. For remote access, we recommend a VPN like Tailscale.
+| | CLI | Remote Control | Channels | **Clay** |
+|---|---|---|---|---|
+| Multi-user with roles | – | – | Platform-dependent | **Accounts + RBAC** |
+| AI teammates (Mates + Debates) | – | – | – | **Yes** |
+| Join teammate's session | – | – | – | **Yes** |
+| Persistent daemon | – | Session-based | – | **Yes** |
+| Native mobile app | – | **Yes** | **Platform app** | PWA |
+| Official support | **Anthropic** | **Anthropic** | **Anthropic** | Community |
----
+Clay is a community project, not affiliated with Anthropic. Official tools receive guaranteed support and updates.
-## Why Clay?
+---
-*As of March 2026.*
+## Getting Started
-| | CLI + Remote Control | tmux | Desktop | Cowork | **Clay** |
-|---|---|---|---|---|---|
-| Multi-user | ❌ | ✅ | ❌ | ❌ | ✅ |
-| Mobile / PWA | ✅ | ➖ | ➖ | ➖ | ✅ |
-| Push notifications | 🟠 | ❌ | 🟠 | ❌ | ✅ |
-| GUI | 🟠 | ❌ | ✅ | ✅ | ✅ |
-| Scheduler (cron) | 🟠 | ❌ | ✅ | ✅ | ✅ |
-| Scheduler survives logout | ❌ | ➖ | 🟠 | 🟠 | ✅ |
-| Join teammate's session | ❌ | 🟠 | ❌ | ❌ | ✅ |
+**Requirements:** Node.js 20+, Claude Code CLI (authenticated).
-✅ Supported · 🟠 Partial / limited · ❌ Not supported · ➖ N/A
+```bash
+npx clay-server
+```
----
+On first run, it walks you through port and PIN setup.
+Scan the QR code to connect from your phone instantly.
-## Key Features
+For remote access, use a VPN like Tailscale.
-* **Mates** - AI teammates with persistent identity, context, and memory. Create through an interview, DM them, collaborate across sessions.
-* **Multi-user** - Accounts, invitations, per-project/session permissions, real-time presence.
-* **Multi-agent** - Parallel agents per project, sidebar switching.
-* **Push notifications** - Approval, completion, error. Native-like PWA experience.
-* **Scheduler** - Cron-based automatic agent execution.
-* **Ralph Loop** - Autonomous coding loop. The agent works, a judge evaluates, and it iterates until it passes.
-* **File browser** - File exploration, syntax highlighting, live reload.
-* **Built-in terminal** - Multi-tab terminal, mobile keyboard support.
-* **Session search** - Full-text search across all conversation history.
-* **Session persistence** - Survives crashes, restarts, and network drops.
+<p align="center">
+  <img src="media/start.gif" alt="Clay starting from CLI" width="600">
+</p>
 ---
@@ -150,20 +122,11 @@ Yes. Pick up a CLI session in the browser, or continue a browser session in the
 Yes. If your project has a CLAUDE.md, it works in Clay as-is.
 **"Does each teammate need their own API key?"**
-No. Teammates share the Claude Code session logged in on the server. If needed, you can configure per-project environment variables to use different API keys.
+No. Teammates share the Claude Code session logged in on the server. You can also assign different API keys per project for billing isolation.
 **"Does it work with MCP servers?"**
 Yes. MCP configurations from the CLI carry over as-is.
-**"What are Mates?"**
-AI teammates you create through a conversation. Each Mate has a name, avatar, personality, and persistent memory. They live in your sidebar and you can DM them or bring them into projects.
-**"How is a Mate different from Claude Projects?"**
-Claude Projects save prompts and files as context. A Mate is a teammate. It has its own identity formed through an interview, remembers how you work together across sessions, and exists alongside your human teammates in the workspace. You're not organizing prompts. You're building a team.
-**"Can I create multiple Mates?"**
-Yes. Create as many as you need. A code reviewer, a writing partner, a project manager. Each one is independent.
 ---
 ## HTTPS

package/lib/config.js CHANGED Viewed

@@ -335,4 +335,5 @@ module.exports = {
   syncClayrc: syncClayrc,
   removeFromClayrc: removeFromClayrc,
   chmodSafe: chmodSafe,
+  isDevMode: _devMode,
 };

package/lib/server.js CHANGED Viewed

@@ -222,7 +222,9 @@ function isAuthed(req, authToken) {
 // --- Multi-user auth helpers ---
 // Multi-user auth tokens: persisted to disk so they survive restarts
-var TOKENS_FILE = path.join(CONFIG_DIR, "auth-tokens.json");
+var _isDevMode = require("./config").isDevMode;
+var TOKENS_FILE = path.join(CONFIG_DIR, _isDevMode ? "auth-tokens-dev.json" : "auth-tokens.json");
+var MULTI_USER_COOKIE = _isDevMode ? "relay_auth_user_dev" : "relay_auth_user";
 var multiUserTokens = {}; // token → userId
 function loadTokens() {
@@ -252,13 +254,13 @@ function createMultiUserSession(userId, tlsOptions) {
   var token = users.generateUserAuthToken(userId);
   multiUserTokens[token] = userId;
   saveTokens();
-  var cookie = "relay_auth_user=" + token + "; Path=/; HttpOnly; SameSite=Strict; Max-Age=31536000" + (tlsOptions ? "; Secure" : "");
+  var cookie = MULTI_USER_COOKIE + "=" + token + "; Path=/; HttpOnly; SameSite=Strict; Max-Age=31536000" + (tlsOptions ? "; Secure" : "");
   return { token: token, cookie: cookie };
 }
 function getMultiUserFromReq(req) {
   var cookies = parseCookies(req);
-  var token = cookies["relay_auth_user"];
+  var token = cookies[MULTI_USER_COOKIE];
   if (!token) return null;
   var userId = multiUserTokens[token];
   if (!userId) return null;
@@ -962,13 +964,13 @@ function createServer(opts) {
     if (req.method === "POST" && fullUrl === "/auth/logout") {
       if (users.isMultiUser()) {
         var cookies = parseCookies(req);
-        var token = cookies["relay_auth_user"];
+        var token = cookies[MULTI_USER_COOKIE];
         if (token && multiUserTokens[token]) {
           delete multiUserTokens[token];
           saveTokens();
         }
         res.writeHead(200, {
-          "Set-Cookie": "relay_auth_user=; Path=/; HttpOnly; SameSite=Strict; Max-Age=0" + (tlsOptions ? "; Secure" : ""),
+          "Set-Cookie": MULTI_USER_COOKIE + "=; Path=/; HttpOnly; SameSite=Strict; Max-Age=0" + (tlsOptions ? "; Secure" : ""),
           "Content-Type": "application/json",
         });
       } else {

package/package.json CHANGED Viewed

@@ -1,6 +1,6 @@
 {
   "name": "clay-server",
-  "version": "2.19.0-beta.1",
+  "version": "2.19.0",
   "description": "Web UI for Claude Code. Any device. Push notifications.",
   "bin": {
     "clay-server": "./bin/cli.js",