# lody

Podium publishes this catalog and sells an agent development environment. Podium chooses the products, criteria, sources and wording, so treat these pages as vendor-authored research. Check important claims against the linked primary sources. The same evidence rules apply to Podium and its competitors, but they do not remove this conflict of interest.

Page: https://adecomparison.com/ade/lody/
Website: https://lody.ai
Research: covered

Method: https://adecomparison.com/method/

Rank by must-haves met, then preferences, then name. Read each finding's checked date. Findings stay published after their scheduled recheck. Checks over six months old may be outdated.

## lody:ACC-01

Finding: Desktop installers cover macOS Universal, Windows x64 and Linux x86-64; native iOS/Android apps, a hosted web app and the lody CLI expose the workspace. The hosted web client has a production phone renderer selected from mobile browser user agents independently of native app shells. Editor extensions are absent; external-editor launchers are separate.

Verification: sourced
Checked: 2026-11-13
Scheduled recheck: 2027-03-13
Plan: Not specified
Surface: Lody Electron desktop app; Lody native iOS and Android apps; Lody hosted web app; Lody CLI and daemon
Version: Lody v0.109.0 (e7b7ab7aacf17f3ee056a6d708ad5ac3c18fb60f); targeted first-party pass 2026-11-13; no installed-product test

The phone-browser mapping follows the production browser renderer; no installed-device scenario was run. Native mobile editing and app-specific capabilities retain their documented scope.

Source: https://lody.ai/download/
Locator: Desktop, Mobile and browser, Browser sections
Finding: Desktop: macOS Universal (Apple Silicon and Intel), Windows x64, Linux AppImage and Debian/Ubuntu x86-64. Mobile: iOS App Store, Android Google Play and signed APK. Browser: hosted web app. This page presents the complete client list.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/quickstart/
Locator: Install, sign-in, add project, connect GitHub, configure agents, file locations
Finding: Install desktop/mobile/CLI, sign in (browser), add local dir via picker or npx lody project add, connect GitHub, add agent configs and Test them, run npx lody daemon start on servers. Local data under ~/.lody/repos and ~/.lody/logs.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/cli/
Locator: Command reference: login, daemon, workspaces, sessions, machines, agent configs, review, export
Finding: lody CLI is both the daemon runtime (lody start / daemon start) and a one-shot manager: session create/chat/list/status, project/workspace/machine/agent-config commands, lody review prompting and rendering, lody export, import-magpie, --json output; built-in help is the flag source of truth.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/session/
Locator: Composer, fork, side chat, session list, archive/restore/delete, Quick Session, Open in editor
Finding: Sessions bundle conversation, branch and worktree; fork/side-chat reuse history; sidebar shows status, repo, branch, PR and diff stats; archive retains history and reclaims worktrees; restore recreates them; Quick Session desktop shortcut; Open-in launches VS Code/Xcode/Sublime/Zed (external launchers, not extensions).
Retrieved: 2026-11-13

Source: https://lody.ai/docs/mobile/
Locator: Install, Live Activities, push notifications, progress/diff monitoring, offline support
Finding: Native iOS (App Store + TestFlight) and Android apps: notifications on task completion/approval/PR-ready, iOS Live Activities incl. actionable permission alerts, diff review and approvals, project file browsing; realtime editing is desktop-only; offline viewing of cached conversations with sync on reconnect.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/scheduled-tasks/
Locator: Triggers, owning machine, agent-proposed schedules, missed runs, FAQ
Finding: Scheduled/manual/one-shot tasks run on one owning machine (CLI, local timezone; nothing runs in cloud); agent can only propose schedules, never create them; missed runs catch up once; only the creator can edit/pause/delete; machine must be awake.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/local-project/
Locator: Adding projects, local-first availability, CLI history sync, team visibility, limitations
Finding: Any local directory works with synced chat/diffs/branches/worktrees; desktop works offline with later sync; imports Codex/Claude CLI history; team visibility is opt-in per project; local projects cannot push to remote branches directly.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/first-session/
Locator: Walkthrough, stop control, archive, FAQ (no GitHub needed)
Finding: First session works on a plain local directory without GitHub; stop control cancels the active turn; archived sessions keep branch and conversation and are restorable.
Retrieved: 2026-11-13

Source: https://github.com/LodyAI/Lody/tree/v0.109.0/apps/cli/src/commands
Locator: session.ts, machine.ts, daemon.ts, agent-config.ts, github.ts, review.ts, export.ts, magpie-import.ts, internal.ts
Finding: CLI implements session/machine/daemon/agent-config/GitHub/review/export/magpie commands; no public REST API surface or SDK package in commands, packages or docs.
Retrieved: 2026-11-13

Source: https://github.com/LodyAI/Lody/blob/v0.109.0/apps/cli/src/lib/notifications/AGENTS.md
Locator: Turn/outcome notification pipeline, mobile/cloud ports, best-effort delivery
Finding: Turn outcomes project into control documents and mobile push via the cloud port with best-effort delivery (no outbox, retry, reconnect replay or exactly-once); permission push and Live Activity sync are separate paths.
Retrieved: 2026-11-13

Source: https://github.com/LodyAI/Lody/blob/e7b7ab7aacf17f3ee056a6d708ad5ac3c18fb60f/packages/components/src/hooks/use-mobile.ts
Locator: checkIsMobileDevice; device-class.ts; production sidebar/chat routing
Finding: The shared production web components recognize iPhone/Android browser user agents independently of native shell detection and select the touch-oriented mobile renderer. The hosted web client is publicly linked from the complete download page. This establishes browser phone access beyond merely having native apps.
Retrieved: 2026-11-13

## lody:ACC-02

Finding: Nine built-in ACP providers plus every ACP Registry runtime and Custom ACP launch commands; Lody launches provider servers, negotiates capabilities and reuses machine-side logins. Mixed-harness sessions run side by side and coordinate through a primary agent.

Verification: agent-cross-checked
Checked: 2026-11-13
Scheduled recheck: 2027-03-13
Plan: Not specified
Surface: Lody Electron desktop app; Lody native iOS and Android apps; Lody hosted web app; Lody CLI and daemon
Version: v0.109.0 (commit 2eefb5e); source pass 2026-11-13

Only the cited atomic findings are established. Remaining atomic requirements and the full rubric scenario remain unverified.
Model catalogs resolve per runtime; Lody publishes no standalone model-provider list.

Source: https://lody.ai/
Locator: Hero, provider wall, daemon section, machine-sharing and usage sections
Finding: Team agent workspace: parallel worktrees, live diff review, design mode, mobile access; bring existing Claude Code/Codex/Grok/Kimi subscriptions; ACP-compatible agents plug in; npx lody daemon start connects any machine; sessions shared with usage by member and PR/CI/merge in-session.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/parallel-agents/
Locator: Isolated worktrees, mixed agents, team visibility, coordinator handoff, FAQ
Finding: Multiple sessions each with own worktree/branch; mix Claude Code/Codex/Kimi/Grok per session; team sees running sessions via All Tasks; concurrency limited by host machine capacity; agent-to-agent coordination via Agent Session Control.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/agent-collaboration/
Locator: Orchestrator walkthrough: triage, cross-repo fix, review-fix loop, @ mentions
Finding: Primary agent triages PR/issue queues, delegates fixes/reviews to Kimi/Codex/Grok sessions across machines, exchanges findings via @ session mentions, and collects commits; examples are illustrative prompts, not benchmark results.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/magpie/
Locator: Import targets, gateway, statuses, model management
Finding: One command imports Magpie provider setups (Claude, Codex, Pi, DSH, Kimi, Grok, Bub) on the same server; upstream API keys stay in Magpie; import does not prove inference works; cloud workspaces only, not OSS local-only mode.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/cli-runtimes/
Locator: ACP Registry runtimes, Custom ACP, prerequisites note
Finding: Every ACP Registry runtime (Auggie, Autohand, Codebuddy, Cline, Factory, Gemini, Kimi, OpenCode, Qwen, pi ACP) plus Custom ACP launch commands; host must have the runtime command, login and credentials installed; models depend on runtime and account.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/acp-feature-support/
Locator: Support matrix, extension capability reference, notes
Finding: Nine built-in providers (Claude Code, Codex, Grok, Kimi Code, Devin, Pi, DeepSeek Harness, Bub, Dimcode) share the ACP baseline; optional capabilities (MCP transports, resume/fork, steering, tasks, subagents, goals, usage, rate limits) differ per adapter via acp-extension-core; declarations are read at session start so updates can shift the matrix.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/from-codex-claude-code/
Locator: What stays the same, concept mapping, migration checklist, FAQ
Finding: Lody launches the same provider CLIs and reuses machine-side subscription logins, API env config, and repo instruction files (AGENTS.md/CLAUDE.md); sessions resume like --resume; CLI remains supported for quick one-off edits.
Retrieved: 2026-11-13

## lody:ACC-03

Finding: Existing agent subscriptions and API/env credentials stay on the machine and are reused at zero markup; Lody sells no tokens. A Lody account is required for cloud workspaces while local-only use and lody review work without sign-in.

Verification: agent-cross-checked
Checked: 2026-11-13
Scheduled recheck: 2027-03-13
Plan: Not specified
Surface: Lody Electron desktop app; Lody native iOS and Android apps; Lody hosted web app; Lody CLI and daemon
Version: v0.109.0 (commit 2eefb5e); source pass 2026-11-13

Only the cited atomic findings are established. Remaining atomic requirements and the full rubric scenario remain unverified.
No local-model route is documented; vendor-side spend caps are not a Lody control.

Source: https://lody.ai/price/
Locator: Plan cards, feature table, FAQ (tokens, seats, cancellation)
Finding: Free ($0 forever: 2 workspaces, 200 sessions/workspace, 30 turns/session, 3 members) vs Plus ($8/seat/month billed yearly, unlimited) vs Enterprise (custom; SSO, procurement, rollout). No AI token charges; BYO agent accounts at zero markup. Prices USD; yearly upfront per seat for 12 months.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/cli/
Locator: Command reference: login, daemon, workspaces, sessions, machines, agent configs, review, export
Finding: lody CLI is both the daemon runtime (lody start / daemon start) and a one-shot manager: session create/chat/list/status, project/workspace/machine/agent-config commands, lody review prompting and rendering, lody export, import-magpie, --json output; built-in help is the flag source of truth.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/parallel-agents/
Locator: Isolated worktrees, mixed agents, team visibility, coordinator handoff, FAQ
Finding: Multiple sessions each with own worktree/branch; mix Claude Code/Codex/Kimi/Grok per session; team sees running sessions via All Tasks; concurrency limited by host machine capacity; agent-to-agent coordination via Agent Session Control.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/scheduled-tasks/
Locator: Triggers, owning machine, agent-proposed schedules, missed runs, FAQ
Finding: Scheduled/manual/one-shot tasks run on one owning machine (CLI, local timezone; nothing runs in cloud); agent can only propose schedules, never create them; missed runs catch up once; only the creator can edit/pause/delete; machine must be awake.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/agent-roles/
Locator: Role creation, sharing, mentions, offline-machine behavior
Finding: Roles package machine, agent config, model, reasoning, permission and instruction; private until shared with workspace; mentionable via @ to start new conversations; bound to one machine/config and unusable while offline.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/lody-review/
Locator: Review format, report contents, requirements, options
Finding: npx lody review renders a local Git review into a self-contained shareable HTML report without signing in; runs read-only against the local repo; first render may download and cache a verified viewer.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/magpie/
Locator: Import targets, gateway, statuses, model management
Finding: One command imports Magpie provider setups (Claude, Codex, Pi, DSH, Kimi, Grok, Bub) on the same server; upstream API keys stay in Magpie; import does not prove inference works; cloud workspaces only, not OSS local-only mode.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/cli-runtimes/
Locator: ACP Registry runtimes, Custom ACP, prerequisites note
Finding: Every ACP Registry runtime (Auggie, Autohand, Codebuddy, Cline, Factory, Gemini, Kimi, OpenCode, Qwen, pi ACP) plus Custom ACP launch commands; host must have the runtime command, login and credentials installed; models depend on runtime and account.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/from-codex-claude-code/
Locator: What stays the same, concept mapping, migration checklist, FAQ
Finding: Lody launches the same provider CLIs and reuses machine-side subscription logins, API env config, and repo instruction files (AGENTS.md/CLAUDE.md); sessions resume like --resume; CLI remains supported for quick one-off edits.
Retrieved: 2026-11-13

Source: https://lody.ai/terms/
Locator: Provider, sign-in, fees/billing, account rules
Finding: Provider LoroHub LLC; sign-in via GitHub OAuth; free and paid (Plus) plans with prices on the pricing page in USD; user retains content ownership with a services-only license grant.
Retrieved: 2026-11-13

Source: https://github.com/LodyAI/Lody/tree/v0.109.0/apps/cli/src/commands
Locator: session.ts, machine.ts, daemon.ts, agent-config.ts, github.ts, review.ts, export.ts, magpie-import.ts, internal.ts
Finding: CLI implements session/machine/daemon/agent-config/GitHub/review/export/magpie commands; no public REST API surface or SDK package in commands, packages or docs.
Retrieved: 2026-11-13

## lody:ACC-04

Finding: Quick Start covers install, sign-in, project add, agent-config test and first session; plain directories, local Git repos and GitHub repos are all supported. The daemon onboards BYO servers; no vendor-managed compute onboarding exists.

Verification: agent-cross-checked
Checked: 2026-11-13
Scheduled recheck: 2027-03-13
Plan: Not specified
Surface: Lody Electron desktop app; Lody native iOS and Android apps; Lody hosted web app; Lody CLI and daemon
Version: v0.109.0 (commit 2eefb5e); source pass 2026-11-13

Only the cited atomic findings are established. Remaining atomic requirements and the full rubric scenario remain unverified.
Session-level worktrees require Git; managed-cloud setup is absent.

Source: https://lody.ai/docs/quickstart/
Locator: Install, sign-in, add project, connect GitHub, configure agents, file locations
Finding: Install desktop/mobile/CLI, sign in (browser), add local dir via picker or npx lody project add, connect GitHub, add agent configs and Test them, run npx lody daemon start on servers. Local data under ~/.lody/repos and ~/.lody/logs.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/session/
Locator: Composer, fork, side chat, session list, archive/restore/delete, Quick Session, Open in editor
Finding: Sessions bundle conversation, branch and worktree; fork/side-chat reuse history; sidebar shows status, repo, branch, PR and diff stats; archive retains history and reclaims worktrees; restore recreates them; Quick Session desktop shortcut; Open-in launches VS Code/Xcode/Sublime/Zed (external launchers, not extensions).
Retrieved: 2026-11-13

Source: https://lody.ai/docs/parallel-agents/
Locator: Isolated worktrees, mixed agents, team visibility, coordinator handoff, FAQ
Finding: Multiple sessions each with own worktree/branch; mix Claude Code/Codex/Kimi/Grok per session; team sees running sessions via All Tasks; concurrency limited by host machine capacity; agent-to-agent coordination via Agent Session Control.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/scheduled-tasks/
Locator: Triggers, owning machine, agent-proposed schedules, missed runs, FAQ
Finding: Scheduled/manual/one-shot tasks run on one owning machine (CLI, local timezone; nothing runs in cloud); agent can only propose schedules, never create them; missed runs catch up once; only the creator can edit/pause/delete; machine must be awake.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/github/
Locator: GitHub App setup, issue/PR context, PR panel, auto-archive, commit/push, review sync
Finding: GitHub App gives repo access; issues/PRs inject context via @; PR panel shows state/CI/comments/reviews with in-Lody merge and branch delete; review comments sync both ways; PR-linked sessions auto-archive on merge/close; optional act-as-you identity for PR actions.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/cli-runtimes/
Locator: ACP Registry runtimes, Custom ACP, prerequisites note
Finding: Every ACP Registry runtime (Auggie, Autohand, Codebuddy, Cline, Factory, Gemini, Kimi, OpenCode, Qwen, pi ACP) plus Custom ACP launch commands; host must have the runtime command, login and credentials installed; models depend on runtime and account.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/local-project/
Locator: Adding projects, local-first availability, CLI history sync, team visibility, limitations
Finding: Any local directory works with synced chat/diffs/branches/worktrees; desktop works offline with later sync; imports Codex/Claude CLI history; team visibility is opt-in per project; local projects cannot push to remote branches directly.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/first-session/
Locator: Walkthrough, stop control, archive, FAQ (no GitHub needed)
Finding: First session works on a plain local directory without GitHub; stop control cancels the active turn; archived sessions keep branch and conversation and are restorable.
Retrieved: 2026-11-13

Source: https://lody.ai/terms/
Locator: Provider, sign-in, fees/billing, account rules
Finding: Provider LoroHub LLC; sign-in via GitHub OAuth; free and paid (Plus) plans with prices on the pricing page in USD; user retains content ownership with a services-only license grant.
Retrieved: 2026-11-13

## lody:ACC-05

Finding: The lody CLI manages the full session lifecycle with --json output, and Lody hosts its own session-tools MCP server (stdio + HTTP) while acting as an MCP client. No public REST API, SDK, or webhook receiver exists.

Verification: agent-cross-checked
Checked: 2026-11-13
Scheduled recheck: 2027-03-13
Plan: Not specified
Surface: Lody CLI and daemon; Lody Electron desktop app
Version: v0.109.0 (commit 2eefb5e); source pass 2026-11-13

Only the cited atomic findings are established. Remaining atomic requirements and the full rubric scenario remain unverified.
The MCP server commands are marked internal with no stability commitment.

Source: https://lody.ai/docs/cli/
Locator: Command reference: login, daemon, workspaces, sessions, machines, agent configs, review, export
Finding: lody CLI is both the daemon runtime (lody start / daemon start) and a one-shot manager: session create/chat/list/status, project/workspace/machine/agent-config commands, lody review prompting and rendering, lody export, import-magpie, --json output; built-in help is the flag source of truth.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/session-orchestration/
Locator: Built-in Lody MCP tools: create/reuse, status, follow-up, cancel, model/reasoning selection
Finding: Agents use built-in Lody MCP tools to create/reuse conversations, read status and bounded history, send follow-ups, cancel running turns, select compatible model/reasoning, and bring results back; parent relationship preserved; bounded to Lody conversation data, not a background scheduler.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/encrypted-workspaces/
Locator: Standard vs encrypted comparison, device approval, recovery, known limits
Finding: In E2E workspaces only authorized devices can read content; servers relay/store unreadable data; new devices need approval; loss of all devices plus recovery file means permanent loss; browser security depends on served code; price page flags E2E as coming soon on Plus.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/concepts/
Locator: Mental model, core objects, Agent Config vs Role, MCP/daemon/permission scope glossary
Finding: Workspace holds members, machines, sessions and settings; session = one task/conversation/branch; Agent Config = runtime plus auth and machine; Lody exposes built-in MCP tools for cross-session work; daemon is the background CLI that runs agents.
Retrieved: 2026-11-13

Source: https://lody.ai/terms/
Locator: Provider, sign-in, fees/billing, account rules
Finding: Provider LoroHub LLC; sign-in via GitHub OAuth; free and paid (Plus) plans with prices on the pricing page in USD; user retains content ownership with a services-only license grant.
Retrieved: 2026-11-13

Source: https://github.com/LodyAI/acp-extension-core/releases/tag/v0.3.0
Locator: Release tag and date
Finding: Provider-neutral ACP extension contract v0.3.0 (2026-10-27); sibling adapter repos (claude/codex/kimi/grok/dsh/pi/devin/omp) carry no releases and are inspected at default branch; all Apache-2.0.
Retrieved: 2026-11-13

Source: https://github.com/LodyAI/Lody/tree/v0.109.0/apps/cli/src/commands
Locator: session.ts, machine.ts, daemon.ts, agent-config.ts, github.ts, review.ts, export.ts, magpie-import.ts, internal.ts
Finding: CLI implements session/machine/daemon/agent-config/GitHub/review/export/magpie commands; no public REST API surface or SDK package in commands, packages or docs.
Retrieved: 2026-11-13

Source: https://github.com/LodyAI/Lody/tree/v0.109.0/apps/cli/src/mcp
Locator: lody-mcp-server.ts (@modelcontextprotocol/server), lody-mcp-http-server.ts, session-mcp-resolver.ts, schedule-tools.ts, agent-role-tools.ts, authentication/
Finding: Lody hosts its own MCP server (session/daemon/schedule/role tools over stdio and HTTP loopback) for agents, and resolves the workspace MCP catalog plus OAuth/keychain credentials into ACP sessions as an MCP client.
Retrieved: 2026-11-13

Source: https://github.com/LodyAI/Lody/blob/v0.109.0/apps/cli/src/commands/internal.ts
Locator: lody-mcp-server / lody-mcp-http-host command definitions
Finding: Internal commands expose the Lody session-tools MCP server over stdio and HTTP; marked (internal), so no public stability commitment is made for the MCP surface.
Retrieved: 2026-11-13

Source: https://github.com/LodyAI/Lody/tree/v0.109.0/apps/cli/src/lib/schedules
Locator: schedule-command-service, schedule-documents; pr-poller/ for PR polling
Finding: Schedule storage and command service live in the CLI on the owning machine; PR state arrives via polling (pr-poller/), and no webhook receiver exists in apps/cli, packages or docs.
Retrieved: 2026-11-13

## lody:ACC-06

Finding: Workspace MCP catalog with OAuth and per-transport negotiation feeds agents; custom ACP commands, AGENTS.md/skills/roles imports and keychain-backed auth are product-managed while runtime behavior is inherited from the harness.

Verification: agent-cross-checked
Checked: 2026-11-13
Scheduled recheck: 2027-03-13
Plan: Not specified
Surface: Lody Electron desktop app; Lody CLI and daemon
Version: v0.109.0 (commit 2eefb5e); source pass 2026-11-13

