+5
Daily
1,777
stars
190
forks
5
watchers
2,325
prs
435
issues
6
releases
README
Lody
English | 简体中文
A shared workspace for the coding agents your team already uses.
Connect any machine and bring any coding agent through ACP. Share conversations with your team and dispatch work from desktop, mobile, web, or CLI.
Documentation
|
Getting Started
What you can do with Lody
Share Agent conversations with your team
Open the same conversation with your teammates. See the full transcript, runtime status, files, and code changes around the work, then add instructions without passing around screenshots or pasted logs.
Bring the Agents and machines you already use
Connect Claude Code, Codex, Kimi, OpenCode, or another ACP-compatible Agent. Keep using the subscriptions, logins, models, and permission modes configured on your laptops, workstations, servers, and cloud VMs. Machines remain private until their owner shares them with the workspace.
Dispatch work from any surface
Choose any connected machine when dispatching work from desktop, mobile, web, or CLI. Permission requests, progress, conversations, and code changes stay visible across these surfaces.
Connect a machine
Run Lody on a workstation, server, or cloud VM:
bash
npx lody daemon start
The command opens a sign-in link, connects the machine to your workspace, and keeps it available for work dispatched from desktop, mobile, web, or CLI.
Use Lody from the CLI
The CLI is more than the process that connects a machine. From a terminal or script, you can register local projects; inspect workspaces, machines, linked repositories, and Agent configs; create and message sessions; read their history and status; or archive and restore them. Commands that support --json can also feed Lody workspace data into your own tools.
bash
npx lody session create --workspace my-team --agent-config codex \
--repo owner/repo "Fix the failing test"
npx lody session list --workspace my-team
See the CLI documentation for the full command reference.
Let Agents coordinate work across conversations
Lody gives Agents tools to create or reuse other conversations, read their status and history, send follow-up instructions, cancel running work, and bring results back. This lets one conversation act as the coordinator: you can analyze a bug with a main Agent, then have it delegate investigation, implementation, and testing to separate conversations running in parallel.
Lody keeps each child conversation independent while preserving its relationship to the conversation that created it. Conversations can also be referenced with an @ mention when you or an Agent needs to connect work across sessions.
Keep code and execution in the same workspace
Keep parallel work isolated
Give sessions their own Git worktrees so Agents can work in parallel without mixing changes. Open multiple chats, files, diffs, terminals, and previews in tabs, or fork a session into another conversation or worktree to explore a different approachTop issues
#507[E2E] Daily desktop journey failure61 comments · 2026-09-08#930[Feature Request] Add a built-in Oh My Pi ACP adapter10 comments · 2026-09-24#104[Feature Request] Add global and provider-level controls to disable MCP5 comments · 2026-08-28#1501[Feature Request] 支持 Codex ultrafast 模式4 comments · 2026-10-12#1028[Bug] Machine access registration fails with a Server Error on every daemon start, leaving the live machine unauthorized (session create says "Machine not found" for the daemon itself)4 comments · 2026-09-26#2194[Bug] Agent Role listing holds other machines' `mf:` Flock rooms forever; each 120 s `initial_sync_timeout` flips the Streams transport to `disconnected` every ~2 min3 comments · 2026-11-01#939[Bug] CLI skips turn usage flush while Streams is healthy; skipped usage is never re-sent3 comments · 2026-09-24#782[Feature Request] Durable pin order on SessionMeta3 comments · 2026-09-17
Latest release
Lody OSS 0.109.0 v0.109.0 2026-10-30What's Changed fix: compact Roost renderer change receipts by @Lampese in https://github.com/LodyAI/Lody/pull/1784 perf: commit Roost renderer metadata with content by @Lampese in https://github.com/LodyAI/Lody/pull/1791 docs: record packed Roost storage contract validation by @Lampese in https://github.com/LodyAI/Lody/pull/1800 perf(roost): reuse unchanged owner projections by @Lampese in https://github.com/LodyAI/Lody/pull/1804 perf: install certified Roost text append projections by @Lampese in https://github.com/LodyAI/Lody/pull/1806 perf: reuse sealed Roost projections during window