Compare Lemon
May 20, 2026 ยท View on GitHub
Last reviewed: 2026-05-15
Lemon is a local-first AI agent runtime. It is not trying to be only a chat UI, only a coding CLI, or only an eval harness. The product goal is "Hermes, but better, on the BEAM": reach Hermes-level daily-agent capability, then use OTP supervision, process isolation, event streams, durable state, and runtime introspection to make those capabilities more operable.
Positioning
| Category | What users usually get | Where Lemon is aiming |
|---|---|---|
| Hosted assistants | Fast onboarding, managed infrastructure, limited local control | Local runtime ownership, local files and secrets, configurable engines, supportable self-hosting |
| Single-engine coding CLIs | Strong terminal workflows tied to one engine | Multi-engine execution through Lemon, Codex, Claude, OpenCode, Pi, Kimi, and native Lemon engines |
| Agent harnesses | Repeatable tool loops, transcripts, and eval focus | Hermes-class harness behavior combined with BEAM-supervised memory, skills, channels, browser/media workers, terminal backends, and operator interfaces |
| Chat bridges | Messaging access to an assistant | Channel adapters connected to the same runtime, runs, approvals, sessions, and diagnostics |
| Internal automation scripts | Local control but limited product surface | Supervised BEAM runtime, JSON-RPC control plane, Web/TUI/Telegram surfaces, doctor checks, release profiles |
Main Differentiators
| Area | Lemon direction | Current launch evidence |
|---|---|---|
| Runtime model | Supervised local-first runtime with explicit control-plane APIs | Architecture Overview, BEAM Agents |
| Engine model | Multi-engine architecture rather than one model-provider path | Model Selection, Configuration |
| Harness behavior | Tool execution, approval, transcript, eval, and long-running run support | Hermes Feature Matrix, Hermes Parity Scorecard, Testing |
| Memory and skills | Durable context plus reusable task packs | Memory Guide, Skills Overview |
| Interfaces | Terminal, Web, control plane, stable Telegram and Discord text-first support, and preview gateway adapters | Interface Supportability Audit |
| BEAM parity targets | Browser/media jobs, checkpoint rollback, API/editor adapters, terminal backends, persistent goals, kanban boards, LSP diagnostics, cron, provider routing, and plugin hosts as supervised runtime surfaces | Hermes Feature Matrix, Mainstream Readiness Plan |
| Operations | Doctor checks, support bundles, release profiles, smoke tests, and quality gates | Release Checklist, Safety |
Reality Check
Lemon is pre-1.0. The source install path, release profiles, product smoke, docs site, support bundle, and Web operations views are being hardened toward the stable launch goal.
What is ready enough to evaluate:
- source install on a developer machine
- provider configuration through setup docs and secrets commands
- local runtime startup through
./bin/lemon-devor./bin/lemon - doctor diagnostics and redacted support bundles
- Hermes-class parity tracking through the launch scorecard
- first-party text web search/fetch behavior in supported agent runs
- Web operations pages for runtime health, recent runs, run detail, and approvals
- preview operator-controlled cron and scheduled automation through first-party runtime/Web paths
- release artifact profiles verified locally
Current BEAM parity targets that are not yet stable public promises:
- final launch screenshots and videos
- ACP editor integration or OpenAI-compatible Chat Completions/Responses API parity
- stable checkpoint/rollback beyond the preview file-tool boundary
- persistent
/goal-style continuation loops - durable multi-agent kanban boards
- LSP semantic diagnostics after file edits
- production-grade cron scheduling guarantees or unrestricted model-facing cron management
- first-class browser automation, media generation, image analysis, or voice/TTS behavior
- provider routing, fallback providers, credential pools, and profile distribution parity
- full Web operations coverage for skills, logs, channels, and deeper config
- broad clean-container or clean-VM install matrix
- hosted service support
- Windows-native support outside WSL experimentation
- Discord behavior beyond the live-proven text-first and file-delivery boundary
- production support for third-party plugins or unofficial MCP servers
These are not rejected features. They are the next parity surfaces to build with BEAM supervision, explicit state machines, telemetry, support bundles, and live proof before broad public claims.
When Lemon Is the Right Fit
Use Lemon when you want:
- a local-first assistant runtime that can work inside real repositories
- a multi-engine setup instead of committing to one coding CLI
- durable project memory and reusable skills
- channel access without losing runtime observability
- a supportable self-hosted agent system with quality gates
Do not pick Lemon yet if you need:
- a fully managed hosted assistant
- one-click public binary installation across all operating systems
- a non-technical end-user product
Evaluation Path
- Install from Install Lemon.
- Run
mix lemon.doctor. - Start the runtime with
./bin/lemon-dev /path/to/project. - Exercise a deterministic flow from Demo Lemon.
- Check current gaps in the Mainstream Readiness Plan.
- Use Support if you hit setup or runtime issues.