LodyAI/Lody

Overview

Lody is a collaboration layer for coding agents a team already runs. It connects machines and ACP-compatible agents, then lets teammates share conversations, follow runtime status and code changes, and dispatch work from desktop, mobile, web, or the CLI. It targets teams that want shared visibility into agent work without passing around screenshots or pasted logs.

Supported agents include Claude Code, Codex, Kimi, OpenCode, and other ACP-compatible tools. Existing subscriptions, logins, models, and permission modes stay on the laptops, workstations, servers, or cloud VMs where they are configured, and machines remain private until their owner shares them with the workspace.

Two mechanisms are worth knowing. First, sessions can be given their own Git worktrees so parallel agent work stays isolated, with diffs, terminals, previews, and pull-request/CI status visible beside the conversation. Second, agents get tools to create or reuse other conversations, read status and history, send follow-ups, and cancel work, so one conversation can coordinate parallel investigation, implementation, and testing. The project also documents an E2EE core with a signed ledger and machine-sharing policy, and plans local-first synchronization using the Loro stack; full local-first support is described as still in progress.

Quick start

Prerequisites: Node.js with npx, and a machine where your coding agent and its credentials are already set up.

1. On a workstation, server, or cloud VM, start the daemon:

   npx lody daemon start
   

   The command opens a sign-in link and connects that machine to your workspace.

2. From a terminal, create a session against a workspace, agent config, and repository:

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

3. List sessions to check status:

   npx lody session list --workspace my-team
   

Desktop apps are available for macOS, Windows, and Linux through the download page, and native mobile clients through Google Play and the App Store. The full command set is in the CLI documentation. The README shows the daemon and session commands but does not walk through workspace creation or agent-config setup, so consult the quickstart and CLI reference for those prerequisites.

Constraints

• An agent must speak ACP to be connected; the machine's own subscriptions, logins, models, and permission modes continue to apply.
• The CLI session examples assume an existing workspace (my-team) and a matching agent config; those names are placeholders.
• The native iOS and Android clients are under active development and keep independent build toolchains, with setup and scope in the mobile README.
• Local-first behavior is a stated goal, not a completed capability. The repository uses CRDTs via Loro and includes end-to-end encryption packages, but the README explicitly says Lody is still moving toward full local-first support.
• The release process creates version-sync PRs and a GitHub Release with generated notes; it does not build or upload installers or auto-update files.
• The project is Apache-2.0 licensed and points contributors to CONTRIBUTING.md for development setup and PR size policy.

HotRepo's take

The repository recorded 1,756 stars and 190 forks on the 2026-11-14 TypeScript daily list, with 9 stars gained that day and a best position of 15. That is a single daily snapshot in one language list; it supports the fact that the project appeared on that list but not a trend claim. With no all-language daily rank recorded, the visible signal is a modest one-day gain rather than sustained momentum. The more concrete differentiator in the material is the combination of ACP agent support, CLI-driven sessions, isolated worktrees, and agent-to-agent session coordination, aimed at teams already using coding agents rather than individual users.

Project source and documentation