LodyAI/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

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.

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.

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.

Run Lody on a workstation, server, or cloud VM:

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.

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.

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.

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.

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 approach.

Browse project files and inspect per-turn or full-session diffs beside the conversation. Add line-level comments, follow pull request status and CI, and keep GitHub review threads close to the Agent that produced the change.

Open a running web app inside the session, switch between responsive viewports, and send element-level visual annotations back to the Agent.

• Agent Roles — share reusable Agent, model, permission, and instruction presets with the team.
• Attachments — send files and images from desktop, mobile, web, or CLI, and receive files produced by Agents.
• Session tools — search, pin, archive, fork, and organize conversations without losing their history.
• Desktop tools — use a built-in terminal, command palette, customizable shortcuts, and open files in your editor.
• Mobile controls — receive notifications, approve permission requests, inspect diffs, and follow active work with iOS Live Activities.
• Usage visibility — see context, token and quota usage, plus machine and Agent resource consumption.

Shared conversations are Lody's starting point, not the whole workspace.

We plan to add documents and document sandboxes so teams can shape requirements, preserve decisions, and work with Agents outside the timeline of a single conversation. Over time, these tools can become shared team context for understanding not only what changed, but why.

We want the entire workspace—not only conversations—to become local-first. Lody uses the Loro Stack, including Loro and Flock, to represent and synchronize collaborative state with CRDTs. The same foundation can extend from conversations to documents and future workspace tools. Our goal is for team context to become more durable and portable, and ultimately remain under the team's control.

Lody is still moving toward full local-first support.

Pushing a stable vX.Y.Z tag creates a draft PR synchronizing every apps/*/package.json version on the default branch, followed by a GitHub Release with generated changelog notes. No installers or auto-update files are built or uploaded. The original tag is not moved; version synchronization takes effect on the default branch after the PR is merged. GitHub Actions must be allowed to create pull requests in repository settings. Bot-created PRs may require a maintainer action to trigger CI. Existing releases and their assets are preserved on reruns.

• apps/cli — Connect machines and run coding agents
• apps/electron — Lody desktop app
• packages/components — Shared workspace UI
• packages/ui — Base UI primitives and StyleX design tokens
• packages/platform — Platform capabilities and integrations
• packages/shared — Shared schemas, protocols, and utilities
• packages/cloud-api — Optional-cloud protocol names and DTOs
• packages/e2ee-core — Experimental byte formats and signature verification (no product entrypoint)
• packages/loro-streams-rpc — RPC over Loro Streams
• packages/acp-extension-{core,kimi} — ACP extension submodule workspaces
• site-docs — Website, documentation, and blog

See CONTRIBUTING.md for development setup and the community PR size policy.