Only the cited atomic findings are established. Remaining atomic requirements and the full rubric scenario remain unverified.
No product plugin system exists; plugins appear only as external runtime prerequisites.

Source: https://lody.ai/docs/session/
Locator: Composer, fork, side chat, session list, archive/restore/delete, Quick Session, Open in editor
Finding: Sessions bundle conversation, branch and worktree; fork/side-chat reuse history; sidebar shows status, repo, branch, PR and diff stats; archive retains history and reclaims worktrees; restore recreates them; Quick Session desktop shortcut; Open-in launches VS Code/Xcode/Sublime/Zed (external launchers, not extensions).
Retrieved: 2026-11-13

Source: https://lody.ai/docs/agent-roles/
Locator: Role creation, sharing, mentions, offline-machine behavior
Finding: Roles package machine, agent config, model, reasoning, permission and instruction; private until shared with workspace; mentionable via @ to start new conversations; bound to one machine/config and unusable while offline.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/magpie/
Locator: Import targets, gateway, statuses, model management
Finding: One command imports Magpie provider setups (Claude, Codex, Pi, DSH, Kimi, Grok, Bub) on the same server; upstream API keys stay in Magpie; import does not prove inference works; cloud workspaces only, not OSS local-only mode.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/cli-runtimes/
Locator: ACP Registry runtimes, Custom ACP, prerequisites note
Finding: Every ACP Registry runtime (Auggie, Autohand, Codebuddy, Cline, Factory, Gemini, Kimi, OpenCode, Qwen, pi ACP) plus Custom ACP launch commands; host must have the runtime command, login and credentials installed; models depend on runtime and account.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/acp-feature-support/
Locator: Support matrix, extension capability reference, notes
Finding: Nine built-in providers (Claude Code, Codex, Grok, Kimi Code, Devin, Pi, DeepSeek Harness, Bub, Dimcode) share the ACP baseline; optional capabilities (MCP transports, resume/fork, steering, tasks, subagents, goals, usage, rate limits) differ per adapter via acp-extension-core; declarations are read at session start so updates can shift the matrix.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/from-codex-claude-code/
Locator: What stays the same, concept mapping, migration checklist, FAQ
Finding: Lody launches the same provider CLIs and reuses machine-side subscription logins, API env config, and repo instruction files (AGENTS.md/CLAUDE.md); sessions resume like --resume; CLI remains supported for quick one-off edits.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/concepts/
Locator: Mental model, core objects, Agent Config vs Role, MCP/daemon/permission scope glossary
Finding: Workspace holds members, machines, sessions and settings; session = one task/conversation/branch; Agent Config = runtime plus auth and machine; Lody exposes built-in MCP tools for cross-session work; daemon is the background CLI that runs agents.
Retrieved: 2026-11-13

Source: https://github.com/LodyAI/Lody/tree/v0.109.0/apps/cli/src/mcp
Locator: lody-mcp-server.ts (@modelcontextprotocol/server), lody-mcp-http-server.ts, session-mcp-resolver.ts, schedule-tools.ts, agent-role-tools.ts, authentication/
Finding: Lody hosts its own MCP server (session/daemon/schedule/role tools over stdio and HTTP loopback) for agents, and resolves the workspace MCP catalog plus OAuth/keychain credentials into ACP sessions as an MCP client.
Retrieved: 2026-11-13

Source: https://github.com/LodyAI/Lody/blob/v0.109.0/apps/cli/src/agent/agent-client.ts
Locator: permissionMode/permission plumbing; lody-acp-extension steering/rate-limit snapshots
Finding: Per-session permission modes flow into agent runs with steering support and rate-limit snapshots where the adapter declares them; personal/project credential grants stay machine-local.
Retrieved: 2026-11-13

## lody:ACC-07

Finding: Desktop is an Electron app (pinned source); mobile ships as native iOS/Android apps whose client code post-dates the pinned release. No hybrid wrapper is documented.

Verification: agent-cross-checked
Checked: 2026-11-13
Scheduled recheck: 2027-05-12
Plan: Not specified
Surface: Lody Electron desktop app; Lody native iOS and Android apps
Version: v0.109.0 (commit 2eefb5e); source pass 2026-11-13

Only the cited atomic findings are established. Remaining atomic requirements and the full rubric scenario remain unverified.
Mobile client code landed after v0.109.0, so mobile implementation rests on official docs plus store distribution.

Source: https://lody.ai/download/
Locator: Desktop, Mobile and browser, Browser sections
Finding: Desktop: macOS Universal (Apple Silicon and Intel), Windows x64, Linux AppImage and Debian/Ubuntu x86-64. Mobile: iOS App Store, Android Google Play and signed APK. Browser: hosted web app. This page presents the complete client list.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/mobile/
Locator: Install, Live Activities, push notifications, progress/diff monitoring, offline support
Finding: Native iOS (App Store + TestFlight) and Android apps: notifications on task completion/approval/PR-ready, iOS Live Activities incl. actionable permission alerts, diff review and approvals, project file browsing; realtime editing is desktop-only; offline viewing of cached conversations with sync on reconnect.
Retrieved: 2026-11-13

Source: https://github.com/LodyAI/Lody/blob/HEAD/apps/mobile/README.md
Locator: Native clients, setup/scope, credits and origins
Finding: New native iOS and Android clients under active development with independent build toolchains; iOS built directly on Innei lody-ios with provenance-tracked runtime snapshot reused on Android; mobile client code landed after pinned release v0.109.0.
Retrieved: 2026-11-13

