claude-relay 2.36.0-beta.1 → 2.36.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 (2) hide show
  1. package/README.md +42 -37
  2. package/package.json +2 -2
package/README.md CHANGED
@@ -1,9 +1,13 @@
1
1
  <p align="center">
2
- <img src="media/logo/icon-full-banded-256-transparent.png" alt="Clay" />
2
+ <img src="media/logo/icon-full-banded-256-transparent.png" alt="Clay - self-hosted team workspace for Claude Code and Codex" />
3
3
  </p>
4
4
 
5
- <h2 align="center">Use Claude Code and Codex in a browser, with your whole team.</h2>
6
- <h4 align="center">Self-hosted on your machine. One toggle between vendors. No lock-in.</h4>
5
+ <h2 align="center">Multiplayer Claude Code and Codex.</h2>
6
+ <h4 align="center">
7
+ Drop into a teammate's session live.<br>
8
+ Or pair with AI mates that remember and push back.<br>
9
+ Self-hosted, one toggle between vendors.
10
+ </h4>
7
11
 
8
12
  <p align="center">
9
13
  <a href="https://www.npmjs.com/package/clay-server"><img src="https://img.shields.io/npm/v/clay-server" alt="npm version" /></a>
@@ -12,37 +16,25 @@
12
16
  <a href="https://github.com/chadbyte/clay/blob/main/LICENSE"><img src="https://img.shields.io/badge/License-MIT-yellow.svg" alt="License: MIT" /></a>
13
17
  </p>
14
18
 
15
- <p align="center"><img src="media/hero.png" alt="Clay workspace" /></p>
19
+ The browser tab your whole team lives in. Humans, AI agents, projects, sessions, decisions.
16
20
 
17
- Clay is a team workspace for Claude Code and Codex, self-hosted on your machine. Onboard your team to one tool, share sessions live, switch vendors with a toggle. Your code, your Mates, your decisions, all on disk.
21
+ Afraid of locking your personal or team knowledge into one vendor? With Clay, your conventions, sessions, and decisions live on your disk. Switch when you want.
22
+
23
+ *A team-shared, self-hosted GUI for Claude Code and Codex CLIs.*
18
24
 
19
25
  ```bash
20
26
  npx clay-server
21
27
  # Scan the QR code to connect from any device
22
28
  ```
23
29
 
24
- ## Why Clay
25
-
26
- **One workspace, many people.** Your whole team logs into the same workspace, not a personal editor with billing settings bolted on. Multi-user from day one, with OS-level isolation on Linux.
27
-
28
- **Many projects at once.** If you bounce between repos all day, keep them all loaded in one place and run agents in parallel across them. Permission requests and completed jobs surface as notifications so nothing goes silent in a tab you forgot to check.
29
-
30
- **Self-hosted.** Clay is a daemon on your machine. Your code, your sessions, your AI teammates' memory all live on disk in plain JSONL and Markdown. No proprietary database. No cloud relay. No middleman.
31
-
32
- **Vendor-agnostic.** Run Claude Code and Codex in the same workspace. Toggle vendors per session. When Anthropic raises prices or OpenAI changes terms, your workflow keeps moving. Same Mates, same projects, same memory, different model.
33
-
34
- **No lock-in.** Plain files you can grep, version, and back up. Standard cron expressions. MCP servers you already use. CLAUDE.md, AGENTS.md, .cursorrules, all loaded automatically across vendors. Walk away whenever you want, your data walks with you.
30
+ ## What's Clay?
35
31
 
