Lody
Lody is a shared workspace for running AI coding agents in parallel across desktop, phone, browser, and CLI. It brings agent conversations, runtime state, files, diffs, GitHub work, and team context into one collaborative workspace.
At a Glance
- Software teams and engineering organizations
- Small teams of 20 people or fewer (the open-source announcement specifically solicits these teams for trials)
- Developers using Claude Code, Codex, Gemini CLI, OpenCode, Kimi, or other ACP-compatible coding agents
- Teams operating across desktop, mobile, browser, remote servers, or multiple machines
- +1 more
AI Tools by Lody
(1)
Lody
Team Workspace for Coding Agents
Discussions
No discussions yet
Be the first to start a discussion about Lody
Latest News
Lody v0.104.0 adds iOS Simulator control, Nowledge Mem Agent Role identities, Devin support, expanded PR/MCP tooling, and many fixes.
Lody passes 1,000 GitHub stars and publishes a behind-the-scenes engineering post about generating a Remotion celebration video in code.
Lody explains how teams can hand off and continue the same Claude Code session, including its live context, diffs, worktree, branch, and agent configuration.
Lody announces that its CLI and local desktop client are open source and outlines a longer-term local-first shared-understanding layer for software teams and agents.
Products & Services
Collaborative workspace for running coding-agent sessions with shared conversations, isolated Git worktrees, real-time diffs, team context, machine management, and GitHub/PR workflows.
Command-line tools for starting and managing sessions, including daemon mode for connecting servers, cloud VMs, or other machines and dispatching work remotely.
Desktop application for macOS, Windows, and Linux; the local desktop client was open sourced on August 25, 2026.
Native iOS and Android clients for starting tasks, reviewing diffs, approving permissions, receiving notifications, and monitoring agent sessions away from a desk.
Market Position
Lody positions itself as a shared, cross-device workspace and control plane for coding agents rather than another standalone model or code editor. Its documented distinction from screenshot/transcript/share-link tools and Lore is that teammates can enter the same live session, see the same diffs and worktree, and continue the work; it also competes for workflow budget with standalone coding-agent products and agent workspaces such as Claude Code, Codex, Cursor, Cline, and similar tools while integrating many of them.
Founding Story
Lody says it was created to address context collisions when multiple coding agents work on the same codebase, limited visibility into agent changes, desktop-bound workflows, and the difficulty of sharing agent context with teammates. Its initial vision was to combine isolated Git worktrees, real-time synchronization, mobile access, and team workspaces; it later described a broader goal of becoming a shared understanding layer connecting conversations, code, tasks, documents, and past decisions.
Business Model
Revenue Model
Freemium workspace subscription. Lody charges for collaboration-workspace capacity rather than AI tokens; users bring their own Claude Code, Codex, or model-provider subscriptions/API accounts with no Lody markup.
Pricing Tiers
2 workspaces, up to 200 sessions per workspace, 30 turns per session, up to 3 team members, mobile access, and 40+ agent support with BYOK.
Unlimited conversations, unlimited turns per conversation, unlimited team members, and seat billing for accepted workspace members.
Custom contracts and invoicing, security/procurement support, SSO and access controls, deployment guidance, and a dedicated support channel.
Target Markets
- Software teams and engineering organizations
- Small teams of 20 people or fewer (the open-source announcement specifically solicits these teams for trials)
- Developers using Claude Code, Codex, Gemini CLI, OpenCode, Kimi, or other ACP-compatible coding agents
- Teams operating across desktop, mobile, browser, remote servers, or multiple machines
- Organizations needing enterprise contracts, governance, procurement, SSO, or rollout support
- Running multiple coding agents on separate features or bug fixes without worktree collisions
- Reviewing agent output, diffs, permissions, and previews from a phone or browser
- Sharing an active coding-agent session with a teammate for live handoff and continuation
- Coordinating sub-agents across repositories, machines, and operating systems
- Connecting remote development machines, servers, or CI-oriented environments
- Managing GitHub issues, pull requests, CI checks, reviews, and merges from the agent workspace