clay-server 2.21.0-beta.3 → 2.21.0

package/README.md

@@ -2,13 +2,13 @@
   <img src="media/logo/icon-full-banded-256-transparent.png" alt="Clay" />
 </p>
 
-<h3 align="center">Your AI dev team. Not another coding agent.</h3>
+<h3 align="center">Claude Code for your whole team. No team? Build one with AI.</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)
 
 <p align="center"><img src="media/hero.png" alt="Clay workspace" /></p>
 
-A team workspace built on Claude Code. AI teammates who remember your decisions, challenge your thinking, and grow with your codebase. Runs on your machine.
+Everything Claude Code does, in your browser and on your phone. Multi-session, multi-user, self-hosted. No cloud relay, no middleman.
 
 ```bash
 npx clay-server
@@ -19,64 +19,59 @@ npx clay-server
 
 ## What you get
 
-### Debate before you decide
+### Drop-in replacement for the CLI
 
-<!-- TODO: debate.gif -->
+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.
 
-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.
+<p align="center">
+  <img src="media/split.gif" alt="split-screen workflow" width="700">
+</p>
 
-"REST vs GraphQL for the new API?" "Monorepo or separate repos?" "This architecture won't scale past 10k users. Here's why." Get opposing perspectives before you commit.
+### Claude Code on steroids
 
-### Build your team with Mates
+**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.
 
-<!-- TODO: mates.gif -->
+**Schedule agents with cron**, or let them run autonomously with **Ralph Loop**. Close your laptop, sessions keep running.
 
-Mates are AI teammates shaped through real conversation, built to hold their own perspective. Give them a name, avatar, expertise, and working style. **They don't flatter you. They push back.**
+**Push notifications on mobile.** Your phone buzzes when Claude needs approval, finishes a task, or hits an error. Install as a PWA on iOS or Android, review and approve from anywhere.
 
-@mention them in any project session, 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.
+<p align="center">
+  <img src="media/phone.gif" alt="Clay on phone" width="280">
+</p>
 
-### Drop-in replacement
+### Your machine, your server, your data
 
-Your existing agent setup works as-is. CLI sessions, CLAUDE.md rules, MCP servers. **No migration needed.** Pick up a CLI session in the browser, or continue a browser session in the CLI.
+**Fully local.** Clay runs as a daemon on your machine. Your code and conversations never leave your machine except to reach the AI provider's API.
 
-### Your machine, your server
+**Plain files.** Sessions are JSONL. Settings are JSON. Knowledge is Markdown. Everything lives on your machine in formats you can read, move, and back up. No proprietary database, no cloud lock-in.
 
-Clay runs as a daemon on your machine. **No cloud relay, no intermediary service.** Schedule agents with cron, get push notifications on your phone, close your laptop. Sessions keep running.
+**Secure by default.** PIN authentication, per-project permissions, and HTTPS are built in.
 
 ### Bring your whole team
 
-**One API key runs the whole workspace.** Invite teammates, set permissions per person, per project, per session. If someone gets stuck, **jump into their session** to help in real time.
-
-### Before vs Clay
+**One API key runs the whole workspace.** Invite teammates, set permissions per person, per project, per session. Share one key across the org, or let each member use their own Claude Code login.
 
-| Before | With Clay |
-|---|---|
-| One CLI session at a time | Multiple agents across projects, persistent |
-| No shared context across teammates | Shared workspace with roles and permissions |
-| No memory between decisions | AI that remembers past decisions and challenges new ones |
-| No teammates, just prompts | Mates with names, knowledge, and opinions |
+**OS-level isolation.** On Linux, Clay maps each user to an OS-level account. File permissions and process isolation just work.
 
-### Why not just use Claude Code directly?
+**Shared sessions.** Your PM describes a bug in plain language, your senior joins the same session, and the fix ships together. If someone gets stuck, **jump into their session** to help in real time.
 
-Claude Code is excellent for solo coding. Clay is for when you need more than a single agent session. A team that debates your architecture decisions. AI colleagues who remember what you decided last month. A workspace where your human teammates and AI teammates sit side by side.
+### Build your AI team
 
-If Claude Code is a solo instrument, Clay is the band.
-
-## Who is Clay for
+**Mates.** AI teammates with persistent memory across sessions. They learn your stack, your conventions, and your decision history. @mention them for a quick review, DM them directly, or bring multiple into the same conversation. **They don't flatter you. They push back.**
 
-- **Solo dev juggling multiple roles.** You need a code reviewer, a marketing lead, a writing partner, but it's just you. Build them as Mates.
-- **Small team sharing one AI workflow.** One API key, everyone in the browser, no terminal knowledge required.
-- **Founder doing dev + product + ops.** Run agents overnight, get notified on your phone, review in the morning.
+<!-- TODO: mates.gif -->
 
-## Why I built Clay
+**Debate.** Your Mates argue both sides before you commit. "REST vs GraphQL?" "Monorepo or separate repos?" "This migration plan won't survive production. Here's why."
 
-I wanted AI teammates, not just a coding agent. The underlying agent is the best foundation for a personal AI I've found. I wanted to turn it into my own AI assistant, one that knows my context, remembers my decisions, and works the way I work.
+<!-- TODO: debate.gif -->
 
-That started as a browser interface so I could access it from anywhere. Then I added multi-user so my team could use it too. Then I started building the AI teammates themselves.
+---
 
-Most AI agent projects go for full autonomy. Let the AI loose, give it all the permissions, let it run. I wanted the opposite: **AI that works as part of a team.** Visible, controllable, accountable. Your teammates can see what the agent is doing, jump in when it needs help, and set the rules it operates under.
+## Who is Clay for
 
-That's Clay now. A workspace where AI teammates have names, persistent memory, and their own perspective. Not "act like an expert" prompting. Actual teammates that push back, remember last week, and sit in your sidebar next to your human colleagues.
+- **Solo dev who needs a second opinion.** Architecture review, dependency decisions, refactor tradeoffs. Build reviewers as Mates instead of asking the void.
+- **Small team sharing one Claude Code setup.** One API key, everyone in the browser, no terminal knowledge required.
+- **Dev lead running agents overnight.** Schedule tasks with cron, get push notifications on your phone, review in the morning.
 
 ## Getting Started
 
@@ -87,43 +82,50 @@ npx clay-server
 ```
 
 On first run, it asks for a port number and whether you're using it solo or with a team.