36
- ## Built for Teams
37
-
38
- Clay is the workspace your team logs into, not a private editor with billing settings bolted on. Provision a server, invite your team, work in one place.
39
-
40
- - **Multi-user on a single server.** One Clay daemon hosts everyone on your team. No per-seat SaaS, no separate installs. Add users, they log in, they're in.
41
- - **OS-level isolation on Linux.** Opt in to provision each Clay user as a real Linux account. File ACLs are enforced via `setfacl`. Processes spawn under the right UID/GID. The isolation guarantees come from the OS, not from a promise in our docs.
42
- - **Each member brings their own login.** Share one org-wide API key, or let each user sign in with their own Claude Code or Codex account. Costs route to whoever ran the model.
43
- - **Drop into a teammate's session to help.** When someone gets stuck, jump into their project and pair in real time. Shared control, full history, no screen-share theater.
44
- - **@mention a teammate when you're stuck.** Ping them right inside the session. Their notification center lights up, their phone buzzes. No teammate around? @mention a Mate instead, same gesture, same place.
45
- - **Non-developers welcome.** PMs, designers, support engineers can log in to ask questions about the codebase, create issues, or read what the team built, without ever opening an editor.
32
+ - **A browser-based workspace for Claude Code and Codex.** Open it on any device, alone or with your whole team.
33
+ - **A place where your team collaborates across projects.** Engineers, PMs, designers, and domain experts share one workspace, hop between projects, drop into each other's sessions.
34
+ - **Your virtual team.** Mates with names, memory, and roles — architect, reviewer, designer, whoever you need. They learn your codebase, push back on bad ideas, and don't reset between sessions.
35
+ - **A multi-project dashboard.** Every repo on your machine in one sidebar. Run agents across several in parallel; permission requests and completions surface as notifications.
36
+ - **A self-hosted dev server.** Runs on your machine in plain JSONL and Markdown. No proprietary database, no cloud relay, no lock-in. Walk away whenever — your data walks with you.
37
+ - **A work-automation system.** Ralph Loop iterates a feature overnight; cron schedules agents while you're away. Wake up to results, or a clean failure trace.
46
38
 
47
39
  ## What it does
48
40
 
@@ -51,7 +43,7 @@ Clay is the workspace your team logs into, not a private editor with billing set
51
43
  Open a session, pick a vendor. Switch sessions, pick the other. Clay's adapter layer (YOKE) speaks the Claude Agent SDK and the Codex app-server protocol natively. Cross-vendor instruction loading: Codex reads AGENTS.md, Claude reads CLAUDE.md, Clay merges the rest into the system prompt automatically.
52
44
 
53
45
  <p align="center">
54
- <img src="media/split.gif" alt="split-screen workflow" width="700">
46
+ <img src="media/split.gif" alt="Toggle between Claude Code and Codex in one click" width="700">
55
47
  </p>
56
48
 
57
49
  ### Every project on one dashboard
@@ -62,6 +54,10 @@ All your projects live in the sidebar. Jump between them in one click, see live
62
54
 
63
55
  Mates are AI personas with their own CLAUDE.md, knowledge files, and memory that compounds across sessions. They learn your stack, your conventions, your decision history. @mention them mid-session, DM them directly, or drop them into a debate. **They don't flatter you. They push back.**
64
56
 
57
+ <p align="center">
58
+ <img src="media/mates.gif" alt="An AI teammate (Mate) pushing back on a bad design pitch in Clay" width="640">
59
+ </p>
60
+
65
61
  ### Debate: structured multi-Mate decisions
66
62
 
67
63
  Stuck on REST vs GraphQL? Monorepo or split? Surface the question to a debate. Pick panelists, set the format, let your Mates argue both sides with moderated turns. You walk away with a recorded decision, not a vibe check.
@@ -78,17 +74,23 @@ Write a `PROMPT.md`, optionally a `JUDGE.md`, hit go. Clay iterates: code, evalu
78
74
 
79
75
  Installable PWA on iOS and Android. Push notifications for approvals, errors, and completed tasks. Service worker keeps the app responsive offline. When Claude needs approval, your phone buzzes, you tap approve, the agent keeps going.
80
76
 
81
- <p align="center">
82
- <img src="media/phone.gif" alt="Clay on phone" width="280">
83
- </p>
84
-
85
77
  ## Who is Clay for
86
78
 
87
- - **Teams that want one shared workspace, not one editor each.** Onboard your whole team to a single tool, share sessions, set permissions per person, keep code on your own infrastructure.
88
- - **Teams hedging vendor risk.** You want Claude today, Codex tomorrow, and the freedom to flip without rewriting your workflow.
89
- - **Self-hosting developers who won't put their code in someone else's cloud.** You run the server, you own the data, you pick the model.
90
- - **Codex users tired of CLI-only workflows.** Clay treats Codex as a first-class citizen, not a Claude afterthought.
91
- - **Solo developers building an AI team.** Mates, Debate, and Ralph Loop give you reviewers, decision-makers, and an autonomous coding partner. Your team grows when you're ready.
79
+ ### Small teams (3–10)
80
+
81
+ Engineers, PMs, designers, and domain experts in one workspace. Non-devs read the codebase and ask questions without ever opening an editor. Engineers @mention each other or drop into a teammate's session to help in real time. Share one org-wide API key or let each member bring their own, with costs routing to whoever ran the model.
82
+
83
+ ### Larger teams (10+)
84
+
85
+ Per-user, per-project, per-session permissions. On Linux, opt in to OS-level isolation: each Clay user maps to a real Linux account, file ACLs enforced via `setfacl`, processes spawn under the right UID/GID. Per-project API keys for billing separation. Plain JSONL sessions give you an audit trail you can grep.
86
+
87
+ ### Solopreneurs and indie developers
88
+
89
+ You don't have a team yet, so Mates are your team. A persistent architect, a reviewer, a designer — each with their own memory, ready to push back on bad ideas. Run Ralph Loop overnight to ship while you sleep. Toggle Claude and Codex per session to balance cost and capability.
90
+
91
+ ### Self-hosting developers
92
+
93
+ Your code stays on your machine. Sessions are JSONL, knowledge is Markdown, settings are JSON. No proprietary database, no cloud relay, no middleman. CLAUDE.md, AGENTS.md, `.cursorrules` are all loaded automatically across vendors. Walk away whenever, your data walks with you.
92
94
 
93
95
  ## Getting Started
94
96
 
@@ -103,7 +105,7 @@ On first run, Clay asks for a port and whether you're solo or with a team. Open
103
105
  For remote access, use a VPN like Tailscale.
104
106
 
105
107
  <p align="center">
106
- <img src="media/start.gif" alt="Clay starting from CLI" width="600">
108
+ <img src="media/start.gif" alt="Starting Clay daemon from the CLI with npx clay-server" width="600">
107
109
  </p>
108
110
 
109
111
  ## CLI Options
@@ -132,6 +134,9 @@ No. Clay drives Claude Code through the [Claude Agent SDK](https://www.npmjs.com
132
134
  **"Can I run Claude Code and Codex in the same workspace?"**
133
135
  Yes. Pick a vendor when you open a session. Switch per session. Same projects, same Mates, same memory.
134
136
 
137
+ **"How are Mates different from Claude Code's sub-agents?"**
138
+ Sub-agents are ephemeral specialists spawned inside a single Claude Code session — a role and a system prompt for one task, then forgotten when the task ends. Mates are persistent teammates with their own knowledge files and memory that survive every session. A sub-agent forgets you the moment it returns; a Mate remembers your codebase, your decisions, and your conventions across months of work. @mention a Mate mid-session, DM it between sessions, or drop several into a debate.
139
+
135
140
  **"Does my code leave my machine?"**
136
141
  Only as model API calls (the same as using the CLI directly). Sessions, Mates, knowledge, and settings all stay on disk.
137
142
 
package/package.json CHANGED
@@ -1,12 +1,12 @@
1
1
  {
2
2
  "name": "claude-relay",
3
- "version": "2.36.0-beta.1",
3
+ "version": "2.36.0",
4
4
  "description": "Alias for clay-server — Web UI for Claude Code.",
5
5
  "bin": {
6
6
  "claude-relay": "./bin/cli.js"
7
7
  },
8
8
  "dependencies": {
9
- "clay-server": "2.36.0-beta.1"
9
+ "clay-server": "2.36.0"
10
10
  },
11
11
  "keywords": [
12
12
  "claude",