50 of 51 criteria have a sourced finding; 49 were also cross-checked by a second agent. Every comparison that includes lemon links here for scope, limitations, atomic answers and sources.
Humans approve the rubric, templates and prototype; they do not review every finding. An agent source cross-check is not a hands-on product test. A missing sourced finding is not evidence that a capability is absent.
Terminal TUI and one-shot CLI on macOS Apple Silicon and Linux (glibc 2.39+); Phoenix browser workspace with phone-width layout; Telegram and Discord text channels; Lemon Bot (separate product) with React web, macOS and iOS SwiftUI apps. Native Windows, macOS Intel and Android are unsupported or absent; the Mac DMG is unpublished.
Scope
Surfaces: Lemon TUI (terminal), Lemon web workspace (Phoenix, browser), Lemon Bot (web, macOS and iOS apps; separate product in the same repository), lemon CLI (one-shot, doctor, setup, omp, mcp), Telegram and Discord channels · Version: release v2026.11.11 (2026-11-14, commit 4d94b3c) · Plan: Open source (MIT), self-hosted; user pays model providers and hosts · OS: macOS (Apple Silicon), Linux (glibc 2.39+) · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
Prebuilt releases only for Apple Silicon macOS and Linux; Mac/iOS Bot apps are built from source or pending distribution; no Android app.
9 atomic answers
Desktop os [partial] Prebuilt releases for Apple Silicon macOS and Linux x86_64/ARM64 (glibc 2.39+); macOS Intel and native Windows have no builds; the Lemon Bot Mac app builds from source and the signed DMG is unpublished. Sources: lemon:install, lemon:readme, lemon:apple.
Mobile apps [partial] Lemon Bot has a SwiftUI iOS app (QR pairing, camera, share extension) with App Store release tooling; no Android app; Telegram/Discord are other phone routes. Sources: lemon:botreadme, lemon:apple, lemon:srch-android.
Browser [supported] `lemon web` Phoenix workspace (diffs, tool cards, automation boards, usage, command palette) and the Lemon Bot React web app. Sources: lemon:readme, lemon:web, lemon:botreadme.
Mobile browser [supported] Web workspace has responsive layouts down to phone width and Bot web is a responsive workspace; docs/user-guide/phone-acceptance.md covers phone acceptance. Sources: lemon:web, lemon:botreadme.
Editor extensions [partial] No IDE extension; Tern panes and ACP chat surface editor locations, and a browser-node extension exists for browser automation. Sources: lemon:tern, lemon:readme.
Task actions [supported] Start, follow-up, steer, redirect, cancel, resume and approve from TUI, web and Telegram/Discord (/steer, /cancel, /resume, approval buttons). Sources: lemon:readme, lemon:support.
Notifications [partial] Telegram/Discord messages, Bot Web Push/APNs and heartbeats; TUI shows approval notifications. Sources: lemon:botreadme, lemon:reminders.
Cross device continuity [supported] Sessions persist in the daemon and are reachable from every surface (start on Telegram, review in web). Sources: lemon:readme, lemon:arch.
Lemon runs its own native agent for every top-level run (engine "lemon" is provenance only), spawns native child sessions, and can delegate to omp (oh-my-pi) as an external agent; vendor harness engines (Claude Code, Codex) are not selectable. Models come from many providers.
Scope
Surfaces: Lemon TUI (terminal), Lemon web workspace (Phoenix, browser), lemon CLI (one-shot, doctor, setup, omp, mcp) · Version: release v2026.11.11 (2026-11-14, commit 4d94b3c) · Plan: Open source (MIT), self-hosted; user pays model providers and hosts · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: native lemon agent; omp delegate
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
Only one embedded harness plus omp delegation; no Claude Code/Codex/Cursor harness.
5 atomic answers
Harnesses [partial] Native Lemon agent is the only top-level executor; omp is a delegate driver ("not Lemon engine"); historical vendor resume tokens cannot select or resume top-level execution. Sources: lemon:arch, lemon:omp.
Model providers [supported] Anthropic, OpenAI, Gemini/Vertex, Bedrock, Azure, Mistral, OpenRouter, Groq, DeepSeek, xAI, Kimi, Qwen and any OpenAI-compatible endpoint including local models. Sources: lemon:readme, lemon:config.
Custom adapters [partial] Custom personas in .lemon/agents/, extensions/skills and MCP tools; delegate drivers (omp) are built into lemon_omp; no documented third-party engine adapter. Sources: lemon:readme, lemon:arch.
Session integration [supported] Embedded harness (coding_agent via lemon_agent/lemon_ai) and omp controlled over its structured RPC protocol (omp --mode rpc). Sources: lemon:arch, lemon:omp.
Mixed harness operation [supported] Lemon native sessions and omp sessions are two different harnesses that Lemon can run, monitor and steer in one workspace. Sources: lemon:omp, lemon:arch.
Sign in with a ChatGPT or Claude Pro/Max subscription (and copy an existing Codex CLI login with consent), bring API keys for many providers, or use local models; no vendor credits.
Scope
Surfaces: Lemon TUI (terminal), Lemon web workspace (Phoenix, browser), lemon CLI (one-shot, doctor, setup, omp, mcp) · Version: release v2026.11.11 (2026-11-14, commit 4d94b3c) · Plan: Open source (MIT), self-hosted; user pays model providers and hosts · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
7 atomic answers
Agent subscriptions [supported] README: sign in with ChatGPT or Claude Pro/Max; setup can copy an existing Codex CLI login with consent. Sources: lemon:readme.
Api accounts [supported] Keys for Anthropic, OpenAI, Gemini/Vertex, Bedrock, Azure, Mistral, OpenRouter, Groq, DeepSeek, xAI, Kimi, Qwen or OpenAI-compatible endpoints, stored in an encrypted secrets store. Sources: lemon:readme, lemon:config.
Vendor credits [unsupported] No hosted service or credits: support.md lists hosted Lemon operation as not supported and bounded billing search found only model-catalog pricing. Sources: lemon:support, lemon:srch-pricing.
Local models [supported] Any OpenAI-compatible endpoint, local models included. Sources: lemon:readme.
Account switching [partial] Multiple providers, profiles and model routing are configurable; account-level subscription switching is by re-running setup. Sources: lemon:readme, lemon:config.
Vendor account requirement [supported] No Lemon account required; provider credential or local endpoint needed (Lemon Bot has its own local owner account). Sources: lemon:readme, lemon:botapi.
Provider restrictions [partial] Docs state configured providers receive request data; subscription-provider terms are not summarised. Sources: lemon:readme, lemon:compare.
Install with the curl installer (runtime bundled), run `lemon setup` to connect a model, then `lemon` in a repository; Bot profile installs services and opens the browser signed in. Works in any directory; BYO machines attach with a join command; no managed cloud.
Scope
Surfaces: Lemon TUI (terminal), Lemon Bot (web, macOS and iOS apps; separate product in the same repository), lemon CLI (one-shot, doctor, setup, omp, mcp) · Version: release v2026.11.11 (2026-11-14, commit 4d94b3c) · Plan: Open source (MIT), self-hosted; user pays model providers and hosts · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
Windows unsupported; Git is optional but worktree features need Git.
7 atomic answers
First task setup [supported] README Quick start: install.sh, setup connects a model and opens Lemon; `lemon` starts or reuses the daemon. Sources: lemon:readme.
No git [supported] `lemon` runs in the current directory; Git is only needed for kanban worktrees and git-backed boards. Sources: lemon:readme, lemon:kanbanwt.
Local git without remote [supported] Kanban git workflow commits locally; publication is disabled unless configured. Sources: lemon:kanbanwf.
Hosted git [partial] Built-in github skill and webfetch GitHub support; no GitHub connection flow required. Sources: lemon:srch-issue.
Prerequisite guidance [supported] Install, quickstart, setup, doctor and support docs list requirements (glibc, OTP/Elixir for source). Sources: lemon:install, lemon:support.
Managed cloud setup [unsupported] support.md: hosted Lemon service operation is not supported; no managed cloud. Sources: lemon:support.
Byo vps onboarding [supported] Lemon Bot "Connect a computer" generates one join command and Mac app adds machines over SSH; remote execution nodes authenticate to the node gateway. Sources: lemon:readme, lemon:botreadme.
Rich programmable surface: authenticated JSON-RPC control plane (WebSocket), `lemon -p` with JSON output, MCP client commands, webhook ingress, optional A2A listener, and Lemon Bot product API with TypeScript SDK and MCP /mcp tools. Not versioned as stable beyond documented control-plane methods.
Scope
Surfaces: lemon CLI (one-shot, doctor, setup, omp, mcp), Lemon TUI (terminal), Lemon Bot (web, macOS and iOS apps; separate product in the same repository) · Version: release v2026.11.11 (2026-11-14, commit 4d94b3c) · Plan: Open source (MIT), self-hosted; user pays model providers and hosts · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Api [supported] Control-plane JSON-RPC over WebSocket (docs/reference/control-plane.md) and Lemon Bot HTTP /v1 API with contract docs. Sources: lemon:control, lemon:botapi.
Sdk [supported] Lemon Bot TypeScript SDK (sdk/ts) with typed HTTP, nonces and cursor reconnect. Sources: lemon:botreadme.
Mcp server [partial] Lemon Bot backend serves /mcp bot tools to its bots; A2A listener lets peer agents exchange tasks; the Lemon operator runtime is not documented as an MCP server. Sources: lemon:botreadme, lemon:a2a.
Webhooks [supported] Lemon Bot routine webhooks (/hooks/:routineId) and opt-in gateway webhook, SMS and voice ingress. Sources: lemon:botreadme, lemon:arch.
Operations [supported] Create, inspect, steer/redirect, cancel and resume runs, approvals and kanban via control-plane methods. Sources: lemon:control, lemon:support.
Authentication [supported] Operator token for the control plane (loopback by default), per-peer auth for A2A, session/device auth for Bot API. Sources: lemon:readme, lemon:botapi, lemon:a2a.
Stability [partial] Control plane and Web/TUI documented stable for 1.0 boundary; whole product is pre-1.0. Sources: lemon:support, lemon:readme.
MCP client (`lemon mcp`), skills (SKILL.md bundles with install/audit/curation), extensions and WASM tools, personas, plus project instruction import from CLAUDE.md/AGENTS.md/GEMINI.md. Connections are managed by Lemon, not inherited.
Scope
Surfaces: Lemon TUI (terminal), Lemon web workspace (Phoenix, browser), lemon CLI (one-shot, doctor, setup, omp, mcp) · Version: release v2026.11.11 (2026-11-14, commit 4d94b3c) · Plan: Open source (MIT), self-hosted; user pays model providers and hosts · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
7 atomic answers
Mcp client [supported] lemon_mcp client library for external MCP tools, resources and prompts; `lemon mcp list`; OAuth approval requests with scope context. Sources: lemon:arch, lemon:readme, lemon:support.
Plugins [supported] Extensions and skills catalog with install, audit and curation; native WASM tools runtime. Sources: lemon:arch, lemon:readme.
Custom tools [supported] Skills, extensions, WASM tools and persona definitions in .lemon/agents/. Sources: lemon:readme, lemon:arch.
Instructions import [supported] Loads CLAUDE.md, AGENTS.md, GEMINI.md, CLAUDE.local.md and .claude/.lemon variants; imports from Hermes. Sources: lemon:ctxfiles, lemon:readme.
Authentication [supported] MCP OAuth approvals and encrypted secret store with Keychain-held master key. Sources: lemon:support, lemon:readme.
TUI is Bun/TypeScript; browser workspace is Phoenix LiveView (assistant) and a React/Vite Bot web app; macOS and iOS Bot apps are native SwiftUI; browser-node client is TypeScript. Backend is Elixir/OTP and a Bun/SQLite Bot backend.
Scope
Surfaces: Lemon TUI (terminal), Lemon web workspace (Phoenix, browser), Lemon Bot (web, macOS and iOS apps; separate product in the same repository) · Version: release v2026.11.11 (2026-11-14, commit 4d94b3c) · Plan: Open source (MIT), self-hosted; user pays model providers and hosts · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
4 atomic answers
Desktop implementation [supported] macOS Bot app is SwiftUI (LemonBotMac); TUI runs in the terminal (Bun/TypeScript); web is Phoenix/React. Sources: lemon:botreadme, lemon:tui, lemon:arch.
Mobile implementation [supported] iOS app is SwiftUI (LemonBotiOS) sharing LemonBotKit with macOS. Sources: lemon:botreadme, lemon:apple.
Hybrids [supported] No Electron/Tauri; native SwiftUI plus web apps, and the Mac app embeds a runtime installer. Sources: lemon:botreadme, lemon:apple.
Work enters through prompts (TUI, web, Telegram/Discord, one-shot CLI), kanban boards, cron/heartbeat/goal creation, and @file/@url/@git-diff/@session context references. No tracker import or sync; kanban is the native board.
Scope
Surfaces: Lemon TUI (terminal), Lemon web workspace (Phoenix, browser), Lemon Bot (web, macOS and iOS apps; separate product in the same repository), Telegram and Discord channels · Version: release v2026.11.11 (2026-11-14, commit 4d94b3c) · Plan: Open source (MIT), self-hosted; user pays model providers and hosts · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
No Linear/Jira/GitHub issue import or sync.
9 atomic answers
Local creation [supported] Kanban boards and tasks can be created locally via the kanban tool, TUI /kanban, Telegram /kanban and Discord /kanban. Sources: lemon:support, lemon:kanban.
Prompt intake [supported] Prompts from TUI, web, CLI -p, Telegram and Discord; @file/@folder/@git-diff/@url/@session references. Sources: lemon:readme.
External import [unsupported] Bounded search found no tracker import; a built-in github skill exists for ad-hoc use. Sources: lemon:srch-issue.
Plan mode (`/plan`) plans read-only and asks approval before executing; goals and kanban tasks hold descriptions and review verdicts; session history is JSONL with branching (/tree) and rewind. No dedicated plan editor or acceptance-criteria field.
Scope
Surfaces: Lemon TUI (terminal), Lemon web workspace (Phoenix, browser) · Version: release v2026.11.11 (2026-11-14, commit 4d94b3c) · Plan: Open source (MIT), self-hosted; user pays model providers and hosts · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
Plans are session content; kanban tasks have no structured acceptance criteria or plan revisions.
7 atomic answers
Plans [supported] /plan mode produces a plan the user approves before execution. Sources: lemon:readme.
Acceptance criteria [partial] Goals set a target judged by a judge tick; kanban tasks carry text and review verdicts; no separate criteria field. Sources: lemon:goal, lemon:kanbanwf.
Editors [partial] Plan can be revised conversationally; kanban fields editable via tool/TUI. Sources: lemon:readme, lemon:kanban.
Revisions [partial] /rewind and /tree browse preserved branches of history; no document revision log for plans. Sources: lemon:readme.
Implementation links [partial] Kanban workflow records commitSha and run IDs on the task. Sources: lemon:kanbanwf.
Amendment [supported] Follow-up, steer and redirect change a running turn. Sources: lemon:readme.
Restart persistence [supported] Durable sessions, kanban state and goal state persist across daemon restarts. Sources: lemon:arch, lemon:kanban, lemon:support.
Kanban tasks have depends_on and status columns with leases; sub-work uses `task` child sessions. No epics or arbitrary hierarchy; goals continue within a budget.
Scope
Surfaces: Lemon TUI (terminal), Lemon web workspace (Phoenix, browser) · Version: release v2026.11.11 (2026-11-14, commit 4d94b3c) · Plan: Open source (MIT), self-hosted; user pays model providers and hosts · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
Flat boards with dependencies; no epic/parent entity or task-to-epic growth.
9 atomic answers
Epics [unsupported] No epic entity in the kanban store fields (status, priority, assignee, depends_on, meta). Sources: lemon:kanban.
Hierarchy [partial] Child sessions via `task` form a parent/child tree per run; boards are flat. Sources: lemon:readme, lemon:arch.
Enforcement [supported] Dispatcher leases only available tasks; second review rejection blocks the card. Sources: lemon:kanban, lemon:kanbanwf.
State propagation [partial] Task status moves with workflow phases; no automatic parent propagation. Sources: lemon:kanbanwf.
Task to epic [unsupported] No conversion of a task into an epic. Sources: lemon:kanban.
Identity retention [partial] A task keeps its ID, status and meta across leases and reclaim. Sources: lemon:kanban.
Workflow constraints [supported] No mandatory workflow: chat, goals, kanban and cron are independent entry points; the kanban coding workflow is opt-in. Sources: lemon:kanbanwf, lemon:readme.
AGENTS.md/CLAUDE.md context files, skills (drafted from successful runs, `lemon learn`), durable remember/recall memory scoped by owner/profile, profiles with separate workspaces, and session resume. Memory has review/promote flows.
Scope
Surfaces: Lemon TUI (terminal), Lemon web workspace (Phoenix, browser), Lemon Bot (web, macOS and iOS apps; separate product in the same repository) · Version: release v2026.11.11 (2026-11-14, commit 4d94b3c) · Plan: Open source (MIT), self-hosted; user pays model providers and hosts · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Scope [supported] User or project memory; verified private actor partitions for Bot sessions. Sources: lemon:memory.
Provenance [supported] Search hits include session key, document ID and run ID. Sources: lemon:memory.
Correction [supported] Memory can be edited or undone; Bot Identity/Job/Memory changes are reviewable with undo. Sources: lemon:botreadme, lemon:memory.
Deletion [supported] Memory entries are removable through the memory tools and uninstall --purge removes data. Sources: lemon:memory, lemon:readme.
Freshness [partial] Context window controls (/compact, /context) and adaptive routing; no explicit memory staleness policy found in docs read. Sources: lemon:readme.
Native grep including ast_grep, bounded @file/@folder/@git-diff/@url/@session references, LSP diagnostics (preview), memory recall, web search/fetch, and browser automation (preview). No repository index or architecture-conflict enforcement.
Scope
Surfaces: Lemon TUI (terminal), Lemon web workspace (Phoenix, browser) · Version: release v2026.11.11 (2026-11-14, commit 4d94b3c) · Plan: Open source (MIT), self-hosted; user pays model providers and hosts · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
No semantic index; architecture awareness comes from instructions and LSP checks.
Native kanban boards and tasks (preview) with status columns, priority, assignee, dependencies, leases, archive and TUI/Telegram/Discord/control-plane access; plus saved sessions. No comments or labels documented; external tracker not required.
Scope
Surfaces: Lemon TUI (terminal), Lemon web workspace (Phoenix, browser), Telegram and Discord channels · Version: release v2026.11.11 (2026-11-14, commit 4d94b3c) · Plan: Open source (MIT), self-hosted; user pays model providers and hosts · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
Preview feature; thin metadata (no labels or discussion).
Agents operate the same kanban store through the model-facing `kanban` tool and workers lease and complete tasks; goal and cron state are agent-readable. Human TUI/Telegram/Discord views reflect changes.
Scope
Surfaces: Lemon TUI (terminal), Telegram and Discord channels · Version: release v2026.11.11 (2026-11-14, commit 4d94b3c) · Plan: Open source (MIT), self-hosted; user pays model providers and hosts · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
Preview; attribution and conflict handling beyond leases are not documented.
14 atomic answers
Shared ids [supported] Agent tool and humans use the same task IDs. Sources: lemon:support, lemon:kanban.
No living product specification: skills, memory and context files persist guidance, but there are no maintained requirements with revisions, drift checks or review integration.
Scope
Surfaces: Lemon TUI (terminal), Lemon web workspace (Phoenix, browser) · Version: release v2026.11.11 (2026-11-14, commit 4d94b3c) · Plan: Open source (MIT), self-hosted; user pays model providers and hosts · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
9 atomic answers
Persistent requirements [unsupported] Context files and memory persist guidance but are not a requirements model. Sources: lemon:ctxfiles, lemon:memory.
Human edits [partial] Humans can edit context files and memory. Sources: lemon:ctxfiles.
Agent edits [partial] Agents write memory and draft skills; not requirements. Sources: lemon:memory, lemon:readme.
Revisions [unsupported] No requirement revisions. Sources: lemon:memory.
Approvals [partial] Synthesized skills remain drafts until promotion. Sources: lemon:compare.
Implementation links [unsupported] No requirement-to-code links. Sources: lemon:readme.
Later retrieval [partial] Memory recall in later sessions retrieves notes. Sources: lemon:memory.
Drift detection [unsupported] No drift detection. Sources: lemon:readme.
Review integration [unsupported] No spec check in review. Sources: lemon:kanbanwf.
Many sessions and runs execute concurrently, each its own supervised BEAM process, bounded by max_concurrent_runs and per-conversation serialization; `/tasks`, web activity and kanban show running and finished work.
Scope
Surfaces: Lemon TUI (terminal), Lemon web workspace (Phoenix, browser), Telegram and Discord channels · Version: release v2026.11.11 (2026-11-14, commit 4d94b3c) · Plan: Open source (MIT), self-hosted; user pays model providers and hosts · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
The documented max_concurrent_runs example is 2; actual defaults were read from docs, not measured.
5 atomic answers
Concurrent sessions [supported] Daemon holds many sessions; a conversation key serializes work within one conversation only. Sources: lemon:arch, lemon:readme.
Concurrent tasks [supported] `task` fans out child sessions in parallel; kanban tasks dispatch to workers in separate worktrees. Sources: lemon:readme, lemon:kanbanwt.
Quotas [supported] max_concurrent_runs in config and gateway concurrency slots; budgets caps are separate. Sources: lemon:config, lemon:arch.
Observed concurrency [partial] Source and docs define the slot model; this catalog does not run it. Sources: lemon:arch.
Status visibility [supported] /tasks live children, web activity view, kanban columns, Bot Activity distinct from transcript. Sources: lemon:readme, lemon:botreadme.
Kanban tasks have assignee fields and leases that give exclusive dispatch; router conversation queues serialize per session. Humans or agents can be named assignees; duplicate-work prevention is by lease and compare-and-swap commit.
Scope
Surfaces: Lemon TUI (terminal), Lemon web workspace (Phoenix, browser) · Version: release v2026.11.11 (2026-11-14, commit 4d94b3c) · Plan: Open source (MIT), self-hosted; user pays model providers and hosts · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
Kanban is preview; assignment routing is manual or dispatcher-driven.
7 atomic answers
Human assignment [partial] assignee string field; no user directory enforcement in kanban. Sources: lemon:kanban.
Agent assignment [supported] Dispatcher assigns tasks to workers; /agent delegation can name an execution node. Sources: lemon:kanbanwf, lemon:arch.
Claims [supported] Lease_status claims next available task. Sources: lemon:kanban.
Queues [supported] Collect/follow-up queues per conversation and dispatcher queues. Sources: lemon:arch, lemon:kanban.
Routing [partial] Adaptive model routing and named node placement; not task-level routing rules. Sources: lemon:arch, lemon:config.
Product-owned delegation: `task` spawns native child sessions (read-only scout and reviewer built in, custom personas), `agent` delegates via router to local or named node, omp delegation, and kanban workers. Children inherit parent model; /tasks shows them live; results return to the parent.
Scope
Surfaces: Lemon TUI (terminal), Lemon web workspace (Phoenix, browser), lemon CLI (one-shot, doctor, setup, omp, mcp) · Version: release v2026.11.11 (2026-11-14, commit 4d94b3c) · Plan: Open source (MIT), self-hosted; user pays model providers and hosts · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
12 atomic answers
Roles [supported] Built-in scout and reviewer personas plus custom .lemon/agents definitions. Sources: lemon:readme.
Model harness effort [partial] Children share the parent model and tool stack; omp sessions choose their own model; node placement selectable. Sources: lemon:readme, lemon:omp.
Messages [supported] Steer, redirect and cancel children and omp sessions; subagent parent questions. Sources: lemon:omp, lemon:arch.
Results return [supported] Child usage and completion reports return to the parent. Sources: lemon:config, lemon:arch.
Cross harness [supported] Native children plus omp delegate in one workflow. Sources: lemon:omp.
Activation [supported] Available by default in agent runs; omp needs the binary installed; kanban dispatch opt-in. Sources: lemon:omp, lemon:readme.
Authentication [supported] Native children use Lemon credentials; omp uses its own; named nodes authenticate to the control plane. Sources: lemon:omp, lemon:arch.
Live progress [supported] /tasks lists children live. Sources: lemon:readme.
Retained results [supported] Child sessions are JSONL histories retained with the session. Sources: lemon:arch.
Followup [supported] omp sessions can be resumed; child sessions are reopenable as sessions. Sources: lemon:omp.
Invocation [supported] Model-invoked task/agent tools, @name personas and user commands. Sources: lemon:readme, lemon:arch.
Cron (5-field expressions, `every 30m`, weekday times), heartbeats, goal auto-loops and reminders run unattended in the daemon in isolated forked sessions with an audit trail; the scheduler lives in the daemon so closing a client does not stop it. Cron and goals are preview.
Scope
Surfaces: Lemon TUI (terminal), Lemon web workspace (Phoenix, browser), Telegram and Discord channels · Version: release v2026.11.11 (2026-11-14, commit 4d94b3c) · Plan: Open source (MIT), self-hosted; user pays model providers and hosts · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Events [partial] Webhook, SMS and voice ingress and routine webhooks start runs; no general event bus trigger documented for users. Sources: lemon:arch, lemon:botreadme.
Recurring tasks [supported] Cron jobs and heartbeats recur and report back. Sources: lemon:readme.
Completion conditions [supported] Goals continue within a continuation budget until a judge accepts. Sources: lemon:readme, lemon:goal.
Esc stops a turn, /cancel, /steer and redirect work from TUI, web and Telegram/Discord; approvals resolve from any surface with notifications; omp sessions can be paused/steered/cancelled and resumed. Questions from subagents route to the parent.
Scope
Surfaces: Lemon TUI (terminal), Lemon web workspace (Phoenix, browser), Telegram and Discord channels · Version: release v2026.11.11 (2026-11-14, commit 4d94b3c) · Plan: Open source (MIT), self-hosted; user pays model providers and hosts · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
10 atomic answers
Pause [partial] Cron jobs pause/resume; running turns stop rather than pause. Sources: lemon:support.
Stop [supported] Esc stops the turn; /cancel in channels; history preserved. Sources: lemon:readme.
Web automation boards and Bot Activity views show kanban columns, cron jobs and active work; Bot groups coordinate 2-6 Bots. No dedicated cross-epic fleet view with dependency graph.
Scope
Surfaces: Lemon web workspace (Phoenix, browser), Lemon Bot (web, macOS and iOS apps; separate product in the same repository) · Version: release v2026.11.11 (2026-11-14, commit 4d94b3c) · Plan: Open source (MIT), self-hosted; user pays model providers and hosts · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
Board and activity views; no dependency graph or workload view found.
8 atomic answers
Fleet fixture [partial] Web workspace automation boards and Bot workspace list Bots with activity. Sources: lemon:readme, lemon:botreadme.
Parent child [partial] /tasks child tree per run. Sources: lemon:readme.
No mandatory workflow: chat, plan mode, goals, kanban, cron and omp delegation are independent; personas and model routing are configurable by natural language and config; in-run steer/redirect; /tasks and run details show what ran.
Scope
Surfaces: Lemon TUI (terminal), Lemon web workspace (Phoenix, browser) · Version: release v2026.11.11 (2026-11-14, commit 4d94b3c) · Plan: Open source (MIT), self-hosted; user pays model providers and hosts · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
10 atomic answers
Quick task [supported] `lemon -p` and plain prompts need no preset. Sources: lemon:readme.
Growing epic [partial] Chat can become a goal or kanban board by asking; identity not carried over automatically. Sources: lemon:readme.
The daemon runs on a machine you own; Lemon Bot attaches machines (BYO hosts, SSH join command) and named execution nodes run jobs elsewhere with local credentials. Work keeps running when clients close; no vendor cloud.
Scope
Surfaces: Lemon TUI (terminal), Lemon Bot (web, macOS and iOS apps; separate product in the same repository) · Version: release v2026.11.11 (2026-11-14, commit 4d94b3c) · Plan: Open source (MIT), self-hosted; user pays model providers and hosts · OS: Not specified · Execution modes: local, own-server · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
No managed cloud; laptop independence requires your own always-on host or node.
12 atomic answers
Local [supported] Default: daemon and agent on the local machine. Sources: lemon:readme.
Byo remote [supported] Named execution nodes and Lemon Bot attached machines on hosts you own. Sources: lemon:arch, lemon:botreadme.
Self hosted [supported] The whole control plane and Bot backend are self-hosted. Sources: lemon:readme, lemon:botreadme.
Managed cloud [unsupported] Hosted Lemon service operation is listed as not supported. Sources: lemon:support, lemon:compare.
Hybrid [supported] Controller on one machine with attached nodes on others. Sources: lemon:arch.
Provisioning [partial] User installs and joins machines with generated commands; no auto-provisioning of cloud VMs. Sources: lemon:readme.
Payer [supported] User pays host and model costs. Sources: lemon:compare.
Resources [partial] Host-dependent; no resource spec. Sources: lemon:arch.
Region [unsupported] No region concept. Sources: lemon:support.
Expiry [supported] No sandbox expiry; services persist (macOS login, Linux with linger). Sources: lemon:readme.
Client disconnect [supported] Services keep running after the terminal closes; Bots stay active when clients close but stop if their machine is offline. Sources: lemon:readme, lemon:botreadme.
Other device continuation [supported] Start on Telegram/phone and continue in web or TUI. Sources: lemon:readme.
Runs execute in the project directory as the host user by default; kanban tasks and omp workers can use managed per-task git worktrees, and the exec/process shell tools can optionally run commands in a Docker container backend (cwd mounted at /workspace, read-only root, network none by default, CPU/memory/pids limits; default backend is local; applies to shell commands, not the whole run). Tool policy and approvals are enforced, but docs state there is no OS-level sandbox for the host run; WASM runtime exists for tools.
Scope
Surfaces: Lemon TUI (terminal), Lemon Bot (web, macOS and iOS apps; separate product in the same repository) · Version: release v2026.11.11 (2026-11-14, commit 4d94b3c) · Plan: Open source (MIT), self-hosted; user pays model providers and hosts · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
Not separately cross-checked
Worktrees separate files only; the safety contract disclaims sandboxing.
12 atomic answers
Checkout [supported] Default runs edit the working directory. Sources: lemon:readme.
Branch [supported] Kanban git workflow commits to branches. Sources: lemon:kanbanwf.
Worktree [supported] Per-task git worktree for git-backed boards; omp worktrees at <git common dir>/lemon-omp-worktrees. Sources: lemon:kanbanwt, lemon:omp.
Container [partial] Optional Docker terminal backend for exec/process shell commands (isolation :container, read-only rootfs, tmpfs /tmp, network none, resource limits); default backend is local and other tools and the agent itself are not containerized. Dockerfile.runtime separately packages the runtime. Sources: lemon:docker-backend, lemon:term-backends, lemon:codingagent-readme.
Vm [unsupported] No VM isolation feature; Bot machines are user hosts. Sources: lemon:safety.
Os sandbox [unsupported] Safety contract: not a sandbox; terminal access runs as the host account. Sources: lemon:safety, lemon:support.
Filesystem [partial] Workspace roots and file-size limits in tool policy. Sources: lemon:execpolicy.
Process [partial] Host subprocesses share the host user; shell commands run through the optional Docker backend are contained in a container with a pids limit. Sources: lemon:safety, lemon:docker-backend.
Network [partial] Tool-level egress control; the optional Docker shell backend defaults to network none, but there is no OS network sandbox for the host run. Sources: lemon:safety, lemon:docker-backend.
Secrets [partial] Encrypted secret store; docs say it is not a broker that keeps credentials from tools. Sources: lemon:compare, lemon:readme.
Code separation [partial] Worktrees and node-local workspaces separate code per task or node. Sources: lemon:kanbanwt, lemon:arch.
Each run and tool call is a supervised BEAM process; crashes become tool errors, crashed runs are deliberately not replayed, durable sessions and kanban leases survive daemon restart, and `lemon update rollback`, backups and doctor aid recovery.
Scope
Surfaces: Lemon TUI (terminal), Lemon web workspace (Phoenix, browser), Telegram and Discord channels · Version: release v2026.11.11 (2026-11-14, commit 4d94b3c) · Plan: Open source (MIT), self-hosted; user pays model providers and hosts · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
12 atomic answers
Client disconnect [supported] Daemon continues when a client closes. Sources: lemon:readme.
Worker crash [supported] A crashed tool becomes an error result; supervised processes restart. Sources: lemon:readme.
Service restart [supported] Restart recovery keeps lease, base tree, configuration and run IDs for kanban workflow; sessions persist. Sources: lemon:kanbanwf, lemon:arch.
Expiry [supported] No sandbox expiry. Sources: lemon:readme.
Transcript reload [supported] Session history persists and is reopened. Sources: lemon:readme, lemon:arch.
Process reconnect [partial] Clients reconnect to the daemon; a killed run is not reattached. Sources: lemon:readme.
Lemon does not manage project dependency installs, caches, services or ports for agent tasks; it manages its own runtime, services (launchd/systemd), and ports (loopback defaults). Tool output is for the agent to handle.
Scope
Surfaces: Lemon TUI (terminal) · Version: release v2026.11.11 (2026-11-14, commit 4d94b3c) · Plan: Open source (MIT), self-hosted; user pays model providers and hosts · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
10 atomic answers
Dependencies [unsupported] No project dependency management; agents run shell commands. Sources: lemon:readme.
Caches [unsupported] No project cache handling. Sources: lemon:readme.
Snapshots [partial] Checkpoints (preview) snapshot files with restore. Sources: lemon:support.
Services [unsupported] No service provisioning for project tests. Sources: lemon:readme.
Ports [partial] Lemon uses fixed documented ports (4040, 4044, 4080, 4100, 9901) with loopback defaults; no project port allocation. Sources: lemon:readme.
Secrets [partial] Encrypted store and node-local secrets docs; injection is per tool config. Sources: lemon:readme, lemon:support.
Duplicate installs [unsupported] Worktrees duplicate checkouts with no dedupe. Sources: lemon:kanbanwt.
Collisions [unsupported] No collision avoidance for project services. Sources: lemon:readme.
Remote setup [partial] Node join command sets up the Lemon worker, not project environments. Sources: lemon:readme.
Automatic repair [partial] doctor diagnoses Lemon itself. Sources: lemon:readme.
Enforced cumulative run/session token and dollar budgets (zero blocks), optional cap on tool-using turns, max continuation budget for goals, provider circuit breakers and retries. Time limits per tool exist in tools.
Scope
Surfaces: Lemon TUI (terminal), Lemon web workspace (Phoenix, browser) · Version: release v2026.11.11 (2026-11-14, commit 4d94b3c) · Plan: Open source (MIT), self-hosted; user pays model providers and hosts · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
8 atomic answers
Time limits [partial] Per-tool timeouts; no overall run wall clock limit documented. Sources: lemon:config.
Turn limits [supported] Optional cap on tool-using turns per prompt (unset = unlimited). Sources: lemon:config.
Token limits [supported] [budgets] max_run_tokens and max_session_tokens. Sources: lemon:config.
Spend limits [supported] [budgets] max_run_cost_usd and max_session_cost_usd; children counted. Sources: lemon:config.
Timeouts [partial] Approval timeouts and tool timeouts documented. Sources: lemon:support.
Retries [supported] Retry attempts count toward budgets; messages never sent twice. Sources: lemon:config, lemon:readme.
Persisted introspection events, run summaries, JSONL history, usage by model/provider/session, support bundles (redacted), telemetry events, cron audit, and Bot activity separated from transcript. No cross-project statistics.
Scope
Surfaces: Lemon web workspace (Phoenix, browser), Lemon TUI (terminal) · Version: release v2026.11.11 (2026-11-14, commit 4d94b3c) · Plan: Open source (MIT), self-hosted; user pays model providers and hosts · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
Usage is recorded when a run finishes; cost is a bounded known-subtotal.
13 atomic answers
Logs [supported] Logs and focused traces; `lemon doctor --bundle`. Sources: lemon:support.
Traces [partial] Telemetry events and persisted introspection envelope. Sources: lemon:telemetry.
Usage page and session views show tokens and known-cost subtotals per model, provider and session, with children aggregated for budgets; costs are display-only subtotals flagged incomplete when unknown. No billed reconciliation or alerts.
Scope
Surfaces: Lemon web workspace (Phoenix, browser), Lemon TUI (terminal) · Version: release v2026.11.11 (2026-11-14, commit 4d94b3c) · Plan: Open source (MIT), self-hosted; user pays model providers and hosts · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
usage.cost is a bounded display of known subtotals, not an enforcement ledger; no alerts or export.
14 atomic answers
Task cost [partial] Per-run counters and session usage; kanban task cost not shown. Sources: lemon:config.
Session cost [supported] Session tokens and cost in web and TUI. Sources: lemon:web.
Child cost [supported] Descendant spend stored separately and counted in the parent budget. Sources: lemon:config.
Epic cost [unsupported] No epic entity. Sources: lemon:kanban.
Harness aggregation [partial] Aggregation across providers; omp usage is not folded in. Sources: lemon:omp, lemon:web.
Billed vs estimated [supported] knownCostSubtotal and incomplete flag mark estimates. Sources: lemon:support.
Tokens [supported] Tokens recorded per run and session. Sources: lemon:config, lemon:web.
Subscription allowance [unsupported] No subscription-allowance display found. Sources: lemon:web.
Provider reconciliation [unsupported] Not an enforcement ledger and no provider-bill reconciliation. Sources: lemon:support.
Compute cost [unsupported] No compute cost; self-hosted. Sources: lemon:compare.
Refresh delay [supported] Usage is recorded when a run finishes. Sources: lemon:web.
Alerts [unsupported] Budgets block but no alert notifications documented. Sources: lemon:config.
Export [partial] Control-plane methods; no CSV export read. Sources: lemon:control.
Drilldown [supported] Top sessions and per-model drilldown. Sources: lemon:web.
max_concurrent_runs and gateway slots bound concurrency; conversation queues serialize per session; per-provider admission and circuit breakers; children respect ancestor budgets. No CPU/RAM-aware scheduling or check deduplication.
Scope
Surfaces: Lemon TUI (terminal), Lemon web workspace (Phoenix, browser) · Version: release v2026.11.11 (2026-11-14, commit 4d94b3c) · Plan: Open source (MIT), self-hosted; user pays model providers and hosts · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Single-owner by design: each Lemon Bot belongs to one human and Bot groups coordinate Bots of the same person; the contract says no live Team Bots or other-human groups. Operator surfaces are single-user with shared sessions across the same user devices.
Scope
Surfaces: Lemon Bot (web, macOS and iOS apps; separate product in the same repository), Lemon web workspace (Phoenix, browser), Lemon TUI (terminal) · Version: release v2026.11.11 (2026-11-14, commit 4d94b3c) · Plan: Open source (MIT), self-hosted; user pays model providers and hosts · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
11 atomic answers
Visibility [partial] Same owner sees sessions on all devices; other users cannot see private Bot content. Sources: lemon:botapi.
Discussion [unsupported] No multi-user discussion. Sources: lemon:botapi.
Comments [unsupported] No comment threads. Sources: lemon:botapi.
Presence [unsupported] No presence for other humans. Sources: lemon:botapi.
Coprompting [unsupported] Contract: current scope is personally owned assistants; no live Team Bots or other-human groups. Sources: lemon:botapi.
Ordering [unsupported] No multi-human ordering. Sources: lemon:botapi.
Conflicts [unsupported] Not applicable to single-owner sessions. Sources: lemon:botapi.
Attribution [partial] Run.initiatorUserId records the actor. Sources: lemon:botapi.
Permissions [supported] Workspace admin/owner roles never grant access to another user Bot. Sources: lemon:botapi.
Plan restrictions [supported] No plans; MIT software. Sources: lemon:license.
Owner online [supported] Bots stay active when clients close but depend on the assigned machine. Sources: lemon:botreadme.
Lemon Bot has workspace roles (owner, admin, member), invite tokens, per-user ownership ACL, OIDC sign-in with requireSSO and SCIM provisioning adapters; the operator control plane uses token auth and thread-level grants are limited. Enforcement is documented in the contract and backend.
Scope
Surfaces: Lemon Bot (web, macOS and iOS apps; separate product in the same repository) · Version: release v2026.11.11 (2026-11-14, commit 4d94b3c) · Plan: Open source (MIT), self-hosted; user pays model providers and hosts · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
Roles and SSO exist in the Lemon Bot product only; the Lemon runtime has no org roles.
Approvals for command, tool and access escalation with scopes once/session/agent/global, expiry on run end, approver identity (owner), allow/deny, full command expansion required for long commands, fail-closed tool policy, and permission modes; defaults and policies are product-enforced. Terminal runs as the host account.
Scope
Surfaces: Lemon TUI (terminal), Lemon web workspace (Phoenix, browser), Lemon Bot (web, macOS and iOS apps; separate product in the same repository), Telegram and Discord channels · Version: release v2026.11.11 (2026-11-14, commit 4d94b3c) · Plan: Open source (MIT), self-hosted; user pays model providers and hosts · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
Not a sandbox; approvals do not cover network at OS level.
Durable JSONL session history, run summaries, cron audit, approval resolved events, Bot Activity separated from transcript, persisted introspection and local telemetry. History is local files and databases; no tamper-evident audit.
Scope
Surfaces: Lemon web workspace (Phoenix, browser), Lemon Bot (web, macOS and iOS apps; separate product in the same repository), Lemon TUI (terminal) · Version: release v2026.11.11 (2026-11-14, commit 4d94b3c) · Plan: Open source (MIT), self-hosted; user pays model providers and hosts · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
Not an audit log with integrity or defined retention.
11 atomic answers
Actions [supported] Run and tool events in history and introspection. Sources: lemon:arch, lemon:telemetry.
Approvals [supported] exec.approval.resolved events with decision. Sources: lemon:support.
Web workspace shows diffs and tool cards, git changes viewer, /rewind with file restore, and kanban independent reviewer with exact-tree commit; Telegram/Discord offer approval buttons. Review guidance is partial; keyboard palette (cmd-K) exists.
Scope
Surfaces: Lemon web workspace (Phoenix, browser), Lemon TUI (terminal) · Version: release v2026.11.11 (2026-11-14, commit 4d94b3c) · Plan: Open source (MIT), self-hosted; user pays model providers and hosts · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
No PR-level review comments or batch review queue.
Session continuity across devices for the same owner; Bots remain active and reachable from any of the owner clients, omp sessions can be resumed. No handover to another human, ownership transfer or attribution flow.
Scope
Surfaces: Lemon Bot (web, macOS and iOS apps; separate product in the same repository), Lemon TUI (terminal), Lemon web workspace (Phoenix, browser) · Version: release v2026.11.11 (2026-11-14, commit 4d94b3c) · Plan: Open source (MIT), self-hosted; user pays model providers and hosts · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
Owner-only; no second-person takeover.
12 atomic answers
Ongoing takeover [unsupported] Contract says no other-human groups; no takeover flow. Sources: lemon:botapi.
Same task [supported] Same session across owner devices. Sources: lemon:readme.
Session history [supported] Full history persists. Sources: lemon:arch.
Retained session history, checkpoints and diffs, tool cards, Bot attachments, kanban review verdicts and commit SHA, browser screenshot artifacts under .lemon/browser-artifacts (preview), generated media job records; no cross-task gallery.
Scope
Surfaces: Lemon web workspace (Phoenix, browser), Lemon Bot (web, macOS and iOS apps; separate product in the same repository), Lemon TUI (terminal) · Version: release v2026.11.11 (2026-11-14, commit 4d94b3c) · Plan: Open source (MIT), self-hosted; user pays model providers and hosts · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
No searchable artifact gallery; browser and media are preview.
13 atomic answers
Diffs [supported] Git changes viewer and diff cards. Sources: lemon:readme.
Documents [partial] Files in workspace and Bot attachments. Sources: lemon:botreadme.
Kanban coding workflow requires an independent review before commit, with one corrective pass and a block on second rejection; LSP diagnostics checks (preview) optional on edits; tests and CI run only if the agent runs them. Goal judge checks progress.
Scope
Surfaces: Lemon web workspace (Phoenix, browser), Lemon TUI (terminal) · Version: release v2026.11.11 (2026-11-14, commit 4d94b3c) · Plan: Open source (MIT), self-hosted; user pays model providers and hosts · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
Review gate exists only in the opt-in kanban workflow; no mandatory tests/lint/CI gate.
11 atomic answers
Tests [partial] Agent runs tests; no required test gate. Sources: lemon:readme.
Kanban git workflow: per-task worktree, leased coding, exact-tree compare-and-swap local commit and optional publication (push and PR creation, never implicit, uncertain publishes are queried not retried); github skill for ad-hoc PR work. Rebase and review comment response are not documented.
Scope
Surfaces: Lemon web workspace (Phoenix, browser), Lemon TUI (terminal) · Version: release v2026.11.11 (2026-11-14, commit 4d94b3c) · Plan: Open source (MIT), self-hosted; user pays model providers and hosts · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
Publication is opt-in and preview.
9 atomic answers
Branches [supported] Branch updates by compare-and-swap. Sources: lemon:kanbanwf.
Humans approve commands and plans; merge authority belongs to the user: workflow commits locally and publishes only when configured; no release or deploy features.
Scope
Surfaces: Lemon TUI (terminal), Lemon web workspace (Phoenix, browser) · Version: release v2026.11.11 (2026-11-14, commit 4d94b3c) · Plan: Open source (MIT), self-hosted; user pays model providers and hosts · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
No release/deploy.
6 atomic answers
Approve [supported] Plan and command approvals. Sources: lemon:readme.
Merge [partial] Local exact-tree commit; merge stays with the user ("you review and merge the results"). Sources: lemon:readme, lemon:kanbanwf.
Release [unsupported] No release feature (Lemon own releases use CI). Sources: lemon:srch-issue.
Deploy [unsupported] No deploy feature. Sources: lemon:srch-issue.
Kanban tasks store commitSha, review verdict and run IDs; checkpoints and /rewind restore files; kanban restart recovery. No PR/deploy links or approval invalidation on revision change.
Scope
Surfaces: Lemon web workspace (Phoenix, browser), Lemon TUI (terminal) · Version: release v2026.11.11 (2026-11-14, commit 4d94b3c) · Plan: Open source (MIT), self-hosted; user pays model providers and hosts · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
Commit-level evidence only.
9 atomic answers
Commit links [supported] commitSha on task. Sources: lemon:kanbanwf.
Pr links [partial] Publication phase may record push/PR outcome. Sources: lemon:kanbanwf.
Revert [partial] Rewind restore; no git revert command. Sources: lemon:readme.
Stale approval invalidation [partial] Approvals expire when runs end; exact-tree commit binds review to a tree. Sources: lemon:support, lemon:kanbanwf.
No batch review queue: kanban shows tasks by state and the reviewer reviews one task at a time; no grouping, risk filters or merge queue.
Scope
Surfaces: Lemon web workspace (Phoenix, browser), Lemon TUI (terminal) · Version: release v2026.11.11 (2026-11-14, commit 4d94b3c) · Plan: Open source (MIT), self-hosted; user pays model providers and hosts · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
Per-task review only.
12 atomic answers
Review queue [partial] Kanban columns include review states per task. Sources: lemon:kanban.
Summaries [partial] Run summaries per task. Sources: lemon:kanbanwf.
Grouping [unsupported] No grouping. Sources: lemon:kanban.
Risk size filters [unsupported] No risk/size filters. Sources: lemon:kanban.
MIT for the whole repository (TUI, runtime, control plane, Lemon Bot backend and apps), except the Lemon desktop-pet artwork under CC0; LemonSim lives in a separate repository. GitHub metadata shows NOASSERTION but the LICENSE file is MIT.
Scope
Surfaces: Lemon TUI (terminal), Lemon web workspace (Phoenix, browser), Lemon Bot (web, macOS and iOS apps; separate product in the same repository), lemon CLI (one-shot, doctor, setup, omp, mcp) · Version: release v2026.11.11 (2026-11-14, commit 4d94b3c) · Plan: Open source (MIT), self-hosted; user pays model providers and hosts · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Fully self-hosted: runtime, control plane and Lemon Bot backend run on your machines with verified backups, update plans with rollback, uninstall with preview, Hermes import, and plain JSONL/SQLite data. No vendor account is required.
Scope
Surfaces: Lemon TUI (terminal), Lemon Bot (web, macOS and iOS apps; separate product in the same repository) · Version: release v2026.11.11 (2026-11-14, commit 4d94b3c) · Plan: Open source (MIT), self-hosted; user pays model providers and hosts · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
8 atomic answers
Self hosting [supported] All components self-hosted. Sources: lemon:readme.
Vendor dependencies [supported] Model providers only; optional push relay and Sentry are opt-in. Sources: lemon:readme, lemon:errrep.
Data stays on your machine except what your configured model providers receive; no analytics SDK; Sentry error reporting only when SENTRY_DSN is set; telemetry events are local; push notifications are content-free end-to-end encrypted in Lemon Bot; secrets in an encrypted store with a Keychain-held master key.
Scope
Surfaces: Lemon TUI (terminal), Lemon web workspace (Phoenix, browser), Lemon Bot (web, macOS and iOS apps; separate product in the same repository) · Version: release v2026.11.11 (2026-11-14, commit 4d94b3c) · Plan: Open source (MIT), self-hosted; user pays model providers and hosts · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
Provider retention, training and residency are provider facts.
Credentials [supported] Encrypted store; master key in macOS Keychain or env/private key file; omp credentials separate. Sources: lemon:readme, lemon:omp.
Logs [supported] Local logs and redacted support bundles. Sources: lemon:support.
Artifacts [supported] Local workspace and Bot data directory. Sources: lemon:botreadme.
Retention [partial] Local until deleted; no policy beyond docs. Sources: lemon:readme.
Deletion [supported] uninstall --purge and memory tools. Sources: lemon:readme.
Training [unknown] Provider training policy is a third-party fact. Sources: lemon:compare.
Residency [unknown] Provider-dependent; local storage otherwise. Sources: lemon:compare.
Subprocessors [unknown] Providers and optional Sentry/APNs are third parties; no list published. Sources: lemon:errrep.
Telemetry disclosure [supported] docs/telemetry.md and error-reporting.md document emissions and the Sentry sink. Sources: lemon:telemetry, lemon:errrep.
Telemetry defaults [supported] No external telemetry by default; Sentry disabled without DSN. Sources: lemon:errrep, lemon:srch-analytics.
Free open-source software with no Lemon price; users pay model providers (API keys or ChatGPT/Claude subscriptions) and their own hosts.
Scope
Surfaces: Lemon TUI (terminal), Lemon Bot (web, macOS and iOS apps; separate product in the same repository) · Version: release v2026.11.11 (2026-11-14, commit 4d94b3c) · Plan: Open source (MIT), self-hosted; user pays model providers and hosts · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
12 atomic answers
Currency [supported] No price. Sources: lemon:license.
No Lemon platform fee for one, two or five developers; costs are provider tokens or subscriptions and own hosts; no stated workload scenarios.
Scope
Surfaces: Lemon TUI (terminal), Lemon Bot (web, macOS and iOS apps; separate product in the same repository) · Version: release v2026.11.11 (2026-11-14, commit 4d94b3c) · Plan: Open source (MIT), self-hosted; user pays model providers and hosts · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
Token and compute volumes are workload-specific and not assumed.
11 atomic answers
One person [partial] Lemon fee 0 plus provider costs. Sources: lemon:license.
Two people [partial] Each person runs their own owner account; fee 0. Sources: lemon:botapi, lemon:license.
Five people [partial] Same; fee 0. Sources: lemon:license.
Task assumptions [unknown] No catalog task assumptions. Sources: lemon:readme.
Pre-1.0 open-source project with frequent calendar-versioned releases (three releases 2026-11-13/14), docs site, GitHub issues and a SECURITY.md/support guide; no SLA; stable versus preview boundaries documented.
Scope
Surfaces: Lemon TUI (terminal), Lemon web workspace (Phoenix, browser), Lemon Bot (web, macOS and iOS apps; separate product in the same repository) · Version: release v2026.11.11 (2026-11-14, commit 4d94b3c) · Plan: Open source (MIT), self-hosted; user pays model providers and hosts · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
No response commitments or status page.
8 atomic answers
Release stage [supported] Pre-1.0; stable vs preview features listed. Sources: lemon:readme, lemon:support.
Access restrictions [supported] Public releases; Windows and hosted service unsupported. Sources: lemon:support.
Support [supported] Support guide, doctor bundles, GitHub issues, private security reports. Sources: lemon:support.
Free forever open-source software (MIT); only provider costs apply; free scenarios work, including local models, BYO machines and iOS via source builds.
Scope
Surfaces: Lemon TUI (terminal), Lemon Bot (web, macOS and iOS apps; separate product in the same repository) · Version: release v2026.11.11 (2026-11-14, commit 4d94b3c) · Plan: Open source (MIT), self-hosted; user pays model providers and hosts · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-17 (5 days old)
Agent cross-check
2026-11-17
10 atomic answers
Ongoing free [supported] MIT software. Sources: lemon:license.
Trial [supported] Not applicable. Sources: lemon:license.
No Lemon pricing: free MIT software; model and host costs are third-party. Classification: no paid plan.
Scope
Surfaces: Lemon TUI (terminal), Lemon Bot (web, macOS and iOS apps; separate product in the same repository) · Version: release v2026.11.11 (2026-11-14, commit 4d94b3c) · Plan: Open source (MIT), self-hosted; user pays model providers and hosts · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Stable: TUI, Web UI, control plane, Telegram/Discord text channels, source and Linux x86_64 release tarballs; preview: goals, kanban, cron, browser automation, LSP, checkpoints, media; native Windows and hosted service not supported; terminal access runs as the host account (line ~194).
Kind
source-inspected
Locator
Supported for 1.0; Channel Support; Automation and Cron; Not Supported for 1.0
All top-level runs use the native executor; task personas spawn native child sessions; agent delegates to a named execution node over an authenticated control-plane socket; omp is a delegate driver; A2A peers separate.
Lemon Bot is a separate Bun/TypeScript product: backend (SQLite, OIDC/SCIM adapters, MCP /mcp, push), React web, SwiftUI macOS and iOS apps; each Bot owned by one human and assigned a machine; groups coordinate 2-6 Bots.
TOML config with cumulative run/session token and dollar budgets (enforced, zero blocks), optional tool-turn cap, max_concurrent_runs, routing and provider settings.
Kind
source-inspected
Locator
[budgets]; max_concurrent_runs; cap on tool-using turns; LEMON_NODE_CAPABILITIES
omp (oh-my-pi) is a separate coding agent Lemon can start, monitor, steer, cancel and resume over omp --mode rpc, optionally in managed git worktrees; Lemon passes no provider credentials to it.
States no managed hosted service or native desktop app, Windows outside support, credentials not kept from tools, cron/goals lack production guarantees.
Local same-OS-user sign-in, owner/admin/member workspace roles that never grant access to another user Bot, invite tokens, OIDC provider routes with requireSSO, device pairing for iPhone.
Kind
source-inspected
Locator
§2 Accounts and ACL; OIDC routes (~1893); invite roles
Opt-in leased coding then independent review then exact-tree commit then optional publication (push/PR never implicit); restart recovery keeps lease and run IDs; a second review rejection blocks the card.
Command guards are not a sandbox; egress control is tool-level not an OS network sandbox; the helper is not a sandbox and every Bot and subprocess shares the host user.