Source: https://github.com/LodyAI/Lody/blob/v0.109.0/apps/electron/package.json
Locator: dependencies: electron, @electron-toolkit/*, electron-updater
Finding: Desktop client is an Electron app (electron runtime, electron-updater, electron-toolkit preload/utils); no Tauri/native-shell packaging in the pinned tree.
Retrieved: 2026-11-13

## lody:PLAN-01

Finding: Sessions start locally from composer, prompts, schedules or the CLI; GitHub issues/PRs inject context via @ while GitHub stays authoritative for tracker state; session IDs are durable and PR comment sync is two-way.

Verification: agent-cross-checked
Checked: 2026-11-13
Scheduled recheck: 2027-03-13
Plan: Not specified
Surface: Lody Electron desktop app; Lody hosted web app; Lody CLI and daemon
Version: v0.109.0 (commit 2eefb5e); source pass 2026-11-13

Only the cited atomic findings are established. Remaining atomic requirements and the full rubric scenario remain unverified.
No issue import or two-way issue sync; issue edits stay in GitHub.

Source: https://lody.ai/docs/session/
Locator: Composer, fork, side chat, session list, archive/restore/delete, Quick Session, Open in editor
Finding: Sessions bundle conversation, branch and worktree; fork/side-chat reuse history; sidebar shows status, repo, branch, PR and diff stats; archive retains history and reclaims worktrees; restore recreates them; Quick Session desktop shortcut; Open-in launches VS Code/Xcode/Sublime/Zed (external launchers, not extensions).
Retrieved: 2026-11-13

Source: https://lody.ai/docs/agent-collaboration/
Locator: Orchestrator walkthrough: triage, cross-repo fix, review-fix loop, @ mentions
Finding: Primary agent triages PR/issue queues, delegates fixes/reviews to Kimi/Codex/Grok sessions across machines, exchanges findings via @ session mentions, and collects commits; examples are illustrative prompts, not benchmark results.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/scheduled-tasks/
Locator: Triggers, owning machine, agent-proposed schedules, missed runs, FAQ
Finding: Scheduled/manual/one-shot tasks run on one owning machine (CLI, local timezone; nothing runs in cloud); agent can only propose schedules, never create them; missed runs catch up once; only the creator can edit/pause/delete; machine must be awake.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/github/
Locator: GitHub App setup, issue/PR context, PR panel, auto-archive, commit/push, review sync
Finding: GitHub App gives repo access; issues/PRs inject context via @; PR panel shows state/CI/comments/reviews with in-Lody merge and branch delete; review comments sync both ways; PR-linked sessions auto-archive on merge/close; optional act-as-you identity for PR actions.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/concepts/
Locator: Mental model, core objects, Agent Config vs Role, MCP/daemon/permission scope glossary
Finding: Workspace holds members, machines, sessions and settings; session = one task/conversation/branch; Agent Config = runtime plus auth and machine; Lody exposes built-in MCP tools for cross-session work; daemon is the background CLI that runs agents.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/local-project/
Locator: Adding projects, local-first availability, CLI history sync, team visibility, limitations
Finding: Any local directory works with synced chat/diffs/branches/worktrees; desktop works offline with later sync; imports Codex/Claude CLI history; team visibility is opt-in per project; local projects cannot push to remote branches directly.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/diff-comments/
Locator: Threads, resolve, send-to-agent, GitHub sync
Finding: Line-level Markdown threads with reply/edit/delete/resolve; threads can be sent into the chat for the agent to address; PR-linked sessions sync both ways with GitHub PR review comments.
Retrieved: 2026-11-13

Source: https://github.com/LodyAI/Lody/tree/v0.109.0/apps/cli/src/commands
Locator: session.ts, machine.ts, daemon.ts, agent-config.ts, github.ts, review.ts, export.ts, magpie-import.ts, internal.ts
Finding: CLI implements session/machine/daemon/agent-config/GitHub/review/export/magpie commands; no public REST API surface or SDK package in commands, packages or docs.
Retrieved: 2026-11-13

## lody:PLAN-02

Finding: Rounds pair each agent turn with its diff and stay revisable through history, restore and steering; durable cross-session plan objects with acceptance criteria do not exist as product entities.

Verification: agent-cross-checked
Checked: 2026-11-13
Scheduled recheck: 2027-03-13
Plan: Not specified
Surface: Lody Electron desktop app; Lody hosted web app
Version: v0.109.0 (commit 2eefb5e); source pass 2026-11-13

Only the cited atomic findings are established. Remaining atomic requirements and the full rubric scenario remain unverified.
No plan objects, acceptance criteria, or spec gates exist; rounds and prompts carry intent.

Source: https://lody.ai/docs/session/
Locator: Composer, fork, side chat, session list, archive/restore/delete, Quick Session, Open in editor
Finding: Sessions bundle conversation, branch and worktree; fork/side-chat reuse history; sidebar shows status, repo, branch, PR and diff stats; archive retains history and reclaims worktrees; restore recreates them; Quick Session desktop shortcut; Open-in launches VS Code/Xcode/Sublime/Zed (external launchers, not extensions).
Retrieved: 2026-11-13

Source: https://lody.ai/docs/scheduled-tasks/
Locator: Triggers, owning machine, agent-proposed schedules, missed runs, FAQ
Finding: Scheduled/manual/one-shot tasks run on one owning machine (CLI, local timezone; nothing runs in cloud); agent can only propose schedules, never create them; missed runs catch up once; only the creator can edit/pause/delete; machine must be awake.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/github/
Locator: GitHub App setup, issue/PR context, PR panel, auto-archive, commit/push, review sync
Finding: GitHub App gives repo access; issues/PRs inject context via @; PR panel shows state/CI/comments/reviews with in-Lody merge and branch delete; review comments sync both ways; PR-linked sessions auto-archive on merge/close; optional act-as-you identity for PR actions.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/worktrees/
Locator: Worktree layout, setup/cleanup scripts, env vars, retention and recovery
Finding: One branch (session/<id>) and worktree per session under ~/.lody/repos/<repoId>/; project setup/cleanup scripts with LODY_* env vars; archive/backup rules keep branches and stage pending changes, discard ignored files; restore recreates the worktree from the branch.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/acp-feature-support/
Locator: Support matrix, extension capability reference, notes
Finding: Nine built-in providers (Claude Code, Codex, Grok, Kimi Code, Devin, Pi, DeepSeek Harness, Bub, Dimcode) share the ACP baseline; optional capabilities (MCP transports, resume/fork, steering, tasks, subagents, goals, usage, rate limits) differ per adapter via acp-extension-core; declarations are read at session start so updates can shift the matrix.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/diff-viewer/
Locator: Round diffs, line comments, whole-conversation changes, remote review
Finding: Per-round diffs with changed line counts beside the agent message; file/diff tabs; whole-conversation Changes sidebar; remote devices read diffs through the session file provider with explicit loading states.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/diff-comments/
Locator: Threads, resolve, send-to-agent, GitHub sync
Finding: Line-level Markdown threads with reply/edit/delete/resolve; threads can be sent into the chat for the agent to address; PR-linked sessions sync both ways with GitHub PR review comments.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/workflow/
Locator: Small tasks, parallel sessions, AI review loop, archiving
Finding: One conversation per feature/fix (usually one PR); review round diffs; Create PR from the session; AI review loop on PR comments; archive (or auto-archive) when merged; non-GitHub projects skip PR/CI automation.
Retrieved: 2026-11-13

Source: https://github.com/LodyAI/Lody/tree/v0.109.0/apps/cli/src/commands
Locator: session.ts, machine.ts, daemon.ts, agent-config.ts, github.ts, review.ts, export.ts, magpie-import.ts, internal.ts
Finding: CLI implements session/machine/daemon/agent-config/GitHub/review/export/magpie commands; no public REST API surface or SDK package in commands, packages or docs.
Retrieved: 2026-11-13

## lody:PLAN-03

Finding: Parent/child structure exists as forks, side chats, child tabs and delegated conversations with preserved lineage, but no epics, blockers, readiness or enforcement objects exist; scoping guidance is advisory.

Verification: agent-cross-checked
Checked: 2026-11-13
Scheduled recheck: 2027-03-13
Plan: Not specified
Surface: Lody Electron desktop app; Lody hosted web app
Version: v0.109.0 (commit 2eefb5e); source pass 2026-11-13

Only the cited atomic findings are established. Remaining atomic requirements and the full rubric scenario remain unverified.
Hierarchy, dependency and enforcement concepts are agent-prompt conventions, not product objects.

Source: https://lody.ai/docs/session/
Locator: Composer, fork, side chat, session list, archive/restore/delete, Quick Session, Open in editor
Finding: Sessions bundle conversation, branch and worktree; fork/side-chat reuse history; sidebar shows status, repo, branch, PR and diff stats; archive retains history and reclaims worktrees; restore recreates them; Quick Session desktop shortcut; Open-in launches VS Code/Xcode/Sublime/Zed (external launchers, not extensions).
Retrieved: 2026-11-13

Source: https://lody.ai/docs/session-tabs/
Locator: Child chats, file/diff tabs, tab management
Finding: Child chats share the parent session workspace (files/branch/uncommitted changes) with separate histories; file/diff tabs open beside chat; closing a tab does not stop the agent or remove the worktree.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/session-orchestration/
Locator: Built-in Lody MCP tools: create/reuse, status, follow-up, cancel, model/reasoning selection
Finding: Agents use built-in Lody MCP tools to create/reuse conversations, read status and bounded history, send follow-ups, cancel running turns, select compatible model/reasoning, and bring results back; parent relationship preserved; bounded to Lody conversation data, not a background scheduler.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/agent-collaboration/
Locator: Orchestrator walkthrough: triage, cross-repo fix, review-fix loop, @ mentions
Finding: Primary agent triages PR/issue queues, delegates fixes/reviews to Kimi/Codex/Grok sessions across machines, exchanges findings via @ session mentions, and collects commits; examples are illustrative prompts, not benchmark results.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/team/
Locator: Invite, roles, member sessions, token usage by member, machine visibility
Finding: Invite by email with role; owners/admins manage members; All Tasks view with avatars; per-member token usage and trends; machines private by default, explicitly shared per machine; shared docs, mentions and task management are planned, not shipped.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/workflow/
Locator: Small tasks, parallel sessions, AI review loop, archiving
Finding: One conversation per feature/fix (usually one PR); review round diffs; Create PR from the session; AI review loop on PR comments; archive (or auto-archive) when merged; non-GitHub projects skip PR/CI automation.
Retrieved: 2026-11-13

Source: https://github.com/LodyAI/Lody/blob/v0.109.0/apps/cli/src/orchestration/README.md
Locator: Coordinator workflow, inbox, session-create rollback point-of-no-return
Finding: Orchestration layer runs coordinator workflows over sessions with an inbox; session-create has a documented point-of-no-rollback for cleanup only (not user-facing revert); no merge queue, batch-review queue or duplicate-task detection.
Retrieved: 2026-11-13

## lody:PLAN-04

Finding: Repo instruction files, mentionable skills, browsable project files and per-session memory persist; handoff carries context to teammates. Provenance, staleness controls and cross-session memory are not established.

Verification: agent-cross-checked
Checked: 2026-11-13
Scheduled recheck: 2027-03-13
Plan: Not specified
Surface: Lody Electron desktop app; Lody hosted web app; Lody native iOS and Android apps; Lody CLI and daemon
Version: v0.109.0 (commit 2eefb5e); source pass 2026-11-13

Only the cited atomic findings are established. Remaining atomic requirements and the full rubric scenario remain unverified.
No provenance, citation, or stale-context model is documented.

Source: https://lody.ai/docs/session/
Locator: Composer, fork, side chat, session list, archive/restore/delete, Quick Session, Open in editor
Finding: Sessions bundle conversation, branch and worktree; fork/side-chat reuse history; sidebar shows status, repo, branch, PR and diff stats; archive retains history and reclaims worktrees; restore recreates them; Quick Session desktop shortcut; Open-in launches VS Code/Xcode/Sublime/Zed (external launchers, not extensions).
Retrieved: 2026-11-13

Source: https://lody.ai/docs/parallel-agents/
Locator: Isolated worktrees, mixed agents, team visibility, coordinator handoff, FAQ
Finding: Multiple sessions each with own worktree/branch; mix Claude Code/Codex/Kimi/Grok per session; team sees running sessions via All Tasks; concurrency limited by host machine capacity; agent-to-agent coordination via Agent Session Control.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/session-handoff/
Locator: Handoff steps, permissions table, live handoff vs share link, FAQ
Finding: Teammate joins the same live session (conversation, diffs, worktree) after workspace invite plus machine/project sharing; sharing may widen visibility to other conversations on that machine; transcript/markdown copy is a separate record-only action.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/mobile/
Locator: Install, Live Activities, push notifications, progress/diff monitoring, offline support
Finding: Native iOS (App Store + TestFlight) and Android apps: notifications on task completion/approval/PR-ready, iOS Live Activities incl. actionable permission alerts, diff review and approvals, project file browsing; realtime editing is desktop-only; offline viewing of cached conversations with sync on reconnect.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/github/
Locator: GitHub App setup, issue/PR context, PR panel, auto-archive, commit/push, review sync
Finding: GitHub App gives repo access; issues/PRs inject context via @; PR panel shows state/CI/comments/reviews with in-Lody merge and branch delete; review comments sync both ways; PR-linked sessions auto-archive on merge/close; optional act-as-you identity for PR actions.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/agent-roles/
Locator: Role creation, sharing, mentions, offline-machine behavior
Finding: Roles package machine, agent config, model, reasoning, permission and instruction; private until shared with workspace; mentionable via @ to start new conversations; bound to one machine/config and unusable while offline.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/from-codex-claude-code/
Locator: What stays the same, concept mapping, migration checklist, FAQ
Finding: Lody launches the same provider CLIs and reuses machine-side subscription logins, API env config, and repo instruction files (AGENTS.md/CLAUDE.md); sessions resume like --resume; CLI remains supported for quick one-off edits.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/concepts/
Locator: Mental model, core objects, Agent Config vs Role, MCP/daemon/permission scope glossary
Finding: Workspace holds members, machines, sessions and settings; session = one task/conversation/branch; Agent Config = runtime plus auth and machine; Lody exposes built-in MCP tools for cross-session work; daemon is the background CLI that runs agents.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/local-project/
Locator: Adding projects, local-first availability, CLI history sync, team visibility, limitations
Finding: Any local directory works with synced chat/diffs/branches/worktrees; desktop works offline with later sync; imports Codex/Claude CLI history; team visibility is opt-in per project; local projects cannot push to remote branches directly.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/diff-viewer/
Locator: Round diffs, line comments, whole-conversation changes, remote review
Finding: Per-round diffs with changed line counts beside the agent message; file/diff tabs; whole-conversation Changes sidebar; remote devices read diffs through the session file provider with explicit loading states.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/diff-comments/
Locator: Threads, resolve, send-to-agent, GitHub sync
Finding: Line-level Markdown threads with reply/edit/delete/resolve; threads can be sent into the chat for the agent to address; PR-linked sessions sync both ways with GitHub PR review comments.
Retrieved: 2026-11-13

Source: https://github.com/LodyAI/Lody/tree/v0.109.0/apps/cli/src/commands
Locator: session.ts, machine.ts, daemon.ts, agent-config.ts, github.ts, review.ts, export.ts, magpie-import.ts, internal.ts
Finding: CLI implements session/machine/daemon/agent-config/GitHub/review/export/magpie commands; no public REST API surface or SDK package in commands, packages or docs.
Retrieved: 2026-11-13

## lody:PLAN-05

Finding: In-UI text search, a session browser panel, and image/file multimodal inputs are product features; indexing, retrieval grounding and review-time enforcement belong to the underlying runtimes, not Lody.

Verification: agent-cross-checked
Checked: 2026-11-13
Scheduled recheck: 2027-03-13
Plan: Not specified
Surface: Lody Electron desktop app; Lody hosted web app
Version: v0.109.0 (commit 2eefb5e); source pass 2026-11-13

Only the cited atomic findings are established. Remaining atomic requirements and the full rubric scenario remain unverified.
No product code index, citation model, or review gate is documented.

Source: https://lody.ai/docs/session/
Locator: Composer, fork, side chat, session list, archive/restore/delete, Quick Session, Open in editor
Finding: Sessions bundle conversation, branch and worktree; fork/side-chat reuse history; sidebar shows status, repo, branch, PR and diff stats; archive retains history and reclaims worktrees; restore recreates them; Quick Session desktop shortcut; Open-in launches VS Code/Xcode/Sublime/Zed (external launchers, not extensions).
Retrieved: 2026-11-13

Source: https://lody.ai/docs/session-handoff/
Locator: Handoff steps, permissions table, live handoff vs share link, FAQ
Finding: Teammate joins the same live session (conversation, diffs, worktree) after workspace invite plus machine/project sharing; sharing may widen visibility to other conversations on that machine; transcript/markdown copy is a separate record-only action.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/mobile/
Locator: Install, Live Activities, push notifications, progress/diff monitoring, offline support
Finding: Native iOS (App Store + TestFlight) and Android apps: notifications on task completion/approval/PR-ready, iOS Live Activities incl. actionable permission alerts, diff review and approvals, project file browsing; realtime editing is desktop-only; offline viewing of cached conversations with sync on reconnect.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/github/
Locator: GitHub App setup, issue/PR context, PR panel, auto-archive, commit/push, review sync
Finding: GitHub App gives repo access; issues/PRs inject context via @; PR panel shows state/CI/comments/reviews with in-Lody merge and branch delete; review comments sync both ways; PR-linked sessions auto-archive on merge/close; optional act-as-you identity for PR actions.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/acp-feature-support/
Locator: Support matrix, extension capability reference, notes
Finding: Nine built-in providers (Claude Code, Codex, Grok, Kimi Code, Devin, Pi, DeepSeek Harness, Bub, Dimcode) share the ACP baseline; optional capabilities (MCP transports, resume/fork, steering, tasks, subagents, goals, usage, rate limits) differ per adapter via acp-extension-core; declarations are read at session start so updates can shift the matrix.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/local-project/
Locator: Adding projects, local-first availability, CLI history sync, team visibility, limitations
Finding: Any local directory works with synced chat/diffs/branches/worktrees; desktop works offline with later sync; imports Codex/Claude CLI history; team visibility is opt-in per project; local projects cannot push to remote branches directly.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/diff-viewer/
Locator: Round diffs, line comments, whole-conversation changes, remote review
Finding: Per-round diffs with changed line counts beside the agent message; file/diff tabs; whole-conversation Changes sidebar; remote devices read diffs through the session file provider with explicit loading states.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/diff-comments/
Locator: Threads, resolve, send-to-agent, GitHub sync
Finding: Line-level Markdown threads with reply/edit/delete/resolve; threads can be sent into the chat for the agent to address; PR-linked sessions sync both ways with GitHub PR review comments.
Retrieved: 2026-11-13

Source: https://github.com/LodyAI/Lody/tree/v0.109.0/apps/cli/src/commands
Locator: session.ts, machine.ts, daemon.ts, agent-config.ts, github.ts, review.ts, export.ts, magpie-import.ts, internal.ts
Finding: CLI implements session/machine/daemon/agent-config/GitHub/review/export/magpie commands; no public REST API surface or SDK package in commands, packages or docs.
Retrieved: 2026-11-13

## lody:PLAN-06

Finding: Sessions act as durable tasks with archive/restore, search, metadata and PR linkage, dispatchable on send or schedule, without requiring GitHub. Prioritization, labels, assignment, filtering and idea parking do not exist as product features.

Verification: agent-cross-checked
Checked: 2026-11-13
Scheduled recheck: 2027-03-13
Plan: Not specified
Surface: Lody Electron desktop app; Lody hosted web app
Version: v0.109.0 (commit 2eefb5e); source pass 2026-11-13

Only the cited atomic findings are established. Remaining atomic requirements and the full rubric scenario remain unverified.
No issue tracker semantics: prioritize, label, assign and filter are absent and task management is planned.

Source: https://lody.ai/docs/session/
Locator: Composer, fork, side chat, session list, archive/restore/delete, Quick Session, Open in editor
Finding: Sessions bundle conversation, branch and worktree; fork/side-chat reuse history; sidebar shows status, repo, branch, PR and diff stats; archive retains history and reclaims worktrees; restore recreates them; Quick Session desktop shortcut; Open-in launches VS Code/Xcode/Sublime/Zed (external launchers, not extensions).
Retrieved: 2026-11-13

Source: https://lody.ai/docs/session-tabs/
Locator: Child chats, file/diff tabs, tab management
Finding: Child chats share the parent session workspace (files/branch/uncommitted changes) with separate histories; file/diff tabs open beside chat; closing a tab does not stop the agent or remove the worktree.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/session-handoff/
Locator: Handoff steps, permissions table, live handoff vs share link, FAQ
Finding: Teammate joins the same live session (conversation, diffs, worktree) after workspace invite plus machine/project sharing; sharing may widen visibility to other conversations on that machine; transcript/markdown copy is a separate record-only action.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/team/
Locator: Invite, roles, member sessions, token usage by member, machine visibility
Finding: Invite by email with role; owners/admins manage members; All Tasks view with avatars; per-member token usage and trends; machines private by default, explicitly shared per machine; shared docs, mentions and task management are planned, not shipped.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/scheduled-tasks/
Locator: Triggers, owning machine, agent-proposed schedules, missed runs, FAQ
Finding: Scheduled/manual/one-shot tasks run on one owning machine (CLI, local timezone; nothing runs in cloud); agent can only propose schedules, never create them; missed runs catch up once; only the creator can edit/pause/delete; machine must be awake.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/github/
Locator: GitHub App setup, issue/PR context, PR panel, auto-archive, commit/push, review sync
Finding: GitHub App gives repo access; issues/PRs inject context via @; PR panel shows state/CI/comments/reviews with in-Lody merge and branch delete; review comments sync both ways; PR-linked sessions auto-archive on merge/close; optional act-as-you identity for PR actions.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/worktrees/
Locator: Worktree layout, setup/cleanup scripts, env vars, retention and recovery
Finding: One branch (session/<id>) and worktree per session under ~/.lody/repos/<repoId>/; project setup/cleanup scripts with LODY_* env vars; archive/backup rules keep branches and stage pending changes, discard ignored files; restore recreates the worktree from the branch.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/local-project/
Locator: Adding projects, local-first availability, CLI history sync, team visibility, limitations
Finding: Any local directory works with synced chat/diffs/branches/worktrees; desktop works offline with later sync; imports Codex/Claude CLI history; team visibility is opt-in per project; local projects cannot push to remote branches directly.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/diff-comments/
Locator: Threads, resolve, send-to-agent, GitHub sync
Finding: Line-level Markdown threads with reply/edit/delete/resolve; threads can be sent into the chat for the agent to address; PR-linked sessions sync both ways with GitHub PR review comments.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/first-session/
Locator: Walkthrough, stop control, archive, FAQ (no GitHub needed)
Finding: First session works on a plain local directory without GitHub; stop control cancels the active turn; archived sessions keep branch and conversation and are restorable.
Retrieved: 2026-11-13

Source: https://github.com/LodyAI/Lody/blob/v0.109.0/apps/cli/src/orchestration/README.md
Locator: Coordinator workflow, inbox, session-create rollback point-of-no-return
Finding: Orchestration layer runs coordinator workflows over sessions with an inbox; session-create has a documented point-of-no-rollback for cleanup only (not user-facing revert); no merge queue, batch-review queue or duplicate-task detection.
Retrieved: 2026-11-13

## lody:PLAN-07

Finding: Agents operate on the same durable session IDs humans use — creating, reading, messaging, cancelling and spawning child conversations with results returned and human-visible attribution — gated by workspace and machine sharing. Claims, dependencies and conflict handling are not product concepts.

Verification: agent-cross-checked
Checked: 2026-11-13
Scheduled recheck: 2027-03-13
Plan: Not specified
Surface: Lody Electron desktop app; Lody CLI and daemon
Version: v0.109.0 (commit 2eefb5e); source pass 2026-11-13

Only the cited atomic findings are established. Remaining atomic requirements and the full rubric scenario remain unverified.
No claim, dependency, or conflict-resolution semantics exist for agents.

Source: https://lody.ai/docs/session/
Locator: Composer, fork, side chat, session list, archive/restore/delete, Quick Session, Open in editor
Finding: Sessions bundle conversation, branch and worktree; fork/side-chat reuse history; sidebar shows status, repo, branch, PR and diff stats; archive retains history and reclaims worktrees; restore recreates them; Quick Session desktop shortcut; Open-in launches VS Code/Xcode/Sublime/Zed (external launchers, not extensions).
Retrieved: 2026-11-13

Source: https://lody.ai/docs/parallel-agents/
Locator: Isolated worktrees, mixed agents, team visibility, coordinator handoff, FAQ
Finding: Multiple sessions each with own worktree/branch; mix Claude Code/Codex/Kimi/Grok per session; team sees running sessions via All Tasks; concurrency limited by host machine capacity; agent-to-agent coordination via Agent Session Control.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/session-orchestration/
Locator: Built-in Lody MCP tools: create/reuse, status, follow-up, cancel, model/reasoning selection
Finding: Agents use built-in Lody MCP tools to create/reuse conversations, read status and bounded history, send follow-ups, cancel running turns, select compatible model/reasoning, and bring results back; parent relationship preserved; bounded to Lody conversation data, not a background scheduler.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/agent-collaboration/
Locator: Orchestrator walkthrough: triage, cross-repo fix, review-fix loop, @ mentions
Finding: Primary agent triages PR/issue queues, delegates fixes/reviews to Kimi/Codex/Grok sessions across machines, exchanges findings via @ session mentions, and collects commits; examples are illustrative prompts, not benchmark results.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/session-handoff/
Locator: Handoff steps, permissions table, live handoff vs share link, FAQ
Finding: Teammate joins the same live session (conversation, diffs, worktree) after workspace invite plus machine/project sharing; sharing may widen visibility to other conversations on that machine; transcript/markdown copy is a separate record-only action.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/team/
Locator: Invite, roles, member sessions, token usage by member, machine visibility
Finding: Invite by email with role; owners/admins manage members; All Tasks view with avatars; per-member token usage and trends; machines private by default, explicitly shared per machine; shared docs, mentions and task management are planned, not shipped.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/github/
Locator: GitHub App setup, issue/PR context, PR panel, auto-archive, commit/push, review sync
Finding: GitHub App gives repo access; issues/PRs inject context via @; PR panel shows state/CI/comments/reviews with in-Lody merge and branch delete; review comments sync both ways; PR-linked sessions auto-archive on merge/close; optional act-as-you identity for PR actions.
Retrieved: 2026-11-13

Source: https://github.com/LodyAI/Lody/tree/v0.109.0/apps/cli/src/mcp
Locator: lody-mcp-server.ts (@modelcontextprotocol/server), lody-mcp-http-server.ts, session-mcp-resolver.ts, schedule-tools.ts, agent-role-tools.ts, authentication/
Finding: Lody hosts its own MCP server (session/daemon/schedule/role tools over stdio and HTTP loopback) for agents, and resolves the workspace MCP catalog plus OAuth/keychain credentials into ACP sessions as an MCP client.
Retrieved: 2026-11-13

Source: https://github.com/LodyAI/Lody/blob/v0.109.0/apps/cli/src/orchestration/README.md
Locator: Coordinator workflow, inbox, session-create rollback point-of-no-return
Finding: Orchestration layer runs coordinator workflows over sessions with an inbox; session-create has a documented point-of-no-rollback for cleanup only (not user-facing revert); no merge queue, batch-review queue or duplicate-task detection.
Retrieved: 2026-11-13

Source: https://github.com/LodyAI/Lody/blob/v0.109.0/apps/cli/README.md
Locator: authorizeExecution, owner/admin/member device grants, journal reset
Finding: Encrypted workspaces authorize execution per workspace/device with owner/admin/member grants, sub-15-minute memory-only grants, and offline journal reset; UI account IDs grant nothing; guest/recovery/removed/revoked devices do not qualify.
Retrieved: 2026-11-13

## lody:PLAN-08

Finding: No living product specifications exist: documents and document sandboxes are explicitly planned for the future, and shared docs remain on the planned team-features list.

Verification: agent-cross-checked
Checked: 2026-11-13
Scheduled recheck: 2027-03-13
Plan: Not specified
Surface: Lody Electron desktop app; Lody hosted web app
Version: v0.109.0 (commit 2eefb5e); source pass 2026-11-13



Source: https://lody.ai/docs/team/
Locator: Invite, roles, member sessions, token usage by member, machine visibility
Finding: Invite by email with role; owners/admins manage members; All Tasks view with avatars; per-member token usage and trends; machines private by default, explicitly shared per machine; shared docs, mentions and task management are planned, not shipped.
Retrieved: 2026-11-13

Source: https://github.com/LodyAI/Lody/blob/v0.109.0/README.md
Locator: Share conversations, bring agents/machines, daemon, CLI, agent coordination, E2E, mobile credit
Finding: Shared workspace for coding agents teams already use; daemon connects machines; CLI manages sessions; agents coordinate via session tools; parallel worktrees and live diff review; local-first direction via Loro/Flock; mobile clients native with upstream credit.
Retrieved: 2026-11-13

## lody:COORD-01

Finding: Independent sessions run concurrently in isolated worktrees with team-visible statuses; workspace session caps and host-machine capacity bound scale. No hands-on concurrency run was performed.

Verification: agent-cross-checked
Checked: 2026-11-13
Scheduled recheck: 2027-03-13
Plan: Not specified
Surface: Lody Electron desktop app; Lody hosted web app; Lody native iOS and Android apps; Lody CLI and daemon
Version: v0.109.0 (commit 2eefb5e); source pass 2026-11-13

Only the cited atomic findings are established. Remaining atomic requirements and the full rubric scenario remain unverified.
Observed concurrency was not tested; quotas are plan caps plus host capacity.

Source: https://lody.ai/price/
Locator: Plan cards, feature table, FAQ (tokens, seats, cancellation)
Finding: Free ($0 forever: 2 workspaces, 200 sessions/workspace, 30 turns/session, 3 members) vs Plus ($8/seat/month billed yearly, unlimited) vs Enterprise (custom; SSO, procurement, rollout). No AI token charges; BYO agent accounts at zero markup. Prices USD; yearly upfront per seat for 12 months.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/session/
Locator: Composer, fork, side chat, session list, archive/restore/delete, Quick Session, Open in editor
Finding: Sessions bundle conversation, branch and worktree; fork/side-chat reuse history; sidebar shows status, repo, branch, PR and diff stats; archive retains history and reclaims worktrees; restore recreates them; Quick Session desktop shortcut; Open-in launches VS Code/Xcode/Sublime/Zed (external launchers, not extensions).
Retrieved: 2026-11-13

Source: https://lody.ai/docs/parallel-agents/
Locator: Isolated worktrees, mixed agents, team visibility, coordinator handoff, FAQ
Finding: Multiple sessions each with own worktree/branch; mix Claude Code/Codex/Kimi/Grok per session; team sees running sessions via All Tasks; concurrency limited by host machine capacity; agent-to-agent coordination via Agent Session Control.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/team/
Locator: Invite, roles, member sessions, token usage by member, machine visibility
Finding: Invite by email with role; owners/admins manage members; All Tasks view with avatars; per-member token usage and trends; machines private by default, explicitly shared per machine; shared docs, mentions and task management are planned, not shipped.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/mobile/
Locator: Install, Live Activities, push notifications, progress/diff monitoring, offline support
Finding: Native iOS (App Store + TestFlight) and Android apps: notifications on task completion/approval/PR-ready, iOS Live Activities incl. actionable permission alerts, diff review and approvals, project file browsing; realtime editing is desktop-only; offline viewing of cached conversations with sync on reconnect.
Retrieved: 2026-11-13

## lody:COORD-02

Finding: Humans join via membership and handoff; agents receive work through composer selection, saved roles and delegation prompts without locks or queues. Machine sharing gates who can run where.

Verification: agent-cross-checked
Checked: 2026-11-13
Scheduled recheck: 2027-03-13
Plan: Not specified
Surface: Lody Electron desktop app; Lody hosted web app; Lody CLI and daemon
Version: v0.109.0 (commit 2eefb5e); source pass 2026-11-13

Only the cited atomic findings are established. Remaining atomic requirements and the full rubric scenario remain unverified.
No claims, work queues, or exclusive-ownership locks exist.

Source: https://lody.ai/docs/parallel-agents/
Locator: Isolated worktrees, mixed agents, team visibility, coordinator handoff, FAQ
Finding: Multiple sessions each with own worktree/branch; mix Claude Code/Codex/Kimi/Grok per session; team sees running sessions via All Tasks; concurrency limited by host machine capacity; agent-to-agent coordination via Agent Session Control.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/agent-collaboration/
Locator: Orchestrator walkthrough: triage, cross-repo fix, review-fix loop, @ mentions
Finding: Primary agent triages PR/issue queues, delegates fixes/reviews to Kimi/Codex/Grok sessions across machines, exchanges findings via @ session mentions, and collects commits; examples are illustrative prompts, not benchmark results.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/session-handoff/
Locator: Handoff steps, permissions table, live handoff vs share link, FAQ
Finding: Teammate joins the same live session (conversation, diffs, worktree) after workspace invite plus machine/project sharing; sharing may widen visibility to other conversations on that machine; transcript/markdown copy is a separate record-only action.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/team/
Locator: Invite, roles, member sessions, token usage by member, machine visibility
Finding: Invite by email with role; owners/admins manage members; All Tasks view with avatars; per-member token usage and trends; machines private by default, explicitly shared per machine; shared docs, mentions and task management are planned, not shipped.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/scheduled-tasks/
Locator: Triggers, owning machine, agent-proposed schedules, missed runs, FAQ
Finding: Scheduled/manual/one-shot tasks run on one owning machine (CLI, local timezone; nothing runs in cloud); agent can only propose schedules, never create them; missed runs catch up once; only the creator can edit/pause/delete; machine must be awake.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/worktrees/
Locator: Worktree layout, setup/cleanup scripts, env vars, retention and recovery
Finding: One branch (session/<id>) and worktree per session under ~/.lody/repos/<repoId>/; project setup/cleanup scripts with LODY_* env vars; archive/backup rules keep branches and stage pending changes, discard ignored files; restore recreates the worktree from the branch.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/agent-roles/
Locator: Role creation, sharing, mentions, offline-machine behavior
Finding: Roles package machine, agent config, model, reasoning, permission and instruction; private until shared with workspace; mentionable via @ to start new conversations; bound to one machine/config and unusable while offline.
Retrieved: 2026-11-13

Source: https://github.com/LodyAI/Lody/blob/v0.109.0/apps/cli/src/orchestration/README.md
Locator: Coordinator workflow, inbox, session-create rollback point-of-no-return
Finding: Orchestration layer runs coordinator workflows over sessions with an inbox; session-create has a documented point-of-no-rollback for cleanup only (not user-facing revert); no merge queue, batch-review queue or duplicate-task detection.
Retrieved: 2026-11-13

## lody:COORD-03

Finding: A product-owned MCP layer lets any session act as coordinator: create, message, steer and cancel other sessions across machines and harnesses with retained relationships and visible progress. Provider-native subagents surface through declared extension capabilities.

Verification: agent-cross-checked
Checked: 2026-11-13
Scheduled recheck: 2027-03-13
Plan: Not specified
Surface: Lody Electron desktop app; Lody hosted web app; Lody CLI and daemon
Version: v0.109.0 (commit 2eefb5e); source pass 2026-11-13

Only the cited atomic findings are established. Remaining atomic requirements and the full rubric scenario remain unverified.
Delegation is prompt-driven; no prebuilt pipeline or approval gate wraps it.

Source: https://lody.ai/docs/cli/
Locator: Command reference: login, daemon, workspaces, sessions, machines, agent configs, review, export
Finding: lody CLI is both the daemon runtime (lody start / daemon start) and a one-shot manager: session create/chat/list/status, project/workspace/machine/agent-config commands, lody review prompting and rendering, lody export, import-magpie, --json output; built-in help is the flag source of truth.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/session/
Locator: Composer, fork, side chat, session list, archive/restore/delete, Quick Session, Open in editor
Finding: Sessions bundle conversation, branch and worktree; fork/side-chat reuse history; sidebar shows status, repo, branch, PR and diff stats; archive retains history and reclaims worktrees; restore recreates them; Quick Session desktop shortcut; Open-in launches VS Code/Xcode/Sublime/Zed (external launchers, not extensions).
Retrieved: 2026-11-13

Source: https://lody.ai/docs/parallel-agents/
Locator: Isolated worktrees, mixed agents, team visibility, coordinator handoff, FAQ
Finding: Multiple sessions each with own worktree/branch; mix Claude Code/Codex/Kimi/Grok per session; team sees running sessions via All Tasks; concurrency limited by host machine capacity; agent-to-agent coordination via Agent Session Control.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/session-orchestration/
Locator: Built-in Lody MCP tools: create/reuse, status, follow-up, cancel, model/reasoning selection
Finding: Agents use built-in Lody MCP tools to create/reuse conversations, read status and bounded history, send follow-ups, cancel running turns, select compatible model/reasoning, and bring results back; parent relationship preserved; bounded to Lody conversation data, not a background scheduler.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/agent-collaboration/
Locator: Orchestrator walkthrough: triage, cross-repo fix, review-fix loop, @ mentions
Finding: Primary agent triages PR/issue queues, delegates fixes/reviews to Kimi/Codex/Grok sessions across machines, exchanges findings via @ session mentions, and collects commits; examples are illustrative prompts, not benchmark results.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/session-handoff/
Locator: Handoff steps, permissions table, live handoff vs share link, FAQ
Finding: Teammate joins the same live session (conversation, diffs, worktree) after workspace invite plus machine/project sharing; sharing may widen visibility to other conversations on that machine; transcript/markdown copy is a separate record-only action.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/scheduled-tasks/
Locator: Triggers, owning machine, agent-proposed schedules, missed runs, FAQ
Finding: Scheduled/manual/one-shot tasks run on one owning machine (CLI, local timezone; nothing runs in cloud); agent can only propose schedules, never create them; missed runs catch up once; only the creator can edit/pause/delete; machine must be awake.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/acp-feature-support/
Locator: Support matrix, extension capability reference, notes
Finding: Nine built-in providers (Claude Code, Codex, Grok, Kimi Code, Devin, Pi, DeepSeek Harness, Bub, Dimcode) share the ACP baseline; optional capabilities (MCP transports, resume/fork, steering, tasks, subagents, goals, usage, rate limits) differ per adapter via acp-extension-core; declarations are read at session start so updates can shift the matrix.
Retrieved: 2026-11-13

Source: https://github.com/LodyAI/Lody/tree/v0.109.0/apps/cli/src/mcp
Locator: lody-mcp-server.ts (@modelcontextprotocol/server), lody-mcp-http-server.ts, session-mcp-resolver.ts, schedule-tools.ts, agent-role-tools.ts, authentication/
Finding: Lody hosts its own MCP server (session/daemon/schedule/role tools over stdio and HTTP loopback) for agents, and resolves the workspace MCP catalog plus OAuth/keychain credentials into ACP sessions as an MCP client.
Retrieved: 2026-11-13

## lody:COORD-04

Finding: Schedules, manual tasks and one-shot sends run on an owning machine with serialized overlap handling and single catch-up; agents may propose but never create schedules. PR merge/close events drive auto-archive; no generic event triggers exist.

Verification: agent-cross-checked
Checked: 2026-11-13
Scheduled recheck: 2027-03-13
Plan: Not specified
Surface: Lody Electron desktop app; Lody hosted web app; Lody native iOS and Android apps; Lody CLI and daemon
Version: v0.109.0 (commit 2eefb5e); source pass 2026-11-13

Only the cited atomic findings are established. Remaining atomic requirements and the full rubric scenario remain unverified.
Execution depends on the owning machine being awake; closing the requesting client is fine, closing the owner is not.

Source: https://lody.ai/docs/parallel-agents/
Locator: Isolated worktrees, mixed agents, team visibility, coordinator handoff, FAQ
Finding: Multiple sessions each with own worktree/branch; mix Claude Code/Codex/Kimi/Grok per session; team sees running sessions via All Tasks; concurrency limited by host machine capacity; agent-to-agent coordination via Agent Session Control.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/session-orchestration/
Locator: Built-in Lody MCP tools: create/reuse, status, follow-up, cancel, model/reasoning selection
Finding: Agents use built-in Lody MCP tools to create/reuse conversations, read status and bounded history, send follow-ups, cancel running turns, select compatible model/reasoning, and bring results back; parent relationship preserved; bounded to Lody conversation data, not a background scheduler.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/agent-collaboration/
Locator: Orchestrator walkthrough: triage, cross-repo fix, review-fix loop, @ mentions
Finding: Primary agent triages PR/issue queues, delegates fixes/reviews to Kimi/Codex/Grok sessions across machines, exchanges findings via @ session mentions, and collects commits; examples are illustrative prompts, not benchmark results.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/scheduled-tasks/
Locator: Triggers, owning machine, agent-proposed schedules, missed runs, FAQ
Finding: Scheduled/manual/one-shot tasks run on one owning machine (CLI, local timezone; nothing runs in cloud); agent can only propose schedules, never create them; missed runs catch up once; only the creator can edit/pause/delete; machine must be awake.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/github/
Locator: GitHub App setup, issue/PR context, PR panel, auto-archive, commit/push, review sync
Finding: GitHub App gives repo access; issues/PRs inject context via @; PR panel shows state/CI/comments/reviews with in-Lody merge and branch delete; review comments sync both ways; PR-linked sessions auto-archive on merge/close; optional act-as-you identity for PR actions.
Retrieved: 2026-11-13

## lody:COORD-05

Finding: Stop, resume, steering, actionable permission prompts and best-effort notifications span desktop, mobile, web and CLI with retained history. Session-level pause and escalation paths are not established.

Verification: agent-cross-checked
Checked: 2026-11-13
Scheduled recheck: 2027-03-13
Plan: Not specified
Surface: Lody Electron desktop app; Lody hosted web app; Lody native iOS and Android apps; Lody CLI and daemon
Version: v0.109.0 (commit 2eefb5e); source pass 2026-11-13

Only the cited atomic findings are established. Remaining atomic requirements and the full rubric scenario remain unverified.
Delivery is best-effort with no outbox or exactly-once guarantee; escalation is undocumented.

Source: https://lody.ai/docs/cli/
Locator: Command reference: login, daemon, workspaces, sessions, machines, agent configs, review, export
Finding: lody CLI is both the daemon runtime (lody start / daemon start) and a one-shot manager: session create/chat/list/status, project/workspace/machine/agent-config commands, lody review prompting and rendering, lody export, import-magpie, --json output; built-in help is the flag source of truth.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/session/
Locator: Composer, fork, side chat, session list, archive/restore/delete, Quick Session, Open in editor
Finding: Sessions bundle conversation, branch and worktree; fork/side-chat reuse history; sidebar shows status, repo, branch, PR and diff stats; archive retains history and reclaims worktrees; restore recreates them; Quick Session desktop shortcut; Open-in launches VS Code/Xcode/Sublime/Zed (external launchers, not extensions).
Retrieved: 2026-11-13

Source: https://lody.ai/docs/session-orchestration/
Locator: Built-in Lody MCP tools: create/reuse, status, follow-up, cancel, model/reasoning selection
Finding: Agents use built-in Lody MCP tools to create/reuse conversations, read status and bounded history, send follow-ups, cancel running turns, select compatible model/reasoning, and bring results back; parent relationship preserved; bounded to Lody conversation data, not a background scheduler.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/mobile/
Locator: Install, Live Activities, push notifications, progress/diff monitoring, offline support
Finding: Native iOS (App Store + TestFlight) and Android apps: notifications on task completion/approval/PR-ready, iOS Live Activities incl. actionable permission alerts, diff review and approvals, project file browsing; realtime editing is desktop-only; offline viewing of cached conversations with sync on reconnect.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/scheduled-tasks/
Locator: Triggers, owning machine, agent-proposed schedules, missed runs, FAQ
Finding: Scheduled/manual/one-shot tasks run on one owning machine (CLI, local timezone; nothing runs in cloud); agent can only propose schedules, never create them; missed runs catch up once; only the creator can edit/pause/delete; machine must be awake.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/github/
Locator: GitHub App setup, issue/PR context, PR panel, auto-archive, commit/push, review sync
Finding: GitHub App gives repo access; issues/PRs inject context via @; PR panel shows state/CI/comments/reviews with in-Lody merge and branch delete; review comments sync both ways; PR-linked sessions auto-archive on merge/close; optional act-as-you identity for PR actions.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/acp-feature-support/
Locator: Support matrix, extension capability reference, notes
Finding: Nine built-in providers (Claude Code, Codex, Grok, Kimi Code, Devin, Pi, DeepSeek Harness, Bub, Dimcode) share the ACP baseline; optional capabilities (MCP transports, resume/fork, steering, tasks, subagents, goals, usage, rate limits) differ per adapter via acp-extension-core; declarations are read at session start so updates can shift the matrix.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/local-project/
Locator: Adding projects, local-first availability, CLI history sync, team visibility, limitations
Finding: Any local directory works with synced chat/diffs/branches/worktrees; desktop works offline with later sync; imports Codex/Claude CLI history; team visibility is opt-in per project; local projects cannot push to remote branches directly.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/first-session/
Locator: Walkthrough, stop control, archive, FAQ (no GitHub needed)
Finding: First session works on a plain local directory without GitHub; stop control cancels the active turn; archived sessions keep branch and conversation and are restorable.
Retrieved: 2026-11-13

Source: https://github.com/LodyAI/Lody/blob/v0.109.0/apps/cli/src/lib/notifications/AGENTS.md
Locator: Turn/outcome notification pipeline, mobile/cloud ports, best-effort delivery
Finding: Turn outcomes project into control documents and mobile push via the cloud port with best-effort delivery (no outbox, retry, reconnect replay or exactly-once); permission push and Live Activity sync are separate paths.
Retrieved: 2026-11-13

## lody:COORD-06

Finding: The home session list with statuses, PR states, diff stats and filters is the fleet view, backed by attention signals and retained history. Dependencies, workload planning and error/fixture chrome are not established.

Verification: agent-cross-checked
Checked: 2026-11-13
Scheduled recheck: 2027-03-13
Plan: Not specified
Surface: Lody Electron desktop app; Lody hosted web app; Lody native iOS and Android apps
Version: v0.109.0 (commit 2eefb5e); source pass 2026-11-13

Only the cited atomic findings are established. Remaining atomic requirements and the full rubric scenario remain unverified.
No dependency graph, workload planner, or documented navigation/fixture semantics.

Source: https://lody.ai/docs/session/
Locator: Composer, fork, side chat, session list, archive/restore/delete, Quick Session, Open in editor
Finding: Sessions bundle conversation, branch and worktree; fork/side-chat reuse history; sidebar shows status, repo, branch, PR and diff stats; archive retains history and reclaims worktrees; restore recreates them; Quick Session desktop shortcut; Open-in launches VS Code/Xcode/Sublime/Zed (external launchers, not extensions).
Retrieved: 2026-11-13

Source: https://lody.ai/docs/session-tabs/
Locator: Child chats, file/diff tabs, tab management
Finding: Child chats share the parent session workspace (files/branch/uncommitted changes) with separate histories; file/diff tabs open beside chat; closing a tab does not stop the agent or remove the worktree.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/parallel-agents/
Locator: Isolated worktrees, mixed agents, team visibility, coordinator handoff, FAQ
Finding: Multiple sessions each with own worktree/branch; mix Claude Code/Codex/Kimi/Grok per session; team sees running sessions via All Tasks; concurrency limited by host machine capacity; agent-to-agent coordination via Agent Session Control.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/agent-collaboration/
Locator: Orchestrator walkthrough: triage, cross-repo fix, review-fix loop, @ mentions
Finding: Primary agent triages PR/issue queues, delegates fixes/reviews to Kimi/Codex/Grok sessions across machines, exchanges findings via @ session mentions, and collects commits; examples are illustrative prompts, not benchmark results.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/team/
Locator: Invite, roles, member sessions, token usage by member, machine visibility
Finding: Invite by email with role; owners/admins manage members; All Tasks view with avatars; per-member token usage and trends; machines private by default, explicitly shared per machine; shared docs, mentions and task management are planned, not shipped.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/mobile/
Locator: Install, Live Activities, push notifications, progress/diff monitoring, offline support
Finding: Native iOS (App Store + TestFlight) and Android apps: notifications on task completion/approval/PR-ready, iOS Live Activities incl. actionable permission alerts, diff review and approvals, project file browsing; realtime editing is desktop-only; offline viewing of cached conversations with sync on reconnect.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/github/
Locator: GitHub App setup, issue/PR context, PR panel, auto-archive, commit/push, review sync
Finding: GitHub App gives repo access; issues/PRs inject context via @; PR panel shows state/CI/comments/reviews with in-Lody merge and branch delete; review comments sync both ways; PR-linked sessions auto-archive on merge/close; optional act-as-you identity for PR actions.
Retrieved: 2026-11-13

Source: https://github.com/LodyAI/Lody/blob/v0.109.0/apps/cli/src/orchestration/README.md
Locator: Coordinator workflow, inbox, session-create rollback point-of-no-return
Finding: Orchestration layer runs coordinator workflows over sessions with an inbox; session-create has a documented point-of-no-rollback for cleanup only (not user-facing revert); no merge queue, batch-review queue or duplicate-task detection.
Retrieved: 2026-11-13

## lody:COORD-07

Finding: Roles, natural-language configuration, per-agent model/effort controls and retained delegation lineage make execution visible and reconfigurable without mandatory presets. Mid-run model changes and auth friction details are only partly established.

Verification: agent-cross-checked
Checked: 2026-11-13
Scheduled recheck: 2027-03-13
Plan: Not specified
Surface: Lody Electron desktop app; Lody hosted web app; Lody native iOS and Android apps; Lody CLI and daemon
Version: v0.109.0 (commit 2eefb5e); source pass 2026-11-13

Only the cited atomic findings are established. Remaining atomic requirements and the full rubric scenario remain unverified.
No mandatory workflow exists; mid-run model switching is not documented.

Source: https://lody.ai/docs/quickstart/
Locator: Install, sign-in, add project, connect GitHub, configure agents, file locations
Finding: Install desktop/mobile/CLI, sign in (browser), add local dir via picker or npx lody project add, connect GitHub, add agent configs and Test them, run npx lody daemon start on servers. Local data under ~/.lody/repos and ~/.lody/logs.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/session/
Locator: Composer, fork, side chat, session list, archive/restore/delete, Quick Session, Open in editor
Finding: Sessions bundle conversation, branch and worktree; fork/side-chat reuse history; sidebar shows status, repo, branch, PR and diff stats; archive retains history and reclaims worktrees; restore recreates them; Quick Session desktop shortcut; Open-in launches VS Code/Xcode/Sublime/Zed (external launchers, not extensions).
Retrieved: 2026-11-13

Source: https://lody.ai/docs/session-tabs/
Locator: Child chats, file/diff tabs, tab management
Finding: Child chats share the parent session workspace (files/branch/uncommitted changes) with separate histories; file/diff tabs open beside chat; closing a tab does not stop the agent or remove the worktree.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/session-orchestration/
Locator: Built-in Lody MCP tools: create/reuse, status, follow-up, cancel, model/reasoning selection
Finding: Agents use built-in Lody MCP tools to create/reuse conversations, read status and bounded history, send follow-ups, cancel running turns, select compatible model/reasoning, and bring results back; parent relationship preserved; bounded to Lody conversation data, not a background scheduler.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/agent-collaboration/
Locator: Orchestrator walkthrough: triage, cross-repo fix, review-fix loop, @ mentions
Finding: Primary agent triages PR/issue queues, delegates fixes/reviews to Kimi/Codex/Grok sessions across machines, exchanges findings via @ session mentions, and collects commits; examples are illustrative prompts, not benchmark results.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/session-handoff/
Locator: Handoff steps, permissions table, live handoff vs share link, FAQ
Finding: Teammate joins the same live session (conversation, diffs, worktree) after workspace invite plus machine/project sharing; sharing may widen visibility to other conversations on that machine; transcript/markdown copy is a separate record-only action.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/team/
Locator: Invite, roles, member sessions, token usage by member, machine visibility
Finding: Invite by email with role; owners/admins manage members; All Tasks view with avatars; per-member token usage and trends; machines private by default, explicitly shared per machine; shared docs, mentions and task management are planned, not shipped.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/scheduled-tasks/
Locator: Triggers, owning machine, agent-proposed schedules, missed runs, FAQ
Finding: Scheduled/manual/one-shot tasks run on one owning machine (CLI, local timezone; nothing runs in cloud); agent can only propose schedules, never create them; missed runs catch up once; only the creator can edit/pause/delete; machine must be awake.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/github/
Locator: GitHub App setup, issue/PR context, PR panel, auto-archive, commit/push, review sync
Finding: GitHub App gives repo access; issues/PRs inject context via @; PR panel shows state/CI/comments/reviews with in-Lody merge and branch delete; review comments sync both ways; PR-linked sessions auto-archive on merge/close; optional act-as-you identity for PR actions.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/agent-roles/
Locator: Role creation, sharing, mentions, offline-machine behavior
Finding: Roles package machine, agent config, model, reasoning, permission and instruction; private until shared with workspace; mentionable via @ to start new conversations; bound to one machine/config and unusable while offline.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/acp-feature-support/
Locator: Support matrix, extension capability reference, notes
Finding: Nine built-in providers (Claude Code, Codex, Grok, Kimi Code, Devin, Pi, DeepSeek Harness, Bub, Dimcode) share the ACP baseline; optional capabilities (MCP transports, resume/fork, steering, tasks, subagents, goals, usage, rate limits) differ per adapter via acp-extension-core; declarations are read at session start so updates can shift the matrix.
Retrieved: 2026-11-13

Source: https://lody.ai/terms/
Locator: Provider, sign-in, fees/billing, account rules
Finding: Provider LoroHub LLC; sign-in via GitHub OAuth; free and paid (Plus) plans with prices on the pricing page in USD; user retains content ownership with a services-only license grant.
Retrieved: 2026-11-13

## lody:RUN-01

Finding: Agents execute on the user's own machines (desktop or BYO server/VM) connected by the daemon; the vendor cloud only relays and stores workspace data. Work survives the controlling client and continues from any device while the execution machine stays online.

Verification: agent-cross-checked
Checked: 2026-11-13
Scheduled recheck: 2027-03-13
Plan: Not specified
Surface: Lody Electron desktop app; Lody CLI and daemon; Lody native iOS and Android apps; Lody hosted web app
Version: v0.109.0 (commit 2eefb5e); source pass 2026-11-13

Only the cited atomic findings are established. Remaining atomic requirements and the full rubric scenario remain unverified.
No vendor compute, provisioning, regions or lifetimes exist; self-hosting scope beyond local-only mode is not fully documented.

Source: https://lody.ai/price/
Locator: Plan cards, feature table, FAQ (tokens, seats, cancellation)
Finding: Free ($0 forever: 2 workspaces, 200 sessions/workspace, 30 turns/session, 3 members) vs Plus ($8/seat/month billed yearly, unlimited) vs Enterprise (custom; SSO, procurement, rollout). No AI token charges; BYO agent accounts at zero markup. Prices USD; yearly upfront per seat for 12 months.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/quickstart/
Locator: Install, sign-in, add project, connect GitHub, configure agents, file locations
Finding: Install desktop/mobile/CLI, sign in (browser), add local dir via picker or npx lody project add, connect GitHub, add agent configs and Test them, run npx lody daemon start on servers. Local data under ~/.lody/repos and ~/.lody/logs.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/parallel-agents/
Locator: Isolated worktrees, mixed agents, team visibility, coordinator handoff, FAQ
Finding: Multiple sessions each with own worktree/branch; mix Claude Code/Codex/Kimi/Grok per session; team sees running sessions via All Tasks; concurrency limited by host machine capacity; agent-to-agent coordination via Agent Session Control.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/mobile/
Locator: Install, Live Activities, push notifications, progress/diff monitoring, offline support
Finding: Native iOS (App Store + TestFlight) and Android apps: notifications on task completion/approval/PR-ready, iOS Live Activities incl. actionable permission alerts, diff review and approvals, project file browsing; realtime editing is desktop-only; offline viewing of cached conversations with sync on reconnect.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/scheduled-tasks/
Locator: Triggers, owning machine, agent-proposed schedules, missed runs, FAQ
Finding: Scheduled/manual/one-shot tasks run on one owning machine (CLI, local timezone; nothing runs in cloud); agent can only propose schedules, never create them; missed runs catch up once; only the creator can edit/pause/delete; machine must be awake.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/encrypted-workspaces/
Locator: Standard vs encrypted comparison, device approval, recovery, known limits
Finding: In E2E workspaces only authorized devices can read content; servers relay/store unreadable data; new devices need approval; loss of all devices plus recovery file means permanent loss; browser security depends on served code; price page flags E2E as coming soon on Plus.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/magpie/
Locator: Import targets, gateway, statuses, model management
Finding: One command imports Magpie provider setups (Claude, Codex, Pi, DSH, Kimi, Grok, Bub) on the same server; upstream API keys stay in Magpie; import does not prove inference works; cloud workspaces only, not OSS local-only mode.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/local-project/
Locator: Adding projects, local-first availability, CLI history sync, team visibility, limitations
Finding: Any local directory works with synced chat/diffs/branches/worktrees; desktop works offline with later sync; imports Codex/Claude CLI history; team visibility is opt-in per project; local projects cannot push to remote branches directly.
Retrieved: 2026-11-13

Source: https://github.com/LodyAI/Lody/blob/v0.109.0/LICENSE
Locator: Root LICENSE file, Apache grant header
Finding: Root LICENSE is Apache License 2.0 covering the pinned release tree (apps/cli, apps/electron, packages/*, site-docs); hosted sync backend and store-distributed mobile builds are outside this grant.
Retrieved: 2026-11-13

Source: https://github.com/LodyAI/Lody/tree/v0.109.0/apps/cli/src/commands
Locator: session.ts, machine.ts, daemon.ts, agent-config.ts, github.ts, review.ts, export.ts, magpie-import.ts, internal.ts
Finding: CLI implements session/machine/daemon/agent-config/GitHub/review/export/magpie commands; no public REST API surface or SDK package in commands, packages or docs.
Retrieved: 2026-11-13

## lody:RUN-02

Finding: Each session gets its own Git branch and worktree directory for file separation; credentials stay machine-local in the OS keychain. No container, VM or OS-sandbox boundary exists, and worktrees are not a security boundary.

Verification: agent-cross-checked
Checked: 2026-11-13
Scheduled recheck: 2027-03-13
Plan: Not specified
Surface: Lody Electron desktop app; Lody CLI and daemon
Version: v0.109.0 (commit 2eefb5e); source pass 2026-11-13

Only the cited atomic findings are established. Remaining atomic requirements and the full rubric scenario remain unverified.
Isolation is file separation only; hostile-code containment is not claimed.

Source: https://lody.ai/docs/session/
Locator: Composer, fork, side chat, session list, archive/restore/delete, Quick Session, Open in editor
Finding: Sessions bundle conversation, branch and worktree; fork/side-chat reuse history; sidebar shows status, repo, branch, PR and diff stats; archive retains history and reclaims worktrees; restore recreates them; Quick Session desktop shortcut; Open-in launches VS Code/Xcode/Sublime/Zed (external launchers, not extensions).
Retrieved: 2026-11-13

Source: https://lody.ai/docs/parallel-agents/
Locator: Isolated worktrees, mixed agents, team visibility, coordinator handoff, FAQ
Finding: Multiple sessions each with own worktree/branch; mix Claude Code/Codex/Kimi/Grok per session; team sees running sessions via All Tasks; concurrency limited by host machine capacity; agent-to-agent coordination via Agent Session Control.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/worktrees/
Locator: Worktree layout, setup/cleanup scripts, env vars, retention and recovery
Finding: One branch (session/<id>) and worktree per session under ~/.lody/repos/<repoId>/; project setup/cleanup scripts with LODY_* env vars; archive/backup rules keep branches and stage pending changes, discard ignored files; restore recreates the worktree from the branch.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/local-project/
Locator: Adding projects, local-first availability, CLI history sync, team visibility, limitations
Finding: Any local directory works with synced chat/diffs/branches/worktrees; desktop works offline with later sync; imports Codex/Claude CLI history; team visibility is opt-in per project; local projects cannot push to remote branches directly.
Retrieved: 2026-11-13

Source: https://github.com/LodyAI/Lody/tree/v0.109.0/apps/cli/src/mcp
Locator: lody-mcp-server.ts (@modelcontextprotocol/server), lody-mcp-http-server.ts, session-mcp-resolver.ts, schedule-tools.ts, agent-role-tools.ts, authentication/
Finding: Lody hosts its own MCP server (session/daemon/schedule/role tools over stdio and HTTP loopback) for agents, and resolves the workspace MCP catalog plus OAuth/keychain credentials into ACP sessions as an MCP client.
Retrieved: 2026-11-13

Source: https://github.com/LodyAI/Lody/blob/v0.109.0/apps/cli/src/commands/session.ts
Locator: worktree creation/session worktree references; agent-client worktree handling
Finding: Sessions create and manage per-session Git worktrees/branches; container, VM, gVisor, Firecracker and OS-sandbox isolation terms return no implementation hits (only file-icon assets), so isolation is worktree-level file separation.
Retrieved: 2026-11-13

Source: https://github.com/LodyAI/Lody/blob/v0.109.0/apps/cli/src/agent/agent-client.ts
Locator: permissionMode/permission plumbing; lody-acp-extension steering/rate-limit snapshots
Finding: Per-session permission modes flow into agent runs with steering support and rate-limit snapshots where the adapter declares them; personal/project credential grants stay machine-local.
Retrieved: 2026-11-13

## lody:RUN-03

Finding: Client disconnects, restarts and offline stretches recover through daemon persistence, catch-up sync and worktree recreation from kept branches. Crash-recovery semantics and multi-day guarantees are only partly documented.

Verification: agent-cross-checked
Checked: 2026-11-13
Scheduled recheck: 2027-03-13
Plan: Not specified
Surface: Lody Electron desktop app; Lody CLI and daemon; Lody native iOS and Android apps; Lody hosted web app
Version: v0.109.0 (commit 2eefb5e); source pass 2026-11-13

Only the cited atomic findings are established. Remaining atomic requirements and the full rubric scenario remain unverified.
Worker-crash behavior, duplicate-action handling and multi-day continuity lack explicit guarantees.

Source: https://lody.ai/docs/quickstart/
Locator: Install, sign-in, add project, connect GitHub, configure agents, file locations
Finding: Install desktop/mobile/CLI, sign in (browser), add local dir via picker or npx lody project add, connect GitHub, add agent configs and Test them, run npx lody daemon start on servers. Local data under ~/.lody/repos and ~/.lody/logs.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/session/
Locator: Composer, fork, side chat, session list, archive/restore/delete, Quick Session, Open in editor
Finding: Sessions bundle conversation, branch and worktree; fork/side-chat reuse history; sidebar shows status, repo, branch, PR and diff stats; archive retains history and reclaims worktrees; restore recreates them; Quick Session desktop shortcut; Open-in launches VS Code/Xcode/Sublime/Zed (external launchers, not extensions).
Retrieved: 2026-11-13

Source: https://lody.ai/docs/parallel-agents/
Locator: Isolated worktrees, mixed agents, team visibility, coordinator handoff, FAQ
Finding: Multiple sessions each with own worktree/branch; mix Claude Code/Codex/Kimi/Grok per session; team sees running sessions via All Tasks; concurrency limited by host machine capacity; agent-to-agent coordination via Agent Session Control.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/mobile/
Locator: Install, Live Activities, push notifications, progress/diff monitoring, offline support
Finding: Native iOS (App Store + TestFlight) and Android apps: notifications on task completion/approval/PR-ready, iOS Live Activities incl. actionable permission alerts, diff review and approvals, project file browsing; realtime editing is desktop-only; offline viewing of cached conversations with sync on reconnect.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/scheduled-tasks/
Locator: Triggers, owning machine, agent-proposed schedules, missed runs, FAQ
Finding: Scheduled/manual/one-shot tasks run on one owning machine (CLI, local timezone; nothing runs in cloud); agent can only propose schedules, never create them; missed runs catch up once; only the creator can edit/pause/delete; machine must be awake.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/worktrees/
Locator: Worktree layout, setup/cleanup scripts, env vars, retention and recovery
Finding: One branch (session/<id>) and worktree per session under ~/.lody/repos/<repoId>/; project setup/cleanup scripts with LODY_* env vars; archive/backup rules keep branches and stage pending changes, discard ignored files; restore recreates the worktree from the branch.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/local-project/
Locator: Adding projects, local-first availability, CLI history sync, team visibility, limitations
Finding: Any local directory works with synced chat/diffs/branches/worktrees; desktop works offline with later sync; imports Codex/Claude CLI history; team visibility is opt-in per project; local projects cannot push to remote branches directly.
Retrieved: 2026-11-13

Source: https://lody.ai/changelog/
Locator: Dated release notes entries
Finding: Dated bilingual release notes with recent entries (e.g. 2026-10-15 desktop sign-in fixes; 2026-04-22 PR panel); documents active maintenance alongside GitHub releases.
Retrieved: 2026-11-13

Source: https://github.com/LodyAI/Lody/tree/v0.109.0/apps/cli/src/commands
Locator: session.ts, machine.ts, daemon.ts, agent-config.ts, github.ts, review.ts, export.ts, magpie-import.ts, internal.ts
Finding: CLI implements session/machine/daemon/agent-config/GitHub/review/export/magpie commands; no public REST API surface or SDK package in commands, packages or docs.
Retrieved: 2026-11-13

Source: https://github.com/LodyAI/Lody/tree/v0.109.0/apps/cli/src/mcp
Locator: lody-mcp-server.ts (@modelcontextprotocol/server), lody-mcp-http-server.ts, session-mcp-resolver.ts, schedule-tools.ts, agent-role-tools.ts, authentication/
Finding: Lody hosts its own MCP server (session/daemon/schedule/role tools over stdio and HTTP loopback) for agents, and resolves the workspace MCP catalog plus OAuth/keychain credentials into ACP sessions as an MCP client.
Retrieved: 2026-11-13

Source: https://github.com/LodyAI/Lody/blob/v0.109.0/apps/cli/README.md
Locator: authorizeExecution, owner/admin/member device grants, journal reset
Finding: Encrypted workspaces authorize execution per workspace/device with owner/admin/member grants, sub-15-minute memory-only grants, and offline journal reset; UI account IDs grant nothing; guest/recovery/removed/revoked devices do not qualify.
Retrieved: 2026-11-13

## lody:RUN-04

Finding: Per-project setup/cleanup scripts with LODY_* env vars prepare every worktree; secrets arrive via agent-config env and keychain. Snapshots, managed services, collision handling and automatic repair are not established.

Verification: agent-cross-checked
Checked: 2026-11-13
Scheduled recheck: 2027-03-13
Plan: Not specified
Surface: Lody Electron desktop app; Lody CLI and daemon
Version: v0.109.0 (commit 2eefb5e); source pass 2026-11-13

Only the cited atomic findings are established. Remaining atomic requirements and the full rubric scenario remain unverified.
Each worktree runs setup independently; services, ports and repair behavior are only partly documented.

Source: https://lody.ai/docs/quickstart/
Locator: Install, sign-in, add project, connect GitHub, configure agents, file locations
Finding: Install desktop/mobile/CLI, sign in (browser), add local dir via picker or npx lody project add, connect GitHub, add agent configs and Test them, run npx lody daemon start on servers. Local data under ~/.lody/repos and ~/.lody/logs.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/session/
Locator: Composer, fork, side chat, session list, archive/restore/delete, Quick Session, Open in editor
Finding: Sessions bundle conversation, branch and worktree; fork/side-chat reuse history; sidebar shows status, repo, branch, PR and diff stats; archive retains history and reclaims worktrees; restore recreates them; Quick Session desktop shortcut; Open-in launches VS Code/Xcode/Sublime/Zed (external launchers, not extensions).
Retrieved: 2026-11-13

Source: https://lody.ai/docs/worktrees/
Locator: Worktree layout, setup/cleanup scripts, env vars, retention and recovery
Finding: One branch (session/<id>) and worktree per session under ~/.lody/repos/<repoId>/; project setup/cleanup scripts with LODY_* env vars; archive/backup rules keep branches and stage pending changes, discard ignored files; restore recreates the worktree from the branch.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/local-project/
Locator: Adding projects, local-first availability, CLI history sync, team visibility, limitations
Finding: Any local directory works with synced chat/diffs/branches/worktrees; desktop works offline with later sync; imports Codex/Claude CLI history; team visibility is opt-in per project; local projects cannot push to remote branches directly.
Retrieved: 2026-11-13

Source: https://github.com/LodyAI/Lody/tree/v0.109.0/apps/cli/src/commands
Locator: session.ts, machine.ts, daemon.ts, agent-config.ts, github.ts, review.ts, export.ts, magpie-import.ts, internal.ts
Finding: CLI implements session/machine/daemon/agent-config/GitHub/review/export/magpie commands; no public REST API surface or SDK package in commands, packages or docs.
Retrieved: 2026-11-13

Source: https://github.com/LodyAI/Lody/tree/v0.109.0/apps/cli/src/mcp
Locator: lody-mcp-server.ts (@modelcontextprotocol/server), lody-mcp-http-server.ts, session-mcp-resolver.ts, schedule-tools.ts, agent-role-tools.ts, authentication/
Finding: Lody hosts its own MCP server (session/daemon/schedule/role tools over stdio and HTTP loopback) for agents, and resolves the workspace MCP catalog plus OAuth/keychain credentials into ACP sessions as an MCP client.
Retrieved: 2026-11-13

## lody:RUN-05

Finding: Free-plan turn caps and schedule serialization bound usage; rate limits and quota states surface visibly with a scheduled-continue path. Timeouts, retries and spend controls are internal or provider-side, not Lody budgets.

Verification: agent-cross-checked
Checked: 2026-11-13
Scheduled recheck: 2027-03-13
Plan: Not specified
Surface: Lody Electron desktop app; Lody hosted web app; Lody CLI and daemon
Version: v0.109.0 (commit 2eefb5e); source pass 2026-11-13

Only the cited atomic findings are established. Remaining atomic requirements and the full rubric scenario remain unverified.
No Lody-side time, token or spend budgets exist; provider limits apply externally.

Source: https://lody.ai/price/
Locator: Plan cards, feature table, FAQ (tokens, seats, cancellation)
Finding: Free ($0 forever: 2 workspaces, 200 sessions/workspace, 30 turns/session, 3 members) vs Plus ($8/seat/month billed yearly, unlimited) vs Enterprise (custom; SSO, procurement, rollout). No AI token charges; BYO agent accounts at zero markup. Prices USD; yearly upfront per seat for 12 months.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/parallel-agents/
Locator: Isolated worktrees, mixed agents, team visibility, coordinator handoff, FAQ
Finding: Multiple sessions each with own worktree/branch; mix Claude Code/Codex/Kimi/Grok per session; team sees running sessions via All Tasks; concurrency limited by host machine capacity; agent-to-agent coordination via Agent Session Control.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/session-orchestration/
Locator: Built-in Lody MCP tools: create/reuse, status, follow-up, cancel, model/reasoning selection
Finding: Agents use built-in Lody MCP tools to create/reuse conversations, read status and bounded history, send follow-ups, cancel running turns, select compatible model/reasoning, and bring results back; parent relationship preserved; bounded to Lody conversation data, not a background scheduler.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/scheduled-tasks/
Locator: Triggers, owning machine, agent-proposed schedules, missed runs, FAQ
Finding: Scheduled/manual/one-shot tasks run on one owning machine (CLI, local timezone; nothing runs in cloud); agent can only propose schedules, never create them; missed runs catch up once; only the creator can edit/pause/delete; machine must be awake.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/acp-feature-support/
Locator: Support matrix, extension capability reference, notes
Finding: Nine built-in providers (Claude Code, Codex, Grok, Kimi Code, Devin, Pi, DeepSeek Harness, Bub, Dimcode) share the ACP baseline; optional capabilities (MCP transports, resume/fork, steering, tasks, subagents, goals, usage, rate limits) differ per adapter via acp-extension-core; declarations are read at session start so updates can shift the matrix.
Retrieved: 2026-11-13

Source: https://github.com/LodyAI/Lody/tree/v0.109.0/apps/cli/src/commands
Locator: session.ts, machine.ts, daemon.ts, agent-config.ts, github.ts, review.ts, export.ts, magpie-import.ts, internal.ts
Finding: CLI implements session/machine/daemon/agent-config/GitHub/review/export/magpie commands; no public REST API surface or SDK package in commands, packages or docs.
Retrieved: 2026-11-13

Source: https://github.com/LodyAI/Lody/blob/v0.109.0/apps/cli/src/lib/notifications/AGENTS.md
Locator: Turn/outcome notification pipeline, mobile/cloud ports, best-effort delivery
Finding: Turn outcomes project into control documents and mobile push via the cloud port with best-effort delivery (no outbox, retry, reconnect replay or exactly-once); permission push and Live Activity sync are separate paths.
Retrieved: 2026-11-13

Source: https://github.com/LodyAI/Lody/blob/v0.109.0/apps/cli/src/orchestration/README.md
Locator: Coordinator workflow, inbox, session-create rollback point-of-no-return
Finding: Orchestration layer runs coordinator workflows over sessions with an inbox; session-create has a documented point-of-no-rollback for cleanup only (not user-facing revert); no merge queue, batch-review queue or duplicate-task detection.
Retrieved: 2026-11-13

## lody:RUN-06

Finding: Live terminal output, log files, failure states, PR checks, per-member usage trends and session export are all observable; presence reconnects keep views consistent. Traces, project rollups and performance claims are not established.

Verification: agent-cross-checked
Checked: 2026-11-13
Scheduled recheck: 2027-03-13
Plan: Not specified
Surface: Lody Electron desktop app; Lody hosted web app; Lody native iOS and Android apps
Version: v0.109.0 (commit 2eefb5e); source pass 2026-11-13

Only the cited atomic findings are established. Remaining atomic requirements and the full rubric scenario remain unverified.
No tracing, project-level statistics, or vendor performance figures exist; this catalog measures none.

Source: https://lody.ai/docs/quickstart/
Locator: Install, sign-in, add project, connect GitHub, configure agents, file locations
Finding: Install desktop/mobile/CLI, sign in (browser), add local dir via picker or npx lody project add, connect GitHub, add agent configs and Test them, run npx lody daemon start on servers. Local data under ~/.lody/repos and ~/.lody/logs.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/cli/
Locator: Command reference: login, daemon, workspaces, sessions, machines, agent configs, review, export
Finding: lody CLI is both the daemon runtime (lody start / daemon start) and a one-shot manager: session create/chat/list/status, project/workspace/machine/agent-config commands, lody review prompting and rendering, lody export, import-magpie, --json output; built-in help is the flag source of truth.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/session/
Locator: Composer, fork, side chat, session list, archive/restore/delete, Quick Session, Open in editor
Finding: Sessions bundle conversation, branch and worktree; fork/side-chat reuse history; sidebar shows status, repo, branch, PR and diff stats; archive retains history and reclaims worktrees; restore recreates them; Quick Session desktop shortcut; Open-in launches VS Code/Xcode/Sublime/Zed (external launchers, not extensions).
Retrieved: 2026-11-13

Source: https://lody.ai/docs/parallel-agents/
Locator: Isolated worktrees, mixed agents, team visibility, coordinator handoff, FAQ
Finding: Multiple sessions each with own worktree/branch; mix Claude Code/Codex/Kimi/Grok per session; team sees running sessions via All Tasks; concurrency limited by host machine capacity; agent-to-agent coordination via Agent Session Control.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/team/
Locator: Invite, roles, member sessions, token usage by member, machine visibility
Finding: Invite by email with role; owners/admins manage members; All Tasks view with avatars; per-member token usage and trends; machines private by default, explicitly shared per machine; shared docs, mentions and task management are planned, not shipped.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/mobile/
Locator: Install, Live Activities, push notifications, progress/diff monitoring, offline support
Finding: Native iOS (App Store + TestFlight) and Android apps: notifications on task completion/approval/PR-ready, iOS Live Activities incl. actionable permission alerts, diff review and approvals, project file browsing; realtime editing is desktop-only; offline viewing of cached conversations with sync on reconnect.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/github/
Locator: GitHub App setup, issue/PR context, PR panel, auto-archive, commit/push, review sync
Finding: GitHub App gives repo access; issues/PRs inject context via @; PR panel shows state/CI/comments/reviews with in-Lody merge and branch delete; review comments sync both ways; PR-linked sessions auto-archive on merge/close; optional act-as-you identity for PR actions.
Retrieved: 2026-11-13

Source: https://github.com/LodyAI/Lody/tree/v0.109.0/apps/cli/src/commands
Locator: session.ts, machine.ts, daemon.ts, agent-config.ts, github.ts, review.ts, export.ts, magpie-import.ts, internal.ts
Finding: CLI implements session/machine/daemon/agent-config/GitHub/review/export/magpie commands; no public REST API surface or SDK package in commands, packages or docs.
Retrieved: 2026-11-13

Source: https://github.com/LodyAI/Lody/blob/v0.109.0/apps/cli/src/lib/notifications/AGENTS.md
Locator: Turn/outcome notification pipeline, mobile/cloud ports, best-effort delivery
Finding: Turn outcomes project into control documents and mobile push via the cloud port with best-effort delivery (no outbox, retry, reconnect replay or exactly-once); permission push and Live Activity sync are separate paths.
Retrieved: 2026-11-13

## lody:RUN-07

Finding: Token, context, quota and machine-resource usage is visible per session and broken down by model and member, but money never attaches: Lody bills only the workspace while providers bill their own accounts.

Verification: agent-cross-checked
Checked: 2026-11-13
Scheduled recheck: 2027-03-13
Plan: Not specified
Surface: Lody Electron desktop app; Lody hosted web app
Version: v0.109.0 (commit 2eefb5e); source pass 2026-11-13

Only the cited atomic findings are established. Remaining atomic requirements and the full rubric scenario remain unverified.
No billed amounts, child/epic rollups, alerts or exports exist for cost data.

Source: https://lody.ai/price/
Locator: Plan cards, feature table, FAQ (tokens, seats, cancellation)
Finding: Free ($0 forever: 2 workspaces, 200 sessions/workspace, 30 turns/session, 3 members) vs Plus ($8/seat/month billed yearly, unlimited) vs Enterprise (custom; SSO, procurement, rollout). No AI token charges; BYO agent accounts at zero markup. Prices USD; yearly upfront per seat for 12 months.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/cli/
Locator: Command reference: login, daemon, workspaces, sessions, machines, agent configs, review, export
Finding: lody CLI is both the daemon runtime (lody start / daemon start) and a one-shot manager: session create/chat/list/status, project/workspace/machine/agent-config commands, lody review prompting and rendering, lody export, import-magpie, --json output; built-in help is the flag source of truth.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/parallel-agents/
Locator: Isolated worktrees, mixed agents, team visibility, coordinator handoff, FAQ
Finding: Multiple sessions each with own worktree/branch; mix Claude Code/Codex/Kimi/Grok per session; team sees running sessions via All Tasks; concurrency limited by host machine capacity; agent-to-agent coordination via Agent Session Control.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/team/
Locator: Invite, roles, member sessions, token usage by member, machine visibility
Finding: Invite by email with role; owners/admins manage members; All Tasks view with avatars; per-member token usage and trends; machines private by default, explicitly shared per machine; shared docs, mentions and task management are planned, not shipped.
Retrieved: 2026-11-13

## lody:RUN-08

Finding: Parallelism is bounded by host capacity, plan session caps, an internal ACP startup queue and serialized schedules, with cancellation and restore for recovery. Resource-aware limits, fairness and verification reuse are not established.

Verification: agent-cross-checked
Checked: 2026-11-13
Scheduled recheck: 2027-03-13
Plan: Not specified
Surface: Lody Electron desktop app; Lody CLI and daemon
Version: v0.109.0 (commit 2eefb5e); source pass 2026-11-13

Only the cited atomic findings are established. Remaining atomic requirements and the full rubric scenario remain unverified.
No CPU/RAM limits, fairness policy, host awareness, or check reuse is documented.

Source: https://lody.ai/price/
Locator: Plan cards, feature table, FAQ (tokens, seats, cancellation)
Finding: Free ($0 forever: 2 workspaces, 200 sessions/workspace, 30 turns/session, 3 members) vs Plus ($8/seat/month billed yearly, unlimited) vs Enterprise (custom; SSO, procurement, rollout). No AI token charges; BYO agent accounts at zero markup. Prices USD; yearly upfront per seat for 12 months.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/session/
Locator: Composer, fork, side chat, session list, archive/restore/delete, Quick Session, Open in editor
Finding: Sessions bundle conversation, branch and worktree; fork/side-chat reuse history; sidebar shows status, repo, branch, PR and diff stats; archive retains history and reclaims worktrees; restore recreates them; Quick Session desktop shortcut; Open-in launches VS Code/Xcode/Sublime/Zed (external launchers, not extensions).
Retrieved: 2026-11-13

Source: https://lody.ai/docs/parallel-agents/
Locator: Isolated worktrees, mixed agents, team visibility, coordinator handoff, FAQ
Finding: Multiple sessions each with own worktree/branch; mix Claude Code/Codex/Kimi/Grok per session; team sees running sessions via All Tasks; concurrency limited by host machine capacity; agent-to-agent coordination via Agent Session Control.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/team/
Locator: Invite, roles, member sessions, token usage by member, machine visibility
Finding: Invite by email with role; owners/admins manage members; All Tasks view with avatars; per-member token usage and trends; machines private by default, explicitly shared per machine; shared docs, mentions and task management are planned, not shipped.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/scheduled-tasks/
Locator: Triggers, owning machine, agent-proposed schedules, missed runs, FAQ
Finding: Scheduled/manual/one-shot tasks run on one owning machine (CLI, local timezone; nothing runs in cloud); agent can only propose schedules, never create them; missed runs catch up once; only the creator can edit/pause/delete; machine must be awake.
Retrieved: 2026-11-13

Source: https://github.com/LodyAI/Lody/blob/v0.109.0/apps/cli/src/orchestration/README.md
Locator: Coordinator workflow, inbox, session-create rollback point-of-no-return
Finding: Orchestration layer runs coordinator workflows over sessions with an inbox; session-create has a documented point-of-no-rollback for cleanup only (not user-facing revert); no merge queue, batch-review queue or duplicate-task detection.
Retrieved: 2026-11-13

## lody:TEAM-01

Finding: Team sessions are visible, commentable and hand-off-able with attribution and plan-scoped membership; execution needs the machine online, not the original owner. Simultaneous co-prompting, ordering and conflict handling are not established. A separately invited workspace teammate can open the existing live session and send the next prompt to the same agent with its conversation, worktree and diffs. This establishes shared-human sequential prompting, not simultaneous prompt conflict guarantees.

Verification: sourced
Checked: 2026-11-13
Scheduled recheck: 2027-03-13
Plan: Not specified
Surface: Lody Electron desktop app; Lody hosted web app; Lody native iOS and Android apps
Version: Lody v0.109.0 (e7b7ab7aacf17f3ee056a6d708ad5ac3c18fb60f); targeted first-party pass 2026-11-13; no installed-product test

The scoped first-party source pass does not establish ordering, conflicts. No hands-on scenario was run.

Source: https://lody.ai/price/
Locator: Plan cards, feature table, FAQ (tokens, seats, cancellation)
Finding: Free ($0 forever: 2 workspaces, 200 sessions/workspace, 30 turns/session, 3 members) vs Plus ($8/seat/month billed yearly, unlimited) vs Enterprise (custom; SSO, procurement, rollout). No AI token charges; BYO agent accounts at zero markup. Prices USD; yearly upfront per seat for 12 months.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/session/
Locator: Composer, fork, side chat, session list, archive/restore/delete, Quick Session, Open in editor
Finding: Sessions bundle conversation, branch and worktree; fork/side-chat reuse history; sidebar shows status, repo, branch, PR and diff stats; archive retains history and reclaims worktrees; restore recreates them; Quick Session desktop shortcut; Open-in launches VS Code/Xcode/Sublime/Zed (external launchers, not extensions).
Retrieved: 2026-11-13

Source: https://lody.ai/docs/session-handoff/
Locator: Handoff steps, permissions table, live handoff vs share link, FAQ
Finding: Teammate joins the same live session (conversation, diffs, worktree) after workspace invite plus machine/project sharing; sharing may widen visibility to other conversations on that machine; transcript/markdown copy is a separate record-only action.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/team/
Locator: Invite, roles, member sessions, token usage by member, machine visibility
Finding: Invite by email with role; owners/admins manage members; All Tasks view with avatars; per-member token usage and trends; machines private by default, explicitly shared per machine; shared docs, mentions and task management are planned, not shipped.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/mobile/
Locator: Install, Live Activities, push notifications, progress/diff monitoring, offline support
Finding: Native iOS (App Store + TestFlight) and Android apps: notifications on task completion/approval/PR-ready, iOS Live Activities incl. actionable permission alerts, diff review and approvals, project file browsing; realtime editing is desktop-only; offline viewing of cached conversations with sync on reconnect.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/scheduled-tasks/
Locator: Triggers, owning machine, agent-proposed schedules, missed runs, FAQ
Finding: Scheduled/manual/one-shot tasks run on one owning machine (CLI, local timezone; nothing runs in cloud); agent can only propose schedules, never create them; missed runs catch up once; only the creator can edit/pause/delete; machine must be awake.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/github/
Locator: GitHub App setup, issue/PR context, PR panel, auto-archive, commit/push, review sync
Finding: GitHub App gives repo access; issues/PRs inject context via @; PR panel shows state/CI/comments/reviews with in-Lody merge and branch delete; review comments sync both ways; PR-linked sessions auto-archive on merge/close; optional act-as-you identity for PR actions.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/diff-comments/
Locator: Threads, resolve, send-to-agent, GitHub sync
Finding: Line-level Markdown threads with reply/edit/delete/resolve; threads can be sent into the chat for the agent to address; PR-linked sessions sync both ways with GitHub PR review comments.
Retrieved: 2026-11-13

## lody:TEAM-02

Finding: Owner/Admin/Member workspace roles with invite, edit, remove and revocation flows; Enterprise adds SSO and access controls. Per-project and per-task roles plus SCIM provisioning do not exist.

Verification: agent-cross-checked
Checked: 2026-11-13
Scheduled recheck: 2027-03-13
Plan: Not specified
Surface: Lody Electron desktop app; Lody hosted web app
Version: v0.109.0 (commit 2eefb5e); source pass 2026-11-13

Only the cited atomic findings are established. Remaining atomic requirements and the full rubric scenario remain unverified.
Roles are workspace-wide; no project/task roles or provisioning automation exist.

Source: https://lody.ai/price/
Locator: Plan cards, feature table, FAQ (tokens, seats, cancellation)
Finding: Free ($0 forever: 2 workspaces, 200 sessions/workspace, 30 turns/session, 3 members) vs Plus ($8/seat/month billed yearly, unlimited) vs Enterprise (custom; SSO, procurement, rollout). No AI token charges; BYO agent accounts at zero markup. Prices USD; yearly upfront per seat for 12 months.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/cli/
Locator: Command reference: login, daemon, workspaces, sessions, machines, agent configs, review, export
Finding: lody CLI is both the daemon runtime (lody start / daemon start) and a one-shot manager: session create/chat/list/status, project/workspace/machine/agent-config commands, lody review prompting and rendering, lody export, import-magpie, --json output; built-in help is the flag source of truth.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/session-handoff/
Locator: Handoff steps, permissions table, live handoff vs share link, FAQ
Finding: Teammate joins the same live session (conversation, diffs, worktree) after workspace invite plus machine/project sharing; sharing may widen visibility to other conversations on that machine; transcript/markdown copy is a separate record-only action.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/team/
Locator: Invite, roles, member sessions, token usage by member, machine visibility
Finding: Invite by email with role; owners/admins manage members; All Tasks view with avatars; per-member token usage and trends; machines private by default, explicitly shared per machine; shared docs, mentions and task management are planned, not shipped.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/local-project/
Locator: Adding projects, local-first availability, CLI history sync, team visibility, limitations
Finding: Any local directory works with synced chat/diffs/branches/worktrees; desktop works offline with later sync; imports Codex/Claude CLI history; team visibility is opt-in per project; local projects cannot push to remote branches directly.
Retrieved: 2026-11-13

Source: https://github.com/LodyAI/Lody/tree/v0.109.0/apps/cli/src/commands
Locator: session.ts, machine.ts, daemon.ts, agent-config.ts, github.ts, review.ts, export.ts, magpie-import.ts, internal.ts
Finding: CLI implements session/machine/daemon/agent-config/GitHub/review/export/magpie commands; no public REST API surface or SDK package in commands, packages or docs.
Retrieved: 2026-11-13

Source: https://github.com/LodyAI/Lody/blob/v0.109.0/apps/cli/README.md
Locator: authorizeExecution, owner/admin/member device grants, journal reset
Finding: Encrypted workspaces authorize execution per workspace/device with owner/admin/member grants, sub-15-minute memory-only grants, and offline journal reset; UI account IDs grant nothing; guest/recovery/removed/revoked devices do not qualify.
Retrieved: 2026-11-13

## lody:TEAM-03

Finding: Per-session permission modes gate agent actions with mobile approval prompts, Full Access defaults and safer scoped modes, enforced by the product and E2E machine policy. Per-type approval matrices, lifetimes and multi-approver identity are not detailed.

Verification: agent-cross-checked
Checked: 2026-11-13
Scheduled recheck: 2027-03-13
Plan: Not specified
Surface: Lody Electron desktop app; Lody native iOS and Android apps; Lody CLI and daemon
Version: v0.109.0 (commit 2eefb5e); source pass 2026-11-13

Only the cited atomic findings are established. Remaining atomic requirements and the full rubric scenario remain unverified.
Approval granularity, scope lifetimes and approver identity beyond the responding device are not documented.

Source: https://lody.ai/docs/session/
Locator: Composer, fork, side chat, session list, archive/restore/delete, Quick Session, Open in editor
Finding: Sessions bundle conversation, branch and worktree; fork/side-chat reuse history; sidebar shows status, repo, branch, PR and diff stats; archive retains history and reclaims worktrees; restore recreates them; Quick Session desktop shortcut; Open-in launches VS Code/Xcode/Sublime/Zed (external launchers, not extensions).
Retrieved: 2026-11-13

Source: https://lody.ai/docs/session-handoff/
Locator: Handoff steps, permissions table, live handoff vs share link, FAQ
Finding: Teammate joins the same live session (conversation, diffs, worktree) after workspace invite plus machine/project sharing; sharing may widen visibility to other conversations on that machine; transcript/markdown copy is a separate record-only action.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/team/
Locator: Invite, roles, member sessions, token usage by member, machine visibility
Finding: Invite by email with role; owners/admins manage members; All Tasks view with avatars; per-member token usage and trends; machines private by default, explicitly shared per machine; shared docs, mentions and task management are planned, not shipped.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/mobile/
Locator: Install, Live Activities, push notifications, progress/diff monitoring, offline support
Finding: Native iOS (App Store + TestFlight) and Android apps: notifications on task completion/approval/PR-ready, iOS Live Activities incl. actionable permission alerts, diff review and approvals, project file browsing; realtime editing is desktop-only; offline viewing of cached conversations with sync on reconnect.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/scheduled-tasks/
Locator: Triggers, owning machine, agent-proposed schedules, missed runs, FAQ
Finding: Scheduled/manual/one-shot tasks run on one owning machine (CLI, local timezone; nothing runs in cloud); agent can only propose schedules, never create them; missed runs catch up once; only the creator can edit/pause/delete; machine must be awake.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/github/
Locator: GitHub App setup, issue/PR context, PR panel, auto-archive, commit/push, review sync
Finding: GitHub App gives repo access; issues/PRs inject context via @; PR panel shows state/CI/comments/reviews with in-Lody merge and branch delete; review comments sync both ways; PR-linked sessions auto-archive on merge/close; optional act-as-you identity for PR actions.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/cli-runtimes/
Locator: ACP Registry runtimes, Custom ACP, prerequisites note
Finding: Every ACP Registry runtime (Auggie, Autohand, Codebuddy, Cline, Factory, Gemini, Kimi, OpenCode, Qwen, pi ACP) plus Custom ACP launch commands; host must have the runtime command, login and credentials installed; models depend on runtime and account.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/acp-feature-support/
Locator: Support matrix, extension capability reference, notes
Finding: Nine built-in providers (Claude Code, Codex, Grok, Kimi Code, Devin, Pi, DeepSeek Harness, Bub, Dimcode) share the ACP baseline; optional capabilities (MCP transports, resume/fork, steering, tasks, subagents, goals, usage, rate limits) differ per adapter via acp-extension-core; declarations are read at session start so updates can shift the matrix.
Retrieved: 2026-11-13

Source: https://github.com/LodyAI/Lody/tree/v0.109.0/apps/cli/src/mcp
Locator: lody-mcp-server.ts (@modelcontextprotocol/server), lody-mcp-http-server.ts, session-mcp-resolver.ts, schedule-tools.ts, agent-role-tools.ts, authentication/
Finding: Lody hosts its own MCP server (session/daemon/schedule/role tools over stdio and HTTP loopback) for agents, and resolves the workspace MCP catalog plus OAuth/keychain credentials into ACP sessions as an MCP client.
Retrieved: 2026-11-13

Source: https://github.com/LodyAI/Lody/blob/v0.109.0/apps/cli/src/agent/agent-client.ts
Locator: permissionMode/permission plumbing; lody-acp-extension steering/rate-limit snapshots
Finding: Per-session permission modes flow into agent runs with steering support and rate-limit snapshots where the adapter declares them; personal/project credential grants stay machine-local.
Retrieved: 2026-11-13

Source: https://github.com/LodyAI/Lody/blob/v0.109.0/apps/cli/README.md
Locator: authorizeExecution, owner/admin/member device grants, journal reset
Finding: Encrypted workspaces authorize execution per workspace/device with owner/admin/member grants, sub-15-minute memory-only grants, and offline journal reset; UI account IDs grant nothing; guest/recovery/removed/revoked devices do not qualify.
Retrieved: 2026-11-13

## lody:TEAM-04

Finding: Attributed history persists across users and sessions with export paths; retention ends at user deletion with a 30-day clearance SLA. Formal decision links and an integrity model are not established, and the word audit is not used.

Verification: agent-cross-checked
Checked: 2026-11-13
Scheduled recheck: 2027-03-13
Plan: Not specified
Surface: Lody Electron desktop app; Lody hosted web app; Lody CLI and daemon
Version: v0.109.0 (commit 2eefb5e); source pass 2026-11-13

Only the cited atomic findings are established. Remaining atomic requirements and the full rubric scenario remain unverified.
No decision-link graph, exportable activity log, or tamper-evidence integrity model is documented.

Source: https://lody.ai/docs/cli/
Locator: Command reference: login, daemon, workspaces, sessions, machines, agent configs, review, export
Finding: lody CLI is both the daemon runtime (lody start / daemon start) and a one-shot manager: session create/chat/list/status, project/workspace/machine/agent-config commands, lody review prompting and rendering, lody export, import-magpie, --json output; built-in help is the flag source of truth.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/session/
Locator: Composer, fork, side chat, session list, archive/restore/delete, Quick Session, Open in editor
Finding: Sessions bundle conversation, branch and worktree; fork/side-chat reuse history; sidebar shows status, repo, branch, PR and diff stats; archive retains history and reclaims worktrees; restore recreates them; Quick Session desktop shortcut; Open-in launches VS Code/Xcode/Sublime/Zed (external launchers, not extensions).
Retrieved: 2026-11-13

Source: https://lody.ai/docs/session-handoff/
Locator: Handoff steps, permissions table, live handoff vs share link, FAQ
Finding: Teammate joins the same live session (conversation, diffs, worktree) after workspace invite plus machine/project sharing; sharing may widen visibility to other conversations on that machine; transcript/markdown copy is a separate record-only action.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/team/
Locator: Invite, roles, member sessions, token usage by member, machine visibility
Finding: Invite by email with role; owners/admins manage members; All Tasks view with avatars; per-member token usage and trends; machines private by default, explicitly shared per machine; shared docs, mentions and task management are planned, not shipped.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/mobile/
Locator: Install, Live Activities, push notifications, progress/diff monitoring, offline support
Finding: Native iOS (App Store + TestFlight) and Android apps: notifications on task completion/approval/PR-ready, iOS Live Activities incl. actionable permission alerts, diff review and approvals, project file browsing; realtime editing is desktop-only; offline viewing of cached conversations with sync on reconnect.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/github/
Locator: GitHub App setup, issue/PR context, PR panel, auto-archive, commit/push, review sync
Finding: GitHub App gives repo access; issues/PRs inject context via @; PR panel shows state/CI/comments/reviews with in-Lody merge and branch delete; review comments sync both ways; PR-linked sessions auto-archive on merge/close; optional act-as-you identity for PR actions.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/lody-review/
Locator: Review format, report contents, requirements, options
Finding: npx lody review renders a local Git review into a self-contained shareable HTML report without signing in; runs read-only against the local repo; first render may download and cache a verified viewer.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/diff-comments/
Locator: Threads, resolve, send-to-agent, GitHub sync
Finding: Line-level Markdown threads with reply/edit/delete/resolve; threads can be sent into the chat for the agent to address; PR-linked sessions sync both ways with GitHub PR review comments.
Retrieved: 2026-11-13

Source: https://lody.ai/privacy/
Locator: Data collected, subprocessors, retention/deletion, rights
Finding: Controller LoroHub LLC; collects account/auth data, device/diagnostics, service logs, conversation content; subprocessors Cloudflare, Convex, GitHub, Google Analytics, PostHog, Sentry; export/deletion on request with 30-day clearance; no explicit model-training use stated; no telemetry opt-out control documented.
Retrieved: 2026-11-13

## lody:TEAM-05

Finding: Reviewers locate work through statuses and notifications, read round diffs beside evidence, comment, request changes and ship via Create PR and merge, with keyboard shortcuts and mobile review support. Effort analytics and missed-evidence detection are absent.

Verification: agent-cross-checked
Checked: 2026-11-13
Scheduled recheck: 2027-03-13
Plan: Not specified
Surface: Lody Electron desktop app; Lody hosted web app; Lody native iOS and Android apps
Version: v0.109.0 (commit 2eefb5e); source pass 2026-11-13

Only the cited atomic findings are established. Remaining atomic requirements and the full rubric scenario remain unverified.
No review-effort metrics, missed-evidence detection, or high-volume triage queue exists.

Source: https://lody.ai/docs/quickstart/
Locator: Install, sign-in, add project, connect GitHub, configure agents, file locations
Finding: Install desktop/mobile/CLI, sign in (browser), add local dir via picker or npx lody project add, connect GitHub, add agent configs and Test them, run npx lody daemon start on servers. Local data under ~/.lody/repos and ~/.lody/logs.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/session/
Locator: Composer, fork, side chat, session list, archive/restore/delete, Quick Session, Open in editor
Finding: Sessions bundle conversation, branch and worktree; fork/side-chat reuse history; sidebar shows status, repo, branch, PR and diff stats; archive retains history and reclaims worktrees; restore recreates them; Quick Session desktop shortcut; Open-in launches VS Code/Xcode/Sublime/Zed (external launchers, not extensions).
Retrieved: 2026-11-13

Source: https://lody.ai/docs/session-tabs/
Locator: Child chats, file/diff tabs, tab management
Finding: Child chats share the parent session workspace (files/branch/uncommitted changes) with separate histories; file/diff tabs open beside chat; closing a tab does not stop the agent or remove the worktree.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/session-handoff/
Locator: Handoff steps, permissions table, live handoff vs share link, FAQ
Finding: Teammate joins the same live session (conversation, diffs, worktree) after workspace invite plus machine/project sharing; sharing may widen visibility to other conversations on that machine; transcript/markdown copy is a separate record-only action.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/team/
Locator: Invite, roles, member sessions, token usage by member, machine visibility
Finding: Invite by email with role; owners/admins manage members; All Tasks view with avatars; per-member token usage and trends; machines private by default, explicitly shared per machine; shared docs, mentions and task management are planned, not shipped.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/mobile/
Locator: Install, Live Activities, push notifications, progress/diff monitoring, offline support
Finding: Native iOS (App Store + TestFlight) and Android apps: notifications on task completion/approval/PR-ready, iOS Live Activities incl. actionable permission alerts, diff review and approvals, project file browsing; realtime editing is desktop-only; offline viewing of cached conversations with sync on reconnect.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/github/
Locator: GitHub App setup, issue/PR context, PR panel, auto-archive, commit/push, review sync
Finding: GitHub App gives repo access; issues/PRs inject context via @; PR panel shows state/CI/comments/reviews with in-Lody merge and branch delete; review comments sync both ways; PR-linked sessions auto-archive on merge/close; optional act-as-you identity for PR actions.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/agent-roles/
Locator: Role creation, sharing, mentions, offline-machine behavior
Finding: Roles package machine, agent config, model, reasoning, permission and instruction; private until shared with workspace; mentionable via @ to start new conversations; bound to one machine/config and unusable while offline.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/diff-viewer/
Locator: Round diffs, line comments, whole-conversation changes, remote review
Finding: Per-round diffs with changed line counts beside the agent message; file/diff tabs; whole-conversation Changes sidebar; remote devices read diffs through the session file provider with explicit loading states.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/diff-comments/
Locator: Threads, resolve, send-to-agent, GitHub sync
Finding: Line-level Markdown threads with reply/edit/delete/resolve; threads can be sent into the chat for the agent to address; PR-linked sessions sync both ways with GitHub PR review comments.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/workflow/
Locator: Small tasks, parallel sessions, AI review loop, archiving
Finding: One conversation per feature/fix (usually one PR); review round diffs; Create PR from the session; AI review loop on PR comments; archive (or auto-archive) when merged; non-GitHub projects skip PR/CI automation.
Retrieved: 2026-11-13

## lody:TEAM-06

Finding: A teammate takes over the identical live session — conversation, decisions, artifacts, worktree and runtime context — after invite plus machine/project sharing, with attribution and documented loss modes. Ownership transfer and cross-harness session migration are not established.

Verification: agent-cross-checked
Checked: 2026-11-13
Scheduled recheck: 2027-03-13
Plan: Not specified
Surface: Lody Electron desktop app; Lody hosted web app; Lody native iOS and Android apps
Version: v0.109.0 (commit 2eefb5e); source pass 2026-11-13

Only the cited atomic findings are established. Remaining atomic requirements and the full rubric scenario remain unverified.
No ownership-transfer flow or cross-harness session migration is documented.

Source: https://lody.ai/docs/session/
Locator: Composer, fork, side chat, session list, archive/restore/delete, Quick Session, Open in editor
Finding: Sessions bundle conversation, branch and worktree; fork/side-chat reuse history; sidebar shows status, repo, branch, PR and diff stats; archive retains history and reclaims worktrees; restore recreates them; Quick Session desktop shortcut; Open-in launches VS Code/Xcode/Sublime/Zed (external launchers, not extensions).
Retrieved: 2026-11-13

Source: https://lody.ai/docs/parallel-agents/
Locator: Isolated worktrees, mixed agents, team visibility, coordinator handoff, FAQ
Finding: Multiple sessions each with own worktree/branch; mix Claude Code/Codex/Kimi/Grok per session; team sees running sessions via All Tasks; concurrency limited by host machine capacity; agent-to-agent coordination via Agent Session Control.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/session-handoff/
Locator: Handoff steps, permissions table, live handoff vs share link, FAQ
Finding: Teammate joins the same live session (conversation, diffs, worktree) after workspace invite plus machine/project sharing; sharing may widen visibility to other conversations on that machine; transcript/markdown copy is a separate record-only action.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/team/
Locator: Invite, roles, member sessions, token usage by member, machine visibility
Finding: Invite by email with role; owners/admins manage members; All Tasks view with avatars; per-member token usage and trends; machines private by default, explicitly shared per machine; shared docs, mentions and task management are planned, not shipped.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/mobile/
Locator: Install, Live Activities, push notifications, progress/diff monitoring, offline support
Finding: Native iOS (App Store + TestFlight) and Android apps: notifications on task completion/approval/PR-ready, iOS Live Activities incl. actionable permission alerts, diff review and approvals, project file browsing; realtime editing is desktop-only; offline viewing of cached conversations with sync on reconnect.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/scheduled-tasks/
Locator: Triggers, owning machine, agent-proposed schedules, missed runs, FAQ
Finding: Scheduled/manual/one-shot tasks run on one owning machine (CLI, local timezone; nothing runs in cloud); agent can only propose schedules, never create them; missed runs catch up once; only the creator can edit/pause/delete; machine must be awake.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/worktrees/
Locator: Worktree layout, setup/cleanup scripts, env vars, retention and recovery
Finding: One branch (session/<id>) and worktree per session under ~/.lody/repos/<repoId>/; project setup/cleanup scripts with LODY_* env vars; archive/backup rules keep branches and stage pending changes, discard ignored files; restore recreates the worktree from the branch.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/agent-roles/
Locator: Role creation, sharing, mentions, offline-machine behavior
Finding: Roles package machine, agent config, model, reasoning, permission and instruction; private until shared with workspace; mentionable via @ to start new conversations; bound to one machine/config and unusable while offline.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/diff-comments/
Locator: Threads, resolve, send-to-agent, GitHub sync
Finding: Line-level Markdown threads with reply/edit/delete/resolve; threads can be sent into the chat for the agent to address; PR-linked sessions sync both ways with GitHub PR review comments.
Retrieved: 2026-11-13

## lody:SHIP-01

Finding: Round and whole-conversation diffs, images, previews, validation outputs and shareable HTML review reports persist per session with task and revision links. Documents, recordings and cross-task galleries do not exist.

Verification: agent-cross-checked
Checked: 2026-11-13
Scheduled recheck: 2027-03-13
Plan: Not specified
Surface: Lody Electron desktop app; Lody hosted web app; Lody native iOS and Android apps
Version: v0.109.0 (commit 2eefb5e); source pass 2026-11-13

Only the cited atomic findings are established. Remaining atomic requirements and the full rubric scenario remain unverified.
No document artifacts, recordings, or cross-task gallery exist; retention is per session plus archive.

Source: https://lody.ai/docs/cli/
Locator: Command reference: login, daemon, workspaces, sessions, machines, agent configs, review, export
Finding: lody CLI is both the daemon runtime (lody start / daemon start) and a one-shot manager: session create/chat/list/status, project/workspace/machine/agent-config commands, lody review prompting and rendering, lody export, import-magpie, --json output; built-in help is the flag source of truth.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/session/
Locator: Composer, fork, side chat, session list, archive/restore/delete, Quick Session, Open in editor
Finding: Sessions bundle conversation, branch and worktree; fork/side-chat reuse history; sidebar shows status, repo, branch, PR and diff stats; archive retains history and reclaims worktrees; restore recreates them; Quick Session desktop shortcut; Open-in launches VS Code/Xcode/Sublime/Zed (external launchers, not extensions).
Retrieved: 2026-11-13

Source: https://lody.ai/docs/session-orchestration/
Locator: Built-in Lody MCP tools: create/reuse, status, follow-up, cancel, model/reasoning selection
Finding: Agents use built-in Lody MCP tools to create/reuse conversations, read status and bounded history, send follow-ups, cancel running turns, select compatible model/reasoning, and bring results back; parent relationship preserved; bounded to Lody conversation data, not a background scheduler.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/agent-collaboration/
Locator: Orchestrator walkthrough: triage, cross-repo fix, review-fix loop, @ mentions
Finding: Primary agent triages PR/issue queues, delegates fixes/reviews to Kimi/Codex/Grok sessions across machines, exchanges findings via @ session mentions, and collects commits; examples are illustrative prompts, not benchmark results.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/mobile/
Locator: Install, Live Activities, push notifications, progress/diff monitoring, offline support
Finding: Native iOS (App Store + TestFlight) and Android apps: notifications on task completion/approval/PR-ready, iOS Live Activities incl. actionable permission alerts, diff review and approvals, project file browsing; realtime editing is desktop-only; offline viewing of cached conversations with sync on reconnect.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/github/
Locator: GitHub App setup, issue/PR context, PR panel, auto-archive, commit/push, review sync
Finding: GitHub App gives repo access; issues/PRs inject context via @; PR panel shows state/CI/comments/reviews with in-Lody merge and branch delete; review comments sync both ways; PR-linked sessions auto-archive on merge/close; optional act-as-you identity for PR actions.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/worktrees/
Locator: Worktree layout, setup/cleanup scripts, env vars, retention and recovery
Finding: One branch (session/<id>) and worktree per session under ~/.lody/repos/<repoId>/; project setup/cleanup scripts with LODY_* env vars; archive/backup rules keep branches and stage pending changes, discard ignored files; restore recreates the worktree from the branch.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/lody-review/
Locator: Review format, report contents, requirements, options
Finding: npx lody review renders a local Git review into a self-contained shareable HTML report without signing in; runs read-only against the local repo; first render may download and cache a verified viewer.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/diff-viewer/
Locator: Round diffs, line comments, whole-conversation changes, remote review
Finding: Per-round diffs with changed line counts beside the agent message; file/diff tabs; whole-conversation Changes sidebar; remote devices read diffs through the session file provider with explicit loading states.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/workflow/
Locator: Small tasks, parallel sessions, AI review loop, archiving
Finding: One conversation per feature/fix (usually one PR); review round diffs; Create PR from the session; AI review loop on PR comments; archive (or auto-archive) when merged; non-GitHub projects skip PR/CI automation.
Retrieved: 2026-11-13

Source: https://github.com/LodyAI/Lody/blob/v0.109.0/README.md
Locator: Share conversations, bring agents/machines, daemon, CLI, agent coordination, E2E, mobile credit
Finding: Shared workspace for coding agents teams already use; daemon connects machines; CLI manages sessions; agents coordinate via session tools; parallel worktrees and live diff review; local-first direction via Loro/Flock; mobile clients native with upstream credit.
Retrieved: 2026-11-13

Source: https://github.com/LodyAI/Lody/tree/v0.109.0/apps/cli/src/commands
Locator: session.ts, machine.ts, daemon.ts, agent-config.ts, github.ts, review.ts, export.ts, magpie-import.ts, internal.ts
Finding: CLI implements session/machine/daemon/agent-config/GitHub/review/export/magpie commands; no public REST API surface or SDK package in commands, packages or docs.
Retrieved: 2026-11-13

## lody:SHIP-02

Finding: Tests, lint, types and CI run through agents and surface in-session with review loops available, but every gate is optional and unenforced; spec conformance cannot exist without product specs.

Verification: agent-cross-checked
Checked: 2026-11-13
Scheduled recheck: 2027-03-13
Plan: Not specified
Surface: Lody Electron desktop app; Lody hosted web app; Lody CLI and daemon
Version: v0.109.0 (commit 2eefb5e); source pass 2026-11-13

Only the cited atomic findings are established. Remaining atomic requirements and the full rubric scenario remain unverified.
All checks are advisory; no required gate, failure blocking, or configured policy exists.

Source: https://lody.ai/docs/github/
Locator: GitHub App setup, issue/PR context, PR panel, auto-archive, commit/push, review sync
Finding: GitHub App gives repo access; issues/PRs inject context via @; PR panel shows state/CI/comments/reviews with in-Lody merge and branch delete; review comments sync both ways; PR-linked sessions auto-archive on merge/close; optional act-as-you identity for PR actions.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/lody-review/
Locator: Review format, report contents, requirements, options
Finding: npx lody review renders a local Git review into a self-contained shareable HTML report without signing in; runs read-only against the local repo; first render may download and cache a verified viewer.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/diff-viewer/
Locator: Round diffs, line comments, whole-conversation changes, remote review
Finding: Per-round diffs with changed line counts beside the agent message; file/diff tabs; whole-conversation Changes sidebar; remote devices read diffs through the session file provider with explicit loading states.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/workflow/
Locator: Small tasks, parallel sessions, AI review loop, archiving
Finding: One conversation per feature/fix (usually one PR); review round diffs; Create PR from the session; AI review loop on PR comments; archive (or auto-archive) when merged; non-GitHub projects skip PR/CI automation.
Retrieved: 2026-11-13

Source: https://github.com/LodyAI/Lody/blob/v0.109.0/README.md
Locator: Share conversations, bring agents/machines, daemon, CLI, agent coordination, E2E, mobile credit
Finding: Shared workspace for coding agents teams already use; daemon connects machines; CLI manages sessions; agents coordinate via session tools; parallel worktrees and live diff review; local-first direction via Loro/Flock; mobile clients native with upstream credit.
Retrieved: 2026-11-13

Source: https://github.com/LodyAI/Lody/tree/v0.109.0/apps/cli/src/commands
Locator: session.ts, machine.ts, daemon.ts, agent-config.ts, github.ts, review.ts, export.ts, magpie-import.ts, internal.ts
Finding: CLI implements session/machine/daemon/agent-config/GitHub/review/export/magpie commands; no public REST API surface or SDK package in commands, packages or docs.
Retrieved: 2026-11-13

## lody:SHIP-03

Finding: Branches, worktrees, commits, PR creation, review comments, CI response and merge run product-integrated through the GitHub App. Rebase and conflict handling are agent-side and undocumented as product flows.

Verification: agent-cross-checked
Checked: 2026-11-13
Scheduled recheck: 2027-03-13
Plan: Not specified
Surface: Lody Electron desktop app; Lody hosted web app; Lody CLI and daemon
Version: v0.109.0 (commit 2eefb5e); source pass 2026-11-13

Only the cited atomic findings are established. Remaining atomic requirements and the full rubric scenario remain unverified.
Rebase and conflict resolution have no product-integrated flow.

Source: https://lody.ai/docs/github/
Locator: GitHub App setup, issue/PR context, PR panel, auto-archive, commit/push, review sync
Finding: GitHub App gives repo access; issues/PRs inject context via @; PR panel shows state/CI/comments/reviews with in-Lody merge and branch delete; review comments sync both ways; PR-linked sessions auto-archive on merge/close; optional act-as-you identity for PR actions.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/worktrees/
Locator: Worktree layout, setup/cleanup scripts, env vars, retention and recovery
Finding: One branch (session/<id>) and worktree per session under ~/.lody/repos/<repoId>/; project setup/cleanup scripts with LODY_* env vars; archive/backup rules keep branches and stage pending changes, discard ignored files; restore recreates the worktree from the branch.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/local-project/
Locator: Adding projects, local-first availability, CLI history sync, team visibility, limitations
Finding: Any local directory works with synced chat/diffs/branches/worktrees; desktop works offline with later sync; imports Codex/Claude CLI history; team visibility is opt-in per project; local projects cannot push to remote branches directly.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/diff-comments/
Locator: Threads, resolve, send-to-agent, GitHub sync
Finding: Line-level Markdown threads with reply/edit/delete/resolve; threads can be sent into the chat for the agent to address; PR-linked sessions sync both ways with GitHub PR review comments.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/workflow/
Locator: Small tasks, parallel sessions, AI review loop, archiving
Finding: One conversation per feature/fix (usually one PR); review round diffs; Create PR from the session; AI review loop on PR comments; archive (or auto-archive) when merged; non-GitHub projects skip PR/CI automation.
Retrieved: 2026-11-13

Source: https://github.com/LodyAI/Lody/tree/v0.109.0/apps/cli/src/commands
Locator: session.ts, machine.ts, daemon.ts, agent-config.ts, github.ts, review.ts, export.ts, magpie-import.ts, internal.ts
Finding: CLI implements session/machine/daemon/agent-config/GitHub/review/export/magpie commands; no public REST API surface or SDK package in commands, packages or docs.
Retrieved: 2026-11-13

## lody:SHIP-04

Finding: PRs merge from Lody (optionally as the GitHub user) with branch cleanup; approvals surface as comments and reviews without a distinct approve authority, and release or deploy authority does not exist.

Verification: agent-cross-checked
Checked: 2026-11-13
Scheduled recheck: 2027-03-13
Plan: Not specified
Surface: Lody Electron desktop app; Lody hosted web app
Version: v0.109.0 (commit 2eefb5e); source pass 2026-11-13

Only the cited atomic findings are established. Remaining atomic requirements and the full rubric scenario remain unverified.
No release, deploy, or exact-revision approval semantics are documented.

Source: https://lody.ai/price/
Locator: Plan cards, feature table, FAQ (tokens, seats, cancellation)
Finding: Free ($0 forever: 2 workspaces, 200 sessions/workspace, 30 turns/session, 3 members) vs Plus ($8/seat/month billed yearly, unlimited) vs Enterprise (custom; SSO, procurement, rollout). No AI token charges; BYO agent accounts at zero markup. Prices USD; yearly upfront per seat for 12 months.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/github/
Locator: GitHub App setup, issue/PR context, PR panel, auto-archive, commit/push, review sync
Finding: GitHub App gives repo access; issues/PRs inject context via @; PR panel shows state/CI/comments/reviews with in-Lody merge and branch delete; review comments sync both ways; PR-linked sessions auto-archive on merge/close; optional act-as-you identity for PR actions.
Retrieved: 2026-11-13

Source: https://github.com/LodyAI/Lody/tree/v0.109.0/apps/cli/src/commands
Locator: session.ts, machine.ts, daemon.ts, agent-config.ts, github.ts, review.ts, export.ts, magpie-import.ts, internal.ts
Finding: CLI implements session/machine/daemon/agent-config/GitHub/review/export/magpie commands; no public REST API surface or SDK package in commands, packages or docs.
Retrieved: 2026-11-13

## lody:SHIP-05

Finding: Task-to-commit/PR links, delivery status and retained review evidence persist per session; rollback and stale-approval invalidation do not exist (the only revert in-tree is internal session-create cleanup).

Verification: agent-cross-checked
Checked: 2026-11-13
Scheduled recheck: 2027-03-13
Plan: Not specified
Surface: Lody Electron desktop app; Lody hosted web app
Version: v0.109.0 (commit 2eefb5e); source pass 2026-11-13

Only the cited atomic findings are established. Remaining atomic requirements and the full rubric scenario remain unverified.
No rollback, revert, or stale-approval invalidation is documented.

Source: https://lody.ai/docs/session/
Locator: Composer, fork, side chat, session list, archive/restore/delete, Quick Session, Open in editor
Finding: Sessions bundle conversation, branch and worktree; fork/side-chat reuse history; sidebar shows status, repo, branch, PR and diff stats; archive retains history and reclaims worktrees; restore recreates them; Quick Session desktop shortcut; Open-in launches VS Code/Xcode/Sublime/Zed (external launchers, not extensions).
Retrieved: 2026-11-13

Source: https://lody.ai/docs/github/
Locator: GitHub App setup, issue/PR context, PR panel, auto-archive, commit/push, review sync
Finding: GitHub App gives repo access; issues/PRs inject context via @; PR panel shows state/CI/comments/reviews with in-Lody merge and branch delete; review comments sync both ways; PR-linked sessions auto-archive on merge/close; optional act-as-you identity for PR actions.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/worktrees/
Locator: Worktree layout, setup/cleanup scripts, env vars, retention and recovery
Finding: One branch (session/<id>) and worktree per session under ~/.lody/repos/<repoId>/; project setup/cleanup scripts with LODY_* env vars; archive/backup rules keep branches and stage pending changes, discard ignored files; restore recreates the worktree from the branch.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/diff-comments/
Locator: Threads, resolve, send-to-agent, GitHub sync
Finding: Line-level Markdown threads with reply/edit/delete/resolve; threads can be sent into the chat for the agent to address; PR-linked sessions sync both ways with GitHub PR review comments.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/workflow/
Locator: Small tasks, parallel sessions, AI review loop, archiving
Finding: One conversation per feature/fix (usually one PR); review round diffs; Create PR from the session; AI review loop on PR comments; archive (or auto-archive) when merged; non-GitHub projects skip PR/CI automation.
Retrieved: 2026-11-13

Source: https://github.com/LodyAI/Lody/tree/v0.109.0/apps/cli/src/commands
Locator: session.ts, machine.ts, daemon.ts, agent-config.ts, github.ts, review.ts, export.ts, magpie-import.ts, internal.ts
Finding: CLI implements session/machine/daemon/agent-config/GitHub/review/export/magpie commands; no public REST API surface or SDK package in commands, packages or docs.
Retrieved: 2026-11-13

Source: https://github.com/LodyAI/Lody/blob/v0.109.0/apps/cli/src/orchestration/README.md
Locator: Coordinator workflow, inbox, session-create rollback point-of-no-return
Finding: Orchestration layer runs coordinator workflows over sessions with an inbox; session-create has a documented point-of-no-rollback for cleanup only (not user-facing revert); no merge queue, batch-review queue or duplicate-task detection.
Retrieved: 2026-11-13

## lody:SHIP-06

Finding: The session list with per-item summaries, grouping, review threads and per-session ship actions supports high-volume review item by item; risk filters, merge queues, revision-locked approvals and check deduplication do not exist.

Verification: agent-cross-checked
Checked: 2026-11-13
Scheduled recheck: 2027-03-13
Plan: Not specified
Surface: Lody Electron desktop app; Lody hosted web app
Version: v0.109.0 (commit 2eefb5e); source pass 2026-11-13

Only the cited atomic findings are established. Remaining atomic requirements and the full rubric scenario remain unverified.
No queue-level automation: every ship action is per session.

Source: https://lody.ai/docs/session/
Locator: Composer, fork, side chat, session list, archive/restore/delete, Quick Session, Open in editor
Finding: Sessions bundle conversation, branch and worktree; fork/side-chat reuse history; sidebar shows status, repo, branch, PR and diff stats; archive retains history and reclaims worktrees; restore recreates them; Quick Session desktop shortcut; Open-in launches VS Code/Xcode/Sublime/Zed (external launchers, not extensions).
Retrieved: 2026-11-13

Source: https://lody.ai/docs/github/
Locator: GitHub App setup, issue/PR context, PR panel, auto-archive, commit/push, review sync
Finding: GitHub App gives repo access; issues/PRs inject context via @; PR panel shows state/CI/comments/reviews with in-Lody merge and branch delete; review comments sync both ways; PR-linked sessions auto-archive on merge/close; optional act-as-you identity for PR actions.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/diff-viewer/
Locator: Round diffs, line comments, whole-conversation changes, remote review
Finding: Per-round diffs with changed line counts beside the agent message; file/diff tabs; whole-conversation Changes sidebar; remote devices read diffs through the session file provider with explicit loading states.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/diff-comments/
Locator: Threads, resolve, send-to-agent, GitHub sync
Finding: Line-level Markdown threads with reply/edit/delete/resolve; threads can be sent into the chat for the agent to address; PR-linked sessions sync both ways with GitHub PR review comments.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/workflow/
Locator: Small tasks, parallel sessions, AI review loop, archiving
Finding: One conversation per feature/fix (usually one PR); review round diffs; Create PR from the session; AI review loop on PR comments; archive (or auto-archive) when merged; non-GitHub projects skip PR/CI automation.
Retrieved: 2026-11-13

Source: https://github.com/LodyAI/Lody/blob/v0.109.0/apps/cli/src/orchestration/README.md
Locator: Coordinator workflow, inbox, session-create rollback point-of-no-return
Finding: Orchestration layer runs coordinator workflows over sessions with an inbox; session-create has a documented point-of-no-rollback for cleanup only (not user-facing revert); no merge queue, batch-review queue or duplicate-task detection.
Retrieved: 2026-11-13

## lody:OWN-01

Finding: Pinned release tree (CLI, desktop, packages, docs) is Apache-2.0; native mobile client code post-dates the pin with upstream credit, and the vendor sync backend stays closed.

Verification: agent-cross-checked
Checked: 2026-11-13
Scheduled recheck: 2027-05-12
Plan: Not specified
Surface: Lody Electron desktop app; Lody CLI and daemon
Version: v0.109.0 (commit 2eefb5e); source pass 2026-11-13

Mobile client code post-dates v0.109.0; the hosted sync/relay backend is closed.
Repository visibility is not proof of hosted parity.

Source: https://lody.ai/docs/github/
Locator: GitHub App setup, issue/PR context, PR panel, auto-archive, commit/push, review sync
Finding: GitHub App gives repo access; issues/PRs inject context via @; PR panel shows state/CI/comments/reviews with in-Lody merge and branch delete; review comments sync both ways; PR-linked sessions auto-archive on merge/close; optional act-as-you identity for PR actions.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/encrypted-workspaces/
Locator: Standard vs encrypted comparison, device approval, recovery, known limits
Finding: In E2E workspaces only authorized devices can read content; servers relay/store unreadable data; new devices need approval; loss of all devices plus recovery file means permanent loss; browser security depends on served code; price page flags E2E as coming soon on Plus.
Retrieved: 2026-11-13

Source: https://api.github.com/repos/LodyAI/Lody
Locator: stargazers_count, license, pushed_at, topics, homepage
Finding: 1,733 stars; Apache-2.0 license; default branch main, pushed 2026-11-13; homepage https://lody.ai; topics include multi-agent, orchestration, collaboration, local-first. Brief URL github.com/eneskirca/lody returns 404; canonical repo is LodyAI/Lody.
Retrieved: 2026-11-13

Source: https://github.com/LodyAI/Lody/releases/tag/v0.109.0
Locator: Tag, publication date, changelog entries
Finding: Latest release v0.109.0 published 2026-10-30; tag commit e7b7ab7aacf17f3ee056a6d708ad5ac3c18fb60f resolving to commit 2eefb5e0071d2944b40716ab63ec95cd83cada25; release notes list renderer, presence and daemon fixes.
Retrieved: 2026-11-13

Source: https://github.com/LodyAI/Lody/blob/HEAD/apps/mobile/README.md
Locator: Native clients, setup/scope, credits and origins
Finding: New native iOS and Android clients under active development with independent build toolchains; iOS built directly on Innei lody-ios with provenance-tracked runtime snapshot reused on Android; mobile client code landed after pinned release v0.109.0.
Retrieved: 2026-11-13

Source: https://github.com/LodyAI/Lody/blob/v0.109.0/LICENSE
Locator: Root LICENSE file, Apache grant header
Finding: Root LICENSE is Apache License 2.0 covering the pinned release tree (apps/cli, apps/electron, packages/*, site-docs); hosted sync backend and store-distributed mobile builds are outside this grant.
Retrieved: 2026-11-13

## lody:OWN-02

Finding: Apache source, workspace export with JSON/offline support, Markdown/HTML portability and email-driven account deletion cover exit; vendor services (Convex sync, GitHub App, push) are required for cloud workspaces while local-only use and lody review work independently.

Verification: agent-cross-checked
Checked: 2026-11-13
Scheduled recheck: 2027-05-12
Plan: Not specified
Surface: Lody Electron desktop app; Lody CLI and daemon; Lody hosted web app
Version: v0.109.0 (commit 2eefb5e); source pass 2026-11-13

Only the cited atomic findings are established. Remaining atomic requirements and the full rubric scenario remain unverified.
Cancellation mechanics, import tooling and task/history portability formats beyond export are not documented.

Source: https://lody.ai/docs/cli/
Locator: Command reference: login, daemon, workspaces, sessions, machines, agent configs, review, export
Finding: lody CLI is both the daemon runtime (lody start / daemon start) and a one-shot manager: session create/chat/list/status, project/workspace/machine/agent-config commands, lody review prompting and rendering, lody export, import-magpie, --json output; built-in help is the flag source of truth.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/lody-review/
Locator: Review format, report contents, requirements, options
Finding: npx lody review renders a local Git review into a self-contained shareable HTML report without signing in; runs read-only against the local repo; first render may download and cache a verified viewer.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/magpie/
Locator: Import targets, gateway, statuses, model management
Finding: One command imports Magpie provider setups (Claude, Codex, Pi, DSH, Kimi, Grok, Bub) on the same server; upstream API keys stay in Magpie; import does not prove inference works; cloud workspaces only, not OSS local-only mode.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/local-project/
Locator: Adding projects, local-first availability, CLI history sync, team visibility, limitations
Finding: Any local directory works with synced chat/diffs/branches/worktrees; desktop works offline with later sync; imports Codex/Claude CLI history; team visibility is opt-in per project; local projects cannot push to remote branches directly.
Retrieved: 2026-11-13

Source: https://lody.ai/privacy/
Locator: Data collected, subprocessors, retention/deletion, rights
Finding: Controller LoroHub LLC; collects account/auth data, device/diagnostics, service logs, conversation content; subprocessors Cloudflare, Convex, GitHub, Google Analytics, PostHog, Sentry; export/deletion on request with 30-day clearance; no explicit model-training use stated; no telemetry opt-out control documented.
Retrieved: 2026-11-13

Source: https://lody.ai/support/
Locator: Contact channels, response expectation, bug-report guidance
Finding: Support via email, Discord and X (@lody_ai); responds typically within a couple of business days; no response-time commitment; bug reports should include platform and repro steps.
Retrieved: 2026-11-13

Source: https://github.com/LodyAI/Lody/blob/v0.109.0/LICENSE
Locator: Root LICENSE file, Apache grant header
Finding: Root LICENSE is Apache License 2.0 covering the pinned release tree (apps/cli, apps/electron, packages/*, site-docs); hosted sync backend and store-distributed mobile builds are outside this grant.
Retrieved: 2026-11-13

Source: https://github.com/LodyAI/Lody/blob/v0.109.0/apps/cli/src/commands/export.ts
Locator: exportWorkspaceData, --json, offline support
Finding: lody export writes workspace data (sessions, images optional) with --json and offline support; account/data deletion is an email request flow per site-docs account-deletion page.
Retrieved: 2026-11-13

## lody:OWN-03

Finding: LoroHub LLC collects account, device, log and conversation data processed by named subprocessors with export/deletion rights; E2E workspaces restrict reads to authorized devices, while standard workspaces are readable by members and Lody servers. Telemetry is disclosed (PostHog/Sentry/GA) with no documented opt-out or first-run consent.

Verification: agent-cross-checked
Checked: 2026-11-13
Scheduled recheck: 2027-03-13
Plan: Not specified
Surface: Lody Electron desktop app; Lody hosted web app; Lody native iOS and Android apps; Lody CLI and daemon
Version: v0.109.0 (commit 2eefb5e); source pass 2026-11-13

Price-page E2E is flagged coming soon on Plus while E2E docs describe the mechanism; treated as available-with-limitation, not GA-guaranteed.
No telemetry opt-out, first-run consent prompt, residency statement, or model-training position is documented.

Source: https://lody.ai/docs/quickstart/
Locator: Install, sign-in, add project, connect GitHub, configure agents, file locations
Finding: Install desktop/mobile/CLI, sign in (browser), add local dir via picker or npx lody project add, connect GitHub, add agent configs and Test them, run npx lody daemon start on servers. Local data under ~/.lody/repos and ~/.lody/logs.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/cli/
Locator: Command reference: login, daemon, workspaces, sessions, machines, agent configs, review, export
Finding: lody CLI is both the daemon runtime (lody start / daemon start) and a one-shot manager: session create/chat/list/status, project/workspace/machine/agent-config commands, lody review prompting and rendering, lody export, import-magpie, --json output; built-in help is the flag source of truth.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/mobile/
Locator: Install, Live Activities, push notifications, progress/diff monitoring, offline support
Finding: Native iOS (App Store + TestFlight) and Android apps: notifications on task completion/approval/PR-ready, iOS Live Activities incl. actionable permission alerts, diff review and approvals, project file browsing; realtime editing is desktop-only; offline viewing of cached conversations with sync on reconnect.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/encrypted-workspaces/
Locator: Standard vs encrypted comparison, device approval, recovery, known limits
Finding: In E2E workspaces only authorized devices can read content; servers relay/store unreadable data; new devices need approval; loss of all devices plus recovery file means permanent loss; browser security depends on served code; price page flags E2E as coming soon on Plus.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/encrypted-workspaces-ledger/
Locator: Signed records, hash chain, member/device authorization
Finding: Permission ledger holds signed membership/device records in a hash chain that devices verify; the server cannot quietly add members; execution grants are memory-only and checked against current membership.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/magpie/
Locator: Import targets, gateway, statuses, model management
Finding: One command imports Magpie provider setups (Claude, Codex, Pi, DSH, Kimi, Grok, Bub) on the same server; upstream API keys stay in Magpie; import does not prove inference works; cloud workspaces only, not OSS local-only mode.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/from-codex-claude-code/
Locator: What stays the same, concept mapping, migration checklist, FAQ
Finding: Lody launches the same provider CLIs and reuses machine-side subscription logins, API env config, and repo instruction files (AGENTS.md/CLAUDE.md); sessions resume like --resume; CLI remains supported for quick one-off edits.
Retrieved: 2026-11-13

Source: https://lody.ai/privacy/
Locator: Data collected, subprocessors, retention/deletion, rights
Finding: Controller LoroHub LLC; collects account/auth data, device/diagnostics, service logs, conversation content; subprocessors Cloudflare, Convex, GitHub, Google Analytics, PostHog, Sentry; export/deletion on request with 30-day clearance; no explicit model-training use stated; no telemetry opt-out control documented.
Retrieved: 2026-11-13

Source: https://lody.ai/terms/
Locator: Provider, sign-in, fees/billing, account rules
Finding: Provider LoroHub LLC; sign-in via GitHub OAuth; free and paid (Plus) plans with prices on the pricing page in USD; user retains content ownership with a services-only license grant.
Retrieved: 2026-11-13

Source: https://lody.ai/support/
Locator: Contact channels, response expectation, bug-report guidance
Finding: Support via email, Discord and X (@lody_ai); responds typically within a couple of business days; no response-time commitment; bug reports should include platform and repro steps.
Retrieved: 2026-11-13

Source: https://github.com/LodyAI/Lody/tree/v0.109.0/apps/cli/src/mcp
Locator: lody-mcp-server.ts (@modelcontextprotocol/server), lody-mcp-http-server.ts, session-mcp-resolver.ts, schedule-tools.ts, agent-role-tools.ts, authentication/
Finding: Lody hosts its own MCP server (session/daemon/schedule/role tools over stdio and HTTP loopback) for agents, and resolves the workspace MCP catalog plus OAuth/keychain credentials into ACP sessions as an MCP client.
Retrieved: 2026-11-13

Source: https://github.com/LodyAI/Lody/blob/v0.109.0/apps/cli/README.md
Locator: authorizeExecution, owner/admin/member device grants, journal reset
Finding: Encrypted workspaces authorize execution per workspace/device with owner/admin/member grants, sub-15-minute memory-only grants, and offline journal reset; UI account IDs grant nothing; guest/recovery/removed/revoked devices do not qualify.
Retrieved: 2026-11-13

## lody:OWN-04

Finding: Prices are USD: Free is $0 forever; Plus is $10 per seat per month billed monthly, or $8 per seat per month billed yearly; Enterprise is custom. Free includes 2 workspaces, 200 sessions per workspace, 30 turns per session and up to 3 members. Lody charges for the collaboration workspace, while users supply agent/model accounts at zero markup.

Verification: sourced
Checked: 2026-11-13
Scheduled recheck: 2027-01-12
Plan: Not specified
Surface: Lody Electron desktop app; Lody hosted web app; Lody native iOS and Android apps
Version: Lody v0.109.0 (e7b7ab7aacf17f3ee056a6d708ad5ac3c18fb60f); targeted first-party pass 2026-11-13; no installed-product test

The scoped first-party source pass does not establish seat_minimum, taxes. No hands-on scenario was run.

Source: https://lody.ai/price/
Locator: Plan cards, feature table, FAQ (tokens, seats, cancellation)
Finding: Free ($0 forever: 2 workspaces, 200 sessions/workspace, 30 turns/session, 3 members) vs Plus ($8/seat/month billed yearly, unlimited) vs Enterprise (custom; SSO, procurement, rollout). No AI token charges; BYO agent accounts at zero markup. Prices USD; yearly upfront per seat for 12 months.
Retrieved: 2026-11-13

Source: https://lody.ai/terms/
Locator: Provider, sign-in, fees/billing, account rules
Finding: Provider LoroHub LLC; sign-in via GitHub OAuth; free and paid (Plus) plans with prices on the pricing page in USD; user retains content ownership with a services-only license grant.
Retrieved: 2026-11-13

Source: https://github.com/LodyAI/Lody/blob/e7b7ab7aacf17f3ee056a6d708ad5ac3c18fb60f/site-docs/components/pricing-page.tsx
Locator: REGULAR_PLUS_MONTHLY; Plus monthly amount and Billed monthly branch, lines 106-169
Finding: The public pricing page implements a Monthly/Yearly toggle. Its monthly branch uses a USD 10 per-seat Plus list price billed monthly; the initial USD 8 display is billed yearly and is not converted into a monthly-paid price.
Retrieved: 2026-11-13

## lody:OWN-05

Finding: One developer: $0 (Free) or $96/year (Plus yearly); two: $0 or $192/year; five: Plus $480/year (Free caps at 3 members). Model and compute costs are BYO and unknown; no fixed task/token/hour assumptions are published.

Verification: agent-cross-checked
Checked: 2026-11-13
Scheduled recheck: 2027-01-12
Plan: Not specified
Surface: Lody Electron desktop app; Lody hosted web app
Version: v0.109.0 (commit 2eefb5e); source pass 2026-11-13

No vendor task cost, token, or compute-hour figures exist; scenario totals cover workspace seats only.

Source: https://lody.ai/price/
Locator: Plan cards, feature table, FAQ (tokens, seats, cancellation)
Finding: Free ($0 forever: 2 workspaces, 200 sessions/workspace, 30 turns/session, 3 members) vs Plus ($8/seat/month billed yearly, unlimited) vs Enterprise (custom; SSO, procurement, rollout). No AI token charges; BYO agent accounts at zero markup. Prices USD; yearly upfront per seat for 12 months.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/parallel-agents/
Locator: Isolated worktrees, mixed agents, team visibility, coordinator handoff, FAQ
Finding: Multiple sessions each with own worktree/branch; mix Claude Code/Codex/Kimi/Grok per session; team sees running sessions via All Tasks; concurrency limited by host machine capacity; agent-to-agent coordination via Agent Session Control.
Retrieved: 2026-11-13

## lody:OWN-06

Finding: Publicly downloadable with email/Discord/X support (typically days, no commitment), active releases (v0.109.0 on 2026-10-30, pushes through 2026-11-13) and email-driven export/deletion. No staged rollout, status history, or deprecation program is documented.

Verification: agent-cross-checked
Checked: 2026-11-13
Scheduled recheck: 2027-01-12
Plan: Not specified
Surface: Lody Electron desktop app; Lody hosted web app; Lody native iOS and Android apps
Version: v0.109.0 (commit 2eefb5e); source pass 2026-11-13

Only the cited atomic findings are established. Remaining atomic requirements and the full rubric scenario remain unverified.
No status page, SLA, or deprecation policy is documented.

Source: https://lody.ai/download/
Locator: Desktop, Mobile and browser, Browser sections
Finding: Desktop: macOS Universal (Apple Silicon and Intel), Windows x64, Linux AppImage and Debian/Ubuntu x86-64. Mobile: iOS App Store, Android Google Play and signed APK. Browser: hosted web app. This page presents the complete client list.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/mobile/
Locator: Install, Live Activities, push notifications, progress/diff monitoring, offline support
Finding: Native iOS (App Store + TestFlight) and Android apps: notifications on task completion/approval/PR-ready, iOS Live Activities incl. actionable permission alerts, diff review and approvals, project file browsing; realtime editing is desktop-only; offline viewing of cached conversations with sync on reconnect.
Retrieved: 2026-11-13

Source: https://api.github.com/repos/LodyAI/Lody
Locator: stargazers_count, license, pushed_at, topics, homepage
Finding: 1,733 stars; Apache-2.0 license; default branch main, pushed 2026-11-13; homepage https://lody.ai; topics include multi-agent, orchestration, collaboration, local-first. Brief URL github.com/eneskirca/lody returns 404; canonical repo is LodyAI/Lody.
Retrieved: 2026-11-13

Source: https://github.com/LodyAI/Lody/releases/tag/v0.109.0
Locator: Tag, publication date, changelog entries
Finding: Latest release v0.109.0 published 2026-10-30; tag commit e7b7ab7aacf17f3ee056a6d708ad5ac3c18fb60f resolving to commit 2eefb5e0071d2944b40716ab63ec95cd83cada25; release notes list renderer, presence and daemon fixes.
Retrieved: 2026-11-13

Source: https://lody.ai/privacy/
Locator: Data collected, subprocessors, retention/deletion, rights
Finding: Controller LoroHub LLC; collects account/auth data, device/diagnostics, service logs, conversation content; subprocessors Cloudflare, Convex, GitHub, Google Analytics, PostHog, Sentry; export/deletion on request with 30-day clearance; no explicit model-training use stated; no telemetry opt-out control documented.
Retrieved: 2026-11-13

Source: https://lody.ai/support/
Locator: Contact channels, response expectation, bug-report guidance
Finding: Support via email, Discord and X (@lody_ai); responds typically within a couple of business days; no response-time commitment; bug reports should include platform and repro steps.
Retrieved: 2026-11-13

Source: https://lody.ai/changelog/
Locator: Dated release notes entries
Finding: Dated bilingual release notes with recent entries (e.g. 2026-10-15 desktop sign-in fixes; 2026-04-22 PR panel); documents active maintenance alongside GitHub releases.
Retrieved: 2026-11-13

Source: https://github.com/LodyAI/Lody/blob/v0.109.0/apps/cli/src/commands/export.ts
Locator: exportWorkspaceData, --json, offline support
Finding: lody export writes workspace data (sessions, images optional) with --json and offline support; account/data deletion is an email request flow per site-docs account-deletion page.
Retrieved: 2026-11-13

## lody:OWN-08

Finding: Free plan is ongoing ($0, no trial clock) with mobile, BYOK, 3 members, scheduled tasks and handoff-capable sharing; two-person collaboration fits, five-person needs Plus. Card requirements and paid-evaluation needs are not documented.

Verification: agent-cross-checked
Checked: 2026-11-13
Scheduled recheck: 2027-01-12
Plan: Not specified
Surface: Lody Electron desktop app; Lody hosted web app; Lody native iOS and Android apps
Version: v0.109.0 (commit 2eefb5e); source pass 2026-11-13

Only the cited atomic findings are established. Remaining atomic requirements and the full rubric scenario remain unverified.
Card requirements and any paid-evaluation threshold are undocumented.

Source: https://lody.ai/download/
Locator: Desktop, Mobile and browser, Browser sections
Finding: Desktop: macOS Universal (Apple Silicon and Intel), Windows x64, Linux AppImage and Debian/Ubuntu x86-64. Mobile: iOS App Store, Android Google Play and signed APK. Browser: hosted web app. This page presents the complete client list.
Retrieved: 2026-11-13

Source: https://lody.ai/price/
Locator: Plan cards, feature table, FAQ (tokens, seats, cancellation)
Finding: Free ($0 forever: 2 workspaces, 200 sessions/workspace, 30 turns/session, 3 members) vs Plus ($8/seat/month billed yearly, unlimited) vs Enterprise (custom; SSO, procurement, rollout). No AI token charges; BYO agent accounts at zero markup. Prices USD; yearly upfront per seat for 12 months.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/session-handoff/
Locator: Handoff steps, permissions table, live handoff vs share link, FAQ
Finding: Teammate joins the same live session (conversation, diffs, worktree) after workspace invite plus machine/project sharing; sharing may widen visibility to other conversations on that machine; transcript/markdown copy is a separate record-only action.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/mobile/
Locator: Install, Live Activities, push notifications, progress/diff monitoring, offline support
Finding: Native iOS (App Store + TestFlight) and Android apps: notifications on task completion/approval/PR-ready, iOS Live Activities incl. actionable permission alerts, diff review and approvals, project file browsing; realtime editing is desktop-only; offline viewing of cached conversations with sync on reconnect.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/scheduled-tasks/
Locator: Triggers, owning machine, agent-proposed schedules, missed runs, FAQ
Finding: Scheduled/manual/one-shot tasks run on one owning machine (CLI, local timezone; nothing runs in cloud); agent can only propose schedules, never create them; missed runs catch up once; only the creator can edit/pause/delete; machine must be awake.
Retrieved: 2026-11-13

Source: https://lody.ai/docs/local-project/
Locator: Adding projects, local-first availability, CLI history sync, team visibility, limitations
Finding: Any local directory works with synced chat/diffs/branches/worktrees; desktop works offline with later sync; imports Codex/Claude CLI history; team visibility is opt-in per project; local projects cannot push to remote branches directly.
Retrieved: 2026-11-13

## lody:OWN-09

Finding: Pricing states per-seat subscription units with included limits and zero token/compute markup, but the monthly-cadence figure, minimum commitment, cancellation mechanics and tax handling are missing: partially specified.

Verification: agent-cross-checked
Checked: 2026-11-13
Scheduled recheck: 2027-01-12
Plan: Not specified
Surface: Lody Electron desktop app; Lody hosted web app
Version: v0.109.0 (commit 2eefb5e); source pass 2026-11-13

Monthly Plus figure, minimum commitment, cancellation mechanics, taxes and sales-only unknowns are not captured.
No usage-based billing exists, so overage and markup rates are structurally absent rather than hidden.

Source: https://lody.ai/price/
Locator: Plan cards, feature table, FAQ (tokens, seats, cancellation)
Finding: Free ($0 forever: 2 workspaces, 200 sessions/workspace, 30 turns/session, 3 members) vs Plus ($8/seat/month billed yearly, unlimited) vs Enterprise (custom; SSO, procurement, rollout). No AI token charges; BYO agent accounts at zero markup. Prices USD; yearly upfront per seat for 12 months.
Retrieved: 2026-11-13

Source: https://lody.ai/terms/
Locator: Provider, sign-in, fees/billing, account rules
Finding: Provider LoroHub LLC; sign-in via GitHub OAuth; free and paid (Plus) plans with prices on the pricing page in USD; user retains content ownership with a services-only license grant.
Retrieved: 2026-11-13