
Letswork
io.github.saicharanrajoju由 GitHub 账号 saicharanrajoju 发布v3.0.0更新于 Oct 24, 2026
Real-time collaborative coding via MCP — two developers, one codebase
概览
LetsWork 让两名开发者通过 Claude Code 共享同一项目,借助 Cloudflare 隧道提供文件锁与主机审批的编辑流程。
- 可以做什么
- 列出并读取项目文件,并显示文件锁定状态
- 提交文件写入,锁定与解锁文件以独占编辑
- 查看会话信息、在线用户、活动锁与通知
- 访客端:设置显示名称并查看自己待审批的改动
- 主机端:查看带差异的待审批改动,批准或拒绝,强制释放卡住的锁
- 适用场景
- 适合两名开发者从不同机器结对处理同一代码库、各自使用自己的 Claude Code,且项目所有者希望访客的每次写入都先经自己审核再落盘的情况。
- 运行要求
- 需在 macOS 或 Windows(WSL)本地安装:Python 3.10+、letswork 包、Node.js 与 Claude Code,主机还需 cloudflared。主机启动会话后把一次性加入链接和令牌发给访客。未声明需要账号或 API 密钥。
安装
在 SourceWeft 中
- 打开 控制台中的 Letswork,将其添加到工作区。
- 为需要使用其工具的对话启用该服务。
Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。
其他 MCP 客户端
参照 仓库 中的启动说明。
README
LetsWork
Real-time collaborative coding via Claude Code — two developers, one codebase, each using their own Claude subscription.
One developer hosts the session. The other joins from anywhere. Both get a live Claude Code window connected to the same project — with file locking and an approval system to prevent conflicts.
How It Works
- Host runs
letswork startinside their project folder - A secure HTTPS tunnel is created automatically via Cloudflare
- A one-time URL + guest token is generated and printed
- Host shares the join command with the guest
- Guest runs
letswork join <url> --token <token>on their machine - Both developers now have Claude Code connected to the same codebase
Requirements
macOS — Host Setup
The host is the developer who owns the project. You start the session and share the join command.
Step 1 — Install dependencies
Step 2 — Install Claude Code
Step 3 — Start the session
Navigate to your project folder and run:
You will be asked for your display name, then a session box appears:
Copy the full letswork join ... command and send it to your collaborator.
Two new terminal windows open automatically:
- Claude Code — already connected to LetsWork
- A chat window to communicate with your collaborator
Step 4 — Approve guest changes
When the guest edits a file, you'll see a notification in Claude Code. Ask Claude:
Then approve or reject:
Step 5 — Stop the session
Press Ctrl+C in the terminal where you ran letswork start.
macOS — Guest Setup
The guest connects to the host's project. You need the join command from the host.
Step 1 — Install dependencies
Step 2 — Install Claude Code
Step 3 — Join the session
Run the command the host sent you:
You'll be asked for your display name. Then two windows open:
- Claude Code — connected to the host's project
- A chat window to communicate with the host
Step 4 — Edit files
Ask Claude to read and edit files normally. When you write a file, it goes into an approval queue — the host reviews it before it's written to disk. You'll get a notification when it's approved or rejected.
Windows — Guest Setup (WSL)
LetsWork runs inside WSL (Windows Subsystem for Linux). The guest experience is the same as macOS once WSL is set up.
Step 1 — Enable WSL and install Ubuntu
Open PowerShell as Administrator and run:
Restart your computer when prompted. Ubuntu will install automatically.
Open Ubuntu from the Start menu and set up your Linux username and password.
Step 2 — Install dependencies inside Ubuntu
Open Ubuntu and run these one by one:
Step 3 — Install Claude Code inside Ubuntu
Step 4 — Join the session
Run the command the host sent you, inside Ubuntu:
You'll be asked for your display name. Claude Code launches directly in the same terminal window.
Note for Windows users: Claude Code runs in the WSL terminal — not as a separate window. Everything else works identically to macOS.
MCP Tools Available
Both host and guest have access to these tools inside Claude Code:
Approval Flow
Guest file writes do not go directly to disk — they go through the host's approval queue:
- Guest asks Claude to edit a file →
write_filesubmits the change - Host sees:
📝 guest submitted change to server.py (ID: a1b2c3) - Host asks Claude:
get_pending_changes— sees a full diff - Host approves:
approve_change a1b2c3→ file is written to disk - Or rejects:
reject_change a1b2c3→ guest is notified
Security
- Random Cloudflare subdomain — URL is unguessable
- Cryptographic token — second auth layer on top of the URL
- All traffic encrypted via HTTPS
- Path traversal prevention — guest cannot access files outside the project root
- File locks auto-expire after 30 minutes
- No accounts, no signup, no persistent credentials — session ends when host stops
Constraints
- Maximum 2 users per session (Host + 1 Guest)
- Text files only — binary files not supported
- 1MB file size limit per read/write operation
- Guest has no shell access — file operations only
cloudflaredmust be installed on the host machine (guest does not need it on macOS, but WSL guests do)
CLI Reference
Architecture
The guest connects through a stdio proxy rather than directly over HTTP — this avoids Cloudflare SSE reliability issues and gives stable MCP connectivity.
License
MIT — see LICENSE
Built with the Model Context Protocol.
来源:README.md,提交 2361029
工具
0版本历史
1- v3.0.0最新Sep 16, 2026
评分
已满足适用检查项的 50%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
- 近 30 天内可连通25 分
请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。
- 已声明认证方式10 分
请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。
- 已列出工具15 分
请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证10 分