Lody

// Overview

Lody is an Apache-2.0 TypeScript project that describes itself as a shared workspace for the coding agents a team already uses. It is not a new agent: you connect machines (laptops, workstations, servers or cloud VMs) by running a daemon on them, and bring any agent that speaks the Agent Client Protocol (ACP), such as Claude Code, Codex, Kimi or OpenCode. Each agent keeps the subscriptions, logins, models and permission modes already configured on that machine, and a machine stays private until its owner shares it with the workspace.

The point is that the work becomes shared. Teammates can open the same agent conversation and see its full transcript, runtime status, files and code changes, then add their own instructions. Work can be dispatched to any connected machine from the desktop app (macOS, Windows, Linux), the iOS and Android apps, the web or the CLI, and permission requests, progress and diffs follow you across those surfaces, including approval from an iPhone Live Activity.

Inside a session Lody gives each piece of work its own Git worktree, tabs for chats, files, diffs, terminals and previews, per-turn and full-session diffs with line comments, and pull-request and CI status beside the conversation. Agents get tools to create other conversations, read their status, send follow-ups and collect results, so one conversation can coordinate parallel investigation, implementation and testing. The README says collaborative state is synchronised with the Loro CRDT stack and that the project is still moving toward full local-first support; using the apps and daemon requires signing in to a Lody account.

// What it does

• Connect any machine with one command and bring Claude Code, Codex, Kimi, OpenCode or any other ACP-compatible agent, using that machine's existing logins and models
• Shared agent conversations: teammates see the transcript, runtime status, files and code changes and can add instructions
• Dispatch work to any connected machine from desktop, iOS, Android, web or the CLI, with permission requests and progress on every surface
• Agent-to-agent coordination: a conversation can spawn, message, cancel and collect results from child conversations running in parallel
• Per-session Git worktrees, forking, file browser, per-turn diffs with line comments, and pull-request and CI status beside the agent

• In-session web app preview with responsive viewports and element-level visual annotations sent back to the agent
• Shared Agent Roles (agent, model, permission and instruction presets), attachments, a built-in terminal and token, quota and resource usage views

// Getting started

Lody's quickstart offers two routes: the desktop app, which also starts the local daemon that runs the agents, or the CLI daemon on its own for servers and headless machines. Both sign in to a Lody account through the browser.

brew install --cask lody

npx lody daemon start

# headless, with a token from the desktop app
npx lody daemon start --auth <cli_token>

npx lody project add <path>

npx lody session create --workspace my-team --agent-config codex \
  --repo owner/repo "Fix the failing test"

npx lody session list --workspace my-team

Commands and code are distilled from the project's own documentation — always check the official repo for the latest.

// How Lody compares

Lody alongside other open-source coding-agent harnesses & runtimes tools AI/TLDR tracks, ranked by GitHub stars.