-Scan the QR code to connect from your phone instantly.
+Open the browser URL or scan the QR code to connect from your phone instantly.
 
 For remote access, use a VPN like Tailscale.
 
-## Philosophy
-
-**AI is a teammate, not a tool.** A tool gets used once and forgotten. A teammate accumulates your history, your decisions, your working style. Give them a specialty, let them build context over time, and bring them into any project as a colleague.
-
-**AI should understand you first.** When you create a Mate, set up a scheduled task, or start a Ralph Loop, Clay interviews you. Not to save time, but to use AI's capability to understand what you actually want. "Just do it for me" is a trap. The better AI understands you, the better the output.
-
-**Your data is yours.** Sessions are JSONL files. Settings are JSON. Knowledge is Markdown. Everything lives on your machine in formats you can read, move, and back up. No proprietary database, no cloud lock-in. If you stop using Clay tomorrow, your data doesn't disappear.
-
-**Friction is a feature.** The goal of AI is not to remove all friction. It's to free you to focus on the friction that matters. Reviewing a critical decision, shaping the direction, catching what the agent missed. Clay keeps those moments in, on purpose.
+<p align="center">
+  <img src="media/start.gif" alt="Clay starting from CLI" width="600">
+</p>
 
 ## FAQ
 
-**"Is this just a terminal wrapper?"**
-No. Clay is a team workspace that happens to use Claude as its engine. It manages AI teammates, persistent knowledge, and structured debates. The agent runtime is an implementation detail.
+**"Is this just a Claude Code wrapper?"**
+Clay uses the [Claude Agent SDK](https://www.npmjs.com/package/@anthropic-ai/claude-agent-sdk) directly. It doesn't wrap terminal output. It adds multi-session orchestration, persistent AI teammates (Mates), structured debates, scheduled agents, multi-user collaboration, and a full browser UI.
 
 **"Does my code leave my machine?"**
-The Clay server runs locally. Files stay local. Only Claude API calls go out, which is the same as using the CLI.
+Clay is fully self-hosted. The server runs on your machine, files stay local. Only API calls go out, same as using the CLI directly.
 
-**"Can I continue a CLI session?"**
+**"Can I continue a CLI session in the browser?"**
 Yes. Pick up a CLI session in the browser, or continue a browser session in the CLI.
 
 **"Does my existing CLAUDE.md work?"**
 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. You can also assign different API keys per project for billing isolation.
+No. Teammates can share one org-wide API key. On Linux with OS-level isolation, each member can also use their own Claude Code login. You can 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.
 
+**"Can I use it on my phone?"**
+Yes. Clay works as a PWA on iOS and Android. You get push notifications for approvals, errors, and completed tasks. No app store required.
+
 **"What is d.clay.studio in my browser URL?"**
 It's a DNS-only service that resolves to your local IP for HTTPS certificate validation. No data passes through it. All traffic stays between your browser and your machine. See [clay-dns](clay-dns/) for details.
 
+## Why I built Clay
+
+Claude Code is the best coding agent I've found. I wanted to turn it into a team, not just a single-player tool.
+
+That started as a browser interface so I could access it from anywhere. Then I added multi-user so my team could use it too. Then I started building the AI teammates themselves.
+
+Most AI agent projects go for full autonomy. Let the AI loose, give it all the permissions, let it run. I wanted the opposite: **AI that works as part of a team.** Visible, controllable, accountable. Your teammates can see what the agent is doing, jump in when it needs help, and set the rules it operates under.
+
+That's Clay now. A workspace where AI teammates have names, persistent memory, and their own perspective. Not "act like an expert" prompting. Actual colleagues who remember last week and sit in your sidebar next to the human ones.
+
 ## CLI Options
 
 ```bash
@@ -132,20 +134,16 @@ npx clay-server -p 8080      # Specify port
 npx clay-server --yes        # Skip interactive prompts (use defaults)
 npx clay-server -y --pin 123456
                               # Non-interactive + PIN (for scripts/CI)
-npx clay-server --no-https   # Disable HTTPS
-npx clay-server --local-cert # Use local certificate (mkcert) instead of builtin
-npx clay-server --no-update  # Skip update check
-npx clay-server --debug      # Enable debug panel
 npx clay-server --add .      # Add current directory to running daemon
-npx clay-server --add /path  # Add project by path
 npx clay-server --remove .   # Remove project
 npx clay-server --list       # List registered projects
 npx clay-server --shutdown   # Stop running daemon
 npx clay-server --dangerously-skip-permissions
                               # Bypass all permission prompts (requires PIN at setup)
-npx clay-server --dev        # Dev mode (foreground, auto-restart on lib/ changes, port 2635)
 ```
 
+Run `npx clay-server --help` for all options.
+
 ## Architecture
 
 Clay drives agent execution through the [Claude Agent SDK](https://www.npmjs.com/package/@anthropic-ai/claude-agent-sdk) and streams it to the browser over WebSocket.
@@ -187,9 +185,7 @@ If you're using Clay, let us know how in Discussions:
 
 ## Disclaimer
 
-This is an independent project and is not affiliated with Anthropic. Claude is a trademark of Anthropic.
-
-Clay is provided "as is" without warranty of any kind. Users are responsible for complying with the terms of service of underlying AI providers (e.g., Anthropic, OpenAI) and all applicable terms of any third-party services. Features such as multi-user mode are experimental and may involve sharing access to API-based services. Before enabling such features, review your provider's usage policies regarding account sharing, acceptable use, and any applicable rate limits or restrictions. The authors assume no liability for misuse or violations arising from the use of this software.
+Not affiliated with Anthropic. Claude is a trademark of Anthropic. Provided "as is" without warranty. Users are responsible for complying with their AI provider's terms of service.
 
 ## License
 

package/lib/sdk-bridge.js

@@ -1234,9 +1234,9 @@ function createSDKBridge(opts) {
       // Auto-approve safe Bash commands (read-only, non-destructive)
       if (toolName === "Bash" && input && input.command) {
         var cmd = input.command.trim();
-        var firstWord = cmd.split(/[\s;|&]/)[0];
         var safeBashCommands = {
-          ls: true, cat: true, head: true, tail: true, wc: true, file: true,
+          // Navigation (harmless on its own, checked in compound commands below)
+          cd: true, pushd: true, popd: true,
           // File/dir inspection
           ls: true, cat: true, head: true, tail: true, wc: true, file: true,
           stat: true, find: true, tree: true, du: true, df: true,
@@ -1273,7 +1273,16 @@ function createSDKBridge(opts) {
           nslookup: true, host: true, ping: true, traceroute: true,
           curl: true, wget: true, http: true,
         };
-        if (safeBashCommands[firstWord]) {
+        // Split compound commands (&&, ||, ;, |) and check ALL segments
+        var segments = cmd.split(/\s*(?:&&|\|\||[;|])\s*/);
+        var allSafe = true;
+        for (var si = 0; si < segments.length; si++) {
+          var seg = segments[si].trim();
+          if (!seg) continue;
+          var firstWord = seg.split(/\s/)[0];
+          if (!safeBashCommands[firstWord]) { allSafe = false; break; }
+        }
+        if (allSafe) {
           return Promise.resolve({ behavior: "allow", updatedInput: input });
         }
       }

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "clay-server",
-  "version": "2.21.0-beta.3",
-  "description": "Web UI for Claude Code. Any device. Push notifications.",
+  "version": "2.21.0",
+  "description": "Self-hosted Claude Code in your browser. Multi-session, multi-user, push notifications.",
   "bin": {
     "clay-server": "./bin/cli.js",
     "claude-relay": "./bin/claude-relay.js"