50 of 51 criteria have a sourced finding; 49 were also cross-checked by a second agent. Every comparison that includes Luvus 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-first. A single Rust binary runs the TUI on macOS (Apple silicon and Intel), Linux (x86_64, arm64), FreeBSD amd64 and Windows x86_64; the CLI controls the same server; an optional Luvus Web bridge serves a browser client (read-only by default, --control opt-in) that works on phones behind a TLS tunnel; narrow SSH terminals get a touch layout. No native iOS/Android app and no editor extension.
Scope
Surfaces: Luvus terminal UI and CLI (luvus binary; local, named-session and SSH-attached), Luvus Web (optional browser client bridge, luvus web), Programmatic surface (JSON control socket, CLI verbs, UHP 1.0 NDJSON, uhp access gateway) · Version: v0.14.3 (tag, release 2026-09-30, commit 54003ce9568acb2977e4bbdbb30a61f99faa0465); source pass 2026-11-16 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
Not a desktop GUI app: the desktop client is a terminal UI.
Browser client needs a user-provided TLS tunnel for phone access; no native phone app.
No editor extension in the pinned release.
9 atomic answers
Desktop os [partial] Release assets and docs ship the terminal UI for macOS (arm64, x86_64), Linux (x86_64, arm64), FreeBSD amd64 and Windows x86_64 (Windows Terminal); no desktop GUI window, no Windows ARM64 build. Sources: luvus:release, luvus:install, luvus:faq.
Mobile apps [unsupported] Release asset list and docs contain no iOS or Android application; phones use the browser bridge or an SSH terminal app. Sources: luvus:release, luvus:web, luvus:mobile.
Browser [supported] luvus web serves a browser client for live workspaces, terminals and agent titles from a loopback bridge with one-use pairing. Sources: luvus:web, luvus:websrc.
Mobile browser [partial] The browser client works on phones (touch controls dock, viewport-following terminal, file upload) but needs the user to run a trusted TLS tunnel because the bridge is loopback-only. Sources: luvus:web.
Cli [supported] The luvus CLI exposes noun-verb commands (workspace, tab, pane, agent, task, automation, machine, web, uhp, doctor, update) over the local socket. Sources: luvus:concepts, luvus:uhp, luvus:install.
Editor extensions [unsupported] Bounded search of README, docs and repository tree (terms extension, vsix, marketplace, plugin for IDE) finds only a Codex plugin/skill and modules, not an IDE extension. Sources: luvus:readme, luvus:codexplugin, luvus:modules.
Task actions [partial] TUI and CLI start agents, send prompts, answer blocked prompts with agent keys and resume sessions; the browser can steer only with --control; DIFF review is read-only. Sources: luvus:msg, luvus:agents, luvus:web, luvus:diff.
Notifications [partial] Optional sound cues for done/blocked, sidebar state, silent notifications for red PR checks; no mobile push. Sources: luvus:agents, luvus:git.
Cross device continuity [supported] The server keeps sessions alive; any new client (TUI via --remote, SSH, browser pairing) attaches to the same live panes. Sources: luvus:concepts, luvus:remote, luvus:web.
Luvus does not embed a harness: it runs many third-party agent CLIs untouched in terminal panes, detects them by process and screen, and adds resume, fork, usage and hooks per compiled-in adapter. Model-provider choice is entirely the agents' own. Custom agents can be taught via detection manifests.
Scope
Surfaces: Luvus terminal UI and CLI (luvus binary; local, named-session and SSH-attached), Luvus Web (optional browser client bridge, luvus web), Programmatic surface (JSON control socket, CLI verbs, UHP 1.0 NDJSON, uhp access gateway) · Version: v0.14.3 (tag, release 2026-09-30, commit 54003ce9568acb2977e4bbdbb30a61f99faa0465); source pass 2026-11-16 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
custom_adapters: User manifests in ~/.luvus/manifests/<agent>.toml teach detection of a new agent; resume/fork/hook operations exist only for compiled-in adapters, and arbitrary executables can be started for ORCH tasks via --agent argv.
session_integration: Agents run as ordinary processes in PTY panes (launched terminal command) with status read from process/screen; optional hooks and native-store readers give exact session ownership, resume and fork where an adapter implements them.
5 atomic answers
Harnesses [supported] Named supported agents: Claude Code, GitHub Copilot CLI, Codex, Arc Studio CLI, Antigravity CLI, Letta Code, opencode, Kimi, Grok, Hermes CLI, Pi, Oh My Pi, Muse Code, Fx, Cursor, Kilo Code, Devin, Gemini, Aider, Amp, Droid, Qwen, Kiro. Sources: luvus:readme, luvus:agentsrc.
Model providers [supported] Luvus has no model-provider layer; each agent chooses its own provider and models. Mission Control reads usage and model names the agents record. Sources: luvus:agents, luvus:concepts.
Custom adapters [partial] User manifests in ~/.luvus/manifests/<agent>.toml teach detection of a new agent; resume/fork/hook operations exist only for compiled-in adapters, and arbitrary executables can be started for ORCH tasks via --agent argv. Sources: luvus:faq, luvus:orch, luvus:agentsrc.
Session integration [partial] Agents run as ordinary processes in PTY panes (launched terminal command) with status read from process/screen; optional hooks and native-store readers give exact session ownership, resume and fork where an adapter implements them. Sources: luvus:concepts, luvus:agents.
Mixed harness operation [supported] Panes of Claude Code, Codex, Copilot and others run side by side in one workspace and can prompt one another via agent prompt; ORCH workers can use different agents per task. Sources: luvus:msg, luvus:orch, luvus:agents.
Luvus runs each agent with its own native login and credentials, so existing agent subscriptions or API keys work as the agent supports; Luvus holds no keys and sells no credits or models. Account switching and provider restrictions are the agents' concern.
Scope
Surfaces: Luvus terminal UI and CLI (luvus binary; local, named-session and SSH-attached), Luvus Web (optional browser client bridge, luvus web), Programmatic surface (JSON control socket, CLI verbs, UHP 1.0 NDJSON, uhp access gateway) · Version: v0.14.3 (tag, release 2026-09-30, commit 54003ce9568acb2977e4bbdbb30a61f99faa0465); source pass 2026-11-16 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
Subscription/API support is inherited from each agent CLI; Luvus documents no per-plan details.
Provider terms on automation/third-party use are not captured.
7 atomic answers
Agent subscriptions [supported] Agents run untouched under the user's own login, so an installed agent's subscription route works; automation workers require the agent installed and authenticated for the server user. Sources: luvus:concepts, luvus:auto.
Api accounts [supported] Agents launched in panes use whatever API key environment they are given; Luvus adds nothing between the agent and its provider. Sources: luvus:concepts, luvus:privacy.
Vendor credits [unsupported] Luvus is free local software with no vendor credits or hosted model service. Sources: luvus:privacy, luvus:site.
Local models [partial] Any agent that can use a local model works in a pane, but Luvus has no local-model integration of its own. Sources: luvus:concepts.
Account switching [unsupported] Bounded search of docs and agent adapters (terms account, profile switch, login) finds no account manager; credentials stay in each agent. Sources: luvus:agents, luvus:agentsrc.
Vendor account requirement [supported] No Luvus account or login exists; luvus.dev has no account system. Sources: luvus:privacy, luvus:site.
Provider restrictions [unknown] Third-party provider rules for running their CLIs unattended are not stated in Luvus docs.
Install with a one-line script, Homebrew, deb/rpm, Nix or PowerShell, run luvus in a project folder and start any agent in a pane; luvus doctor checks git, gh and ssh. Non-Git directories work in the TUI and workspace-mode tasks; worktree features need Git; GitHub views need gh. SSH remote hosts can be set up from the TUI with managed binary install; no managed cloud.
Scope
Surfaces: Luvus terminal UI and CLI (luvus binary; local, named-session and SSH-attached), Luvus Web (optional browser client bridge, luvus web), Programmatic surface (JSON control socket, CLI verbs, UHP 1.0 NDJSON, uhp access gateway) · Version: v0.14.3 (tag, release 2026-09-30, commit 54003ce9568acb2977e4bbdbb30a61f99faa0465); source pass 2026-11-16 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
Worktree mode requires a Git repository; PR/issue views need an authenticated gh.
No managed-cloud option; remote setup assumes an SSH-reachable host.
7 atomic answers
First task setup [supported] Install, run luvus in a project, split a pane and start an agent (auto-detected); ORCH tasks add title/paths/gate and start with s. Agent login is manual. Sources: luvus:install, luvus:readme, luvus:orch.
No git [supported] Workspaces are any folder; workspace-mode tasks run branchless in the existing directory; worktree mode reports not a git repo. Sources: luvus:concepts, luvus:orch.
Local git without remote [supported] Git tab reads local commits, branches and status with git alone; worktrees and the merge gate need only a local repository. Sources: luvus:git, luvus:orch.
Hosted git [partial] PRs, issues and checks need the gh CLI authenticated; without gh the tab degrades to a local viewer. Sources: luvus:git.
Prerequisite guidance [supported] luvus doctor checks git, gh and ssh; docs list the macOS Ctrl+Space conflict and SSH prerequisites. Sources: luvus:readme, luvus:faq, luvus:machines.
Managed cloud setup [unsupported] The project operates no hosted service and offers no managed cloud environment. Sources: luvus:privacy, luvus:site.
Byo vps onboarding [supported] Remote Machine form or luvus machine add checks SSH, finds or installs a compatible Luvus binary with explicit approval, and saves the profile. Sources: luvus:machines, luvus:remote.
Everything in the UI is also a CLI command and a typed UHP 1.0 method over a local JSON socket (owner-only), covering workspaces, panes, agents, tasks, automations, files, Git, DIFF and modules, with events streaming. A loopback uhp access gateway offers scoped, expiring remote access. The documented web client is an internal TypeScript package, not a published SDK. Luvus does not expose an MCP server.
Scope
Surfaces: Luvus terminal UI and CLI (luvus binary; local, named-session and SSH-attached), Luvus Web (optional browser client bridge, luvus web), Programmatic surface (JSON control socket, CLI verbs, UHP 1.0 NDJSON, uhp access gateway) · Version: v0.14.3 (tag, release 2026-09-30, commit 54003ce9568acb2977e4bbdbb30a61f99faa0465); source pass 2026-11-16 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
Not separately cross-checked
Automations and parts of the board are beta; no public SDK package.
8 atomic answers
Cli [supported] luvus noun-verb CLI including task, lease, automation, agent, pane, workspace, machine, web and uhp commands with help all. Sources: luvus:concepts, luvus:orch, luvus:uhp.
Api [supported] Newline-delimited JSON control API (UHP 1.0) over a Unix socket or Windows named pipe, with schema, capabilities, snapshot and events discovery. Sources: luvus:uhp.
Sdk [unsupported] The only TypeScript client (@luvus/uhp-client) is private, unpublished tooling for the bundled web app; no public SDK in the repository or docs. Sources: luvus:webclient, luvus:uhp.
Mcp server [unsupported] Bounded search of src, docs and web packages for mcp / Model Context Protocol finds only detection fixtures; Luvus exposes UHP/CLI and a skill, not an MCP server. Sources: luvus:uhp, luvus:codexplugin.
Webhooks [partial] Luvus has no built-in inbound or outbound webhook. The documented example module examples/modules/agent-ping posts a webhook when an agent goes blocked or finishes; otherwise events are consumed through luvus events / UHP streams. Sources: luvus:uhp, luvus:orch, luvus:modwebhook.
Operations [supported] Create (task add, agent start), inspect (get/list/read/snapshot), steer (agent prompt/keys), stop (task release, pane close) and review (task done gate, DIFF notes) are all available via CLI/UHP. Sources: luvus:orch, luvus:msg, luvus:diff, luvus:uhp.
Authentication [supported] Local socket authority is the OS account (0700/0600); remote access uses paired, scoped, expiring tokens (read, control, orchestration scopes). Sources: luvus:security, luvus:uhpremote, luvus:auto.
Stability [partial] UHP is declared a stable 1.0 contract (luvus-uhp 1.0) with a conformance suite, while the project releases frequently and Automations are labeled BETA. Sources: luvus:uhp, luvus:auto.
Luvus is not an MCP client or a model runtime; MCP, skills and tool permissions are handled by each agent. Luvus itself is extended through modules (programs in any language with sidebar panels, panes, bar widgets, actions, worktree providers), themes, and an optional Luvus agent skill/Codex plugin.
Scope
Surfaces: Luvus terminal UI and CLI (luvus binary; local, named-session and SSH-attached), Luvus Web (optional browser client bridge, luvus web), Programmatic surface (JSON control socket, CLI verbs, UHP 1.0 NDJSON, uhp access gateway) · Version: v0.14.3 (tag, release 2026-09-30, commit 54003ce9568acb2977e4bbdbb30a61f99faa0465); source pass 2026-11-16 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
No MCP client in Luvus itself; tool and MCP configuration is inherited from each agent.
Modules run local commands with user authority; no per-module permission model beyond install confirmation.
7 atomic answers
Mcp client [unsupported] Bounded search for mcp/Model Context Protocol in src, docs and web packages finds no MCP client; agents inside panes use their own. Sources: luvus:concepts, luvus:modules.
Plugins [supported] Modules declared by luvus-module.toml add actions, events, settings, startup hooks, panes, docks and bar widgets; installable from GitHub repos. Sources: luvus:modules, luvus:readme.
Custom tools [partial] Modules can add actions and panes; Luvus offers no custom tool registry for agents beyond the CLI/UHP surface they can call. Sources: luvus:modules, luvus:uhp.
Instructions import [partial] The optional luvus skill is copied into detected agent skill directories after luvus skill enable; Luvus does not import or manage other instruction files. Sources: luvus:codexplugin, luvus:security.
Authentication [partial] Modules inherit the user's environment; install requires confirmation of declared commands; builds run with a scrubbed environment. Sources: luvus:security, luvus:modules.
Permission scope [partial] Modules run with the user's OS authority after confirmation; scoped delegated tokens apply to UHP access, not to local modules. Sources: luvus:security, luvus:uhpremote.
Integration owner [supported] Luvus owns pane/terminal detection, modules and the skill; agents own MCP and tool connections. Sources: luvus:concepts, luvus:modules.
Pure Rust terminal UI (ratatui) in a single static binary; the optional browser client is a TypeScript web app bundled with the binary and served by the bridge. There is no Electron, Tauri, native desktop window or mobile app.
Scope
Surfaces: Luvus terminal UI and CLI (luvus binary; local, named-session and SSH-attached), Luvus Web (optional browser client bridge, luvus web), Programmatic surface (JSON control socket, CLI verbs, UHP 1.0 NDJSON, uhp access gateway) · Version: v0.14.3 (tag, release 2026-09-30, commit 54003ce9568acb2977e4bbdbb30a61f99faa0465); source pass 2026-11-16 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
4 atomic answers
Desktop implementation [supported] Cargo.toml and docs show a Rust terminal application using ratatui; the desktop client is the terminal UI inside the user's terminal emulator. Sources: luvus:cargo, luvus:readme.
Mobile implementation [unsupported] No mobile application exists; phones use the browser bridge (web app) or an SSH terminal. Sources: luvus:web, luvus:mobile.
Hybrids [supported] Hybrid: Rust server with terminal UI client plus a bundled TypeScript web client (web/packages/app, web/bridge) over UHP. Sources: luvus:webclient, luvus:web.
Implementation evidence [supported] Pinned Cargo.toml, web package manifests and architecture docs. Sources: luvus:cargo, luvus:webclient.
Tasks are created locally on the ORCH board (title, paths, deps, gate, prompt) or via CLI; prompts are typed into agent panes or sent by Commander; no issue import from external trackers. Git tab lists GitHub issues and PRs read-only via gh. Automations trigger by time only.
Scope
Surfaces: Luvus terminal UI and CLI (luvus binary; local, named-session and SSH-attached), Luvus Web (optional browser client bridge, luvus web), Programmatic surface (JSON control socket, CLI verbs, UHP 1.0 NDJSON, uhp access gateway) · Version: v0.14.3 (tag, release 2026-09-30, commit 54003ce9568acb2977e4bbdbb30a61f99faa0465); source pass 2026-11-16 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
No external tracker import or sync; GitHub issues are viewable only.
No chat or Git event triggers; automations are time-based (BETA).
9 atomic answers
Local creation [supported] ORCH board a / luvus task add create tasks with title, paths, dependencies, gate and prompt. Sources: luvus:orch.
Prompt intake [supported] Prompts go into agent panes, Commander composer, or task prompt fields. Sources: luvus:commander, luvus:orch.
External import [unsupported] Bounded search of docs and src/git for issue import found only a read-only Issues view; no import into tasks. Sources: luvus:git, luvus:orch.
Chat git triggers [unsupported] Docs state the automation beta is time-triggered; ORCH dependencies do not trigger automations; no push/PR/chat triggers. Sources: luvus:auto.
Authoritative tracker [supported] The ORCH ledger (orch.json) is the only task record; GitHub issues are not linked to it. Sources: luvus:orch, luvus:config.
Stable ids [partial] Task ids t1, t2 are sequential within a named session ledger; no cross-session or external IDs. Sources: luvus:orchsrc, luvus:orch.
Sync [unsupported] No synchronization with any external tracker exists in the pinned release. Sources: luvus:git, luvus:orch.
Supported edits [partial] Tasks are editable until started; GitHub issue edits are not offered, only viewing. Sources: luvus:orch, luvus:git.
External roundtrips [supported] Any issue work beyond reading in the Git tab happens on GitHub itself. Sources: luvus:git.
A task carries a prompt/briefing, file-path globs, dependencies and an optional quality-gate command; the prompt is editable until the task starts and progress notes are appended; notes and output persist in orch.json. There are no acceptance-criteria objects, plan editors or revision history.
Scope
Surfaces: Luvus terminal UI and CLI (luvus binary; local, named-session and SSH-attached), Luvus Web (optional browser client bridge, luvus web), Programmatic surface (JSON control socket, CLI verbs, UHP 1.0 NDJSON, uhp access gateway) · Version: v0.14.3 (tag, release 2026-09-30, commit 54003ce9568acb2977e4bbdbb30a61f99faa0465); source pass 2026-11-16 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
No formal plans, acceptance criteria or revision history; the gate command is the closest check.
7 atomic answers
Plans [partial] Task briefing (prompt, paths, deps) is a starting plan; no separate plan object. Sources: luvus:orch.
Acceptance criteria [partial] The optional gate command acts as an executable acceptance check; no written criteria field. Sources: luvus:orch.
Editors [partial] luvus task update --prompt/--prompt-file edits a task until it starts; the TUI form edits fields at creation. Sources: luvus:orch.
Revisions [unsupported] Bounded search of src/orch and docs finds no prompt revision history; retry archives a bounded attempt summary only. Sources: luvus:orch, luvus:orchsrc.
Implementation links [partial] A task records its branch, worktree and the integration commit after merge. Sources: luvus:orch.
Amendment [partial] Prompt and notes can be changed before start; after start only notes and status update. Sources: luvus:orch.
Restart persistence [supported] Tasks, leases and notes persist in the session's orch.json across server restarts. Sources: luvus:orch, luvus:config.
Flat tasks with dependency edges: a task cannot start until dependencies are done (worktree-backed dependents wait for merged), path leases prevent overlapping assignment, and a retry creates a new attempt. No epics, parent/child nesting or task-to-epic growth.
Scope
Surfaces: Luvus terminal UI and CLI (luvus binary; local, named-session and SSH-attached), Luvus Web (optional browser client bridge, luvus web), Programmatic surface (JSON control socket, CLI verbs, UHP 1.0 NDJSON, uhp access gateway) · Version: v0.14.3 (tag, release 2026-09-30, commit 54003ce9568acb2977e4bbdbb30a61f99faa0465); source pass 2026-11-16 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
No epics or hierarchy; dependencies are a flat list.
Workflow is fixed to the task lifecycle.
9 atomic answers
Epics [unsupported] Bounded search of docs and src/orch for epic/parent/child finds none. Sources: luvus:orch, luvus:orchsrc.
Hierarchy [unsupported] Tasks are a flat list with dependency edges; no nesting. Sources: luvus:orch.
Blockers [supported] Deps field lists blocking task ids; start is refused with deps not done. Sources: luvus:orch.
Readiness [supported] task.ready events and task next select ready work from the project queue. Sources: luvus:orch.
Enforcement [supported] task start validates dependencies and path lease before creating a worker; dependents wait for merged. Sources: luvus:orch, luvus:orchsrc.
State propagation [partial] Dependents become claimable when dependencies finish; no parent roll-up. Sources: luvus:orch.
Task to epic [unsupported] No epic concept exists. Sources: luvus:orch.
Identity retention [partial] A retried task keeps its id, notes and previous_attempts history. Sources: luvus:orch.
Workflow constraints [partial] Lifecycle queued > claimed/running > done/review > merging > merged is fixed; manual or now start choice. Sources: luvus:orch.
Luvus does not own project memory: agents keep their own instructions, skills and memory. Luvus persists workspaces, layouts, optional pane screens and agent resume metadata, can resume or fork agent conversations with their context, and installs an optional luvus skill. AGENTS.md at repo root guides maintainers.
Scope
Surfaces: Luvus terminal UI and CLI (luvus binary; local, named-session and SSH-attached), Luvus Web (optional browser client bridge, luvus web), Programmatic surface (JSON control socket, CLI verbs, UHP 1.0 NDJSON, uhp access gateway) · Version: v0.14.3 (tag, release 2026-09-30, commit 54003ce9568acb2977e4bbdbb30a61f99faa0465); source pass 2026-11-16 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
No Luvus-managed memory, project docs index or provenance/citation controls.
10 atomic answers
Instructions [partial] No Luvus instruction store; the optional skill is the only Luvus-provided instruction content. Sources: luvus:codexplugin.
Skills [partial] luvus skill enable copies a version-matched skill into detected agent skill directories. Sources: luvus:codexplugin, luvus:security.
Project docs [unsupported] Bounded search finds no project doc store; FILES dock previews Markdown/Mermaid read-only. Sources: luvus:files.
Memory [unsupported] No cross-session or cross-harness memory; resume reopens an agent's own conversation. Sources: luvus:agents.
Scope [partial] Resume and fork scope is per agent conversation and project folder. Sources: luvus:agents.
Provenance [unsupported] No provenance tracking for context items. Sources: luvus:agents, luvus:config.
Correction [unsupported] No memory or context correction feature in Luvus. Sources: luvus:agents.
Deletion [partial] Hide (✕) removes a resumable entry from the list without touching the agent store; rm -rf ~/.luvus resets state. Sources: luvus:agents, luvus:faq.
Freshness [unsupported] No stale-context controls beyond choosing resume vs fork vs new pane. Sources: luvus:agents.
Takeover continuity [partial] Another client attaches to the same live panes; after server loss the next server rebuilds layout and resumes supported native sessions. Sources: luvus:concepts, luvus:agents.
Luvus provides a global fuzzy finder over file names, workspace objects and retained terminal output and a Git-aware file tree, but no code indexing, embeddings, external knowledge or architecture checks; agents do their own retrieval. Clipboard images can be pasted into panes.
Scope
Surfaces: Luvus terminal UI and CLI (luvus binary; local, named-session and SSH-attached), Luvus Web (optional browser client bridge, luvus web), Programmatic surface (JSON control socket, CLI verbs, UHP 1.0 NDJSON, uhp access gateway) · Version: v0.14.3 (tag, release 2026-09-30, commit 54003ce9568acb2977e4bbdbb30a61f99faa0465); source pass 2026-11-16 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
No code-content search or index; file search is path-only.
No citation, conflict detection or review-time enforcement.
10 atomic answers
Code search [partial] Fuzzy finder searches file names/paths and retained output but not file contents. Sources: luvus:search.
Indexing [partial] File path index per workspace honoring Git ignore; no content index. Sources: luvus:search, luvus:files.
The ORCH board is a local task list with ids, titles, paths, dependencies, gates, prompts, notes, worker location and states, editable until start, with Manual vs Now start (an idea can be queued unstarted). It has no discussion, labels, assignment, priority, search, archive or project views beyond per-workspace project scoping.
Scope
Surfaces: Luvus terminal UI and CLI (luvus binary; local, named-session and SSH-attached), Luvus Web (optional browser client bridge, luvus web), Programmatic surface (JSON control socket, CLI verbs, UHP 1.0 NDJSON, uhp access gateway) · Version: v0.14.3 (tag, release 2026-09-30, commit 54003ce9568acb2977e4bbdbb30a61f99faa0465); source pass 2026-11-16 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
No discussion, labels, priority, assignee, archive or epic views.
External tracker still needed for anything beyond the local list.
17 atomic answers
Create [supported] a on the board or luvus task add. Sources: luvus:orch.
Edit [partial] Prompt/paths editable until the task starts; later only notes and status. Sources: luvus:orch.
Discuss [unsupported] No discussion threads on tasks; notes are agent progress notes. Sources: luvus:orch.
Prioritize [unsupported] Bounded search finds no priority field; order is creation order. Sources: luvus:orch, luvus:orchsrc.
Agents in panes can run the same luvus task commands humans use: add, update, heartbeat with context usage, claim via task start/next, done and merge; leases, dependencies and notes are shared through the single ledger, and the board and events show changes live. No per-user attribution or permissions exist beyond OS user.
Scope
Surfaces: Luvus terminal UI and CLI (luvus binary; local, named-session and SSH-attached), Luvus Web (optional browser client bridge, luvus web), Programmatic surface (JSON control socket, CLI verbs, UHP 1.0 NDJSON, uhp access gateway) · Version: v0.14.3 (tag, release 2026-09-30, commit 54003ce9568acb2977e4bbdbb30a61f99faa0465); source pass 2026-11-16 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
Writes are not attributed to a named human or agent identity beyond the worker pane; single OS-user trust model.
14 atomic answers
Shared ids [supported] Agents and humans use the same t-ids and lease records. Sources: luvus:orch, luvus:orchsrc.
Read [supported] task list/get and events are available to agents. Sources: luvus:orch.
Create [supported] luvus task add from any pane. Sources: luvus:orch.
Update [supported] task update --status/--note/--prompt and heartbeat. Sources: luvus:orch.
Claim [supported] task next --start and task start claim queued work; the single-writer loop prevents double claims. Sources: luvus:orch, luvus:arch.
Each pane is a real PTY owned by one detached server, so many agent panes and ORCH workers run concurrently across workspaces; the AGENTS sidebar, Mission Control and the board show blocked/working/done/idle states. The only documented bounds are bounded automation counts (256 definitions); no per-user concurrency quota.
Scope
Surfaces: Luvus terminal UI and CLI (luvus binary; local, named-session and SSH-attached), Luvus Web (optional browser client bridge, luvus web), Programmatic surface (JSON control socket, CLI verbs, UHP 1.0 NDJSON, uhp access gateway) · Version: v0.14.3 (tag, release 2026-09-30, commit 54003ce9568acb2977e4bbdbb30a61f99faa0465); source pass 2026-11-16 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
quotas: Automation bounds (256 definitions, 2,048 run records, 32 KiB prompts); no concurrency quota.
observed_concurrency: Maximum concurrency is not documented or measured by this catalog.
5 atomic answers
Concurrent sessions [supported] Multiple panes and named-session servers run independently. Sources: luvus:concepts.
Concurrent tasks [supported] Several ORCH workers run in parallel in separate worktrees or task tabs; leases keep paths disjoint. Sources: luvus:orch.
Quotas [partial] Automation bounds (256 definitions, 2,048 run records, 32 KiB prompts); no concurrency quota. Sources: luvus:auto.
Observed concurrency [unknown] Maximum concurrency is not documented or measured by this catalog.
Status visibility [supported] Sidebar and Mission Control show blocked/working/done/idle with live updates. Sources: luvus:agents.
Humans or agents start tasks onto agent panes; leases give enforced exclusive path reservations within a project and dependency checks gate starts; task next picks queued ready work; automations queue at most one pending run. No named assignees or routing rules.
Scope
Surfaces: Luvus terminal UI and CLI (luvus binary; local, named-session and SSH-attached), Luvus Web (optional browser client bridge, luvus web), Programmatic surface (JSON control socket, CLI verbs, UHP 1.0 NDJSON, uhp access gateway) · Version: v0.14.3 (tag, release 2026-09-30, commit 54003ce9568acb2977e4bbdbb30a61f99faa0465); source pass 2026-11-16 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
No human assignees or routing rules; leases cover declared paths only and do not stop external writers.
7 atomic answers
Human assignment [partial] A human starts a task onto an agent; no assignee field for people. Sources: luvus:orch.
Agent assignment [supported] task start --agent and automation targets choose the agent. Sources: luvus:orch, luvus:auto.
Claims [supported] task claimed/running states and the single-writer loop. Sources: luvus:orch, luvus:arch.
Routing [partial] Per-project queues; no skill or capacity routing. Sources: luvus:orch.
Duplicate prevention [supported] Lease conflict rejects overlapping paths; automations key occurrences by definition and time. Sources: luvus:orchsrc, luvus:auto.
Ownership enforcement [partial] Leases are enforced at start but do not stop agents writing outside declared paths in workspace mode. Sources: luvus:orch.
Product-supplied delegation: one agent pane can start, name, prompt, wait for, read and send keys to other agent panes through luvus agent commands (any harness), with optional skill and = shorthand; ORCH lets a coordinator create worktree workers. Child identity is the pane/alias and results are read from retained output or tasks. Not a built-in coordinator agent.
Scope
Surfaces: Luvus terminal UI and CLI (luvus binary; local, named-session and SSH-attached), Luvus Web (optional browser client bridge, luvus web), Programmatic surface (JSON control socket, CLI verbs, UHP 1.0 NDJSON, uhp access gateway) · Version: v0.14.3 (tag, release 2026-09-30, commit 54003ce9568acb2977e4bbdbb30a61f99faa0465); source pass 2026-11-16 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
Delegation is pasted prompts and screen reads, not structured messages; no automatic role assignment.
12 atomic answers
Roles [partial] Roles are conventions (aliases like lead/reviewer); ORCH assigns task/worker. Sources: luvus:msg, luvus:orch.
Model harness effort [partial] agent start --kind chooses harness; model and effort are the agent's own settings; automation access chooses native flags. Sources: luvus:msg, luvus:auto.
Messages [supported] agent prompt pastes and submits text into another agent's input; agent keys answers prompts. Sources: luvus:msg.
Results return [supported] agent read returns output; agent prompt --wait blocks until settle; workers can prompt the lead back. Sources: luvus:msg.
Cross harness [supported] Any detected agent kind can be targeted by any other. Sources: luvus:msg, luvus:agents.
Orchestration owner [supported] Luvus ships the delegation commands, skill and ORCH; the coordinator itself is a user-run agent. Sources: luvus:msg, luvus:codexplugin.
Activation [supported] Commands work without configuration; luvus skill enable adds the skill; no experimental flag. Sources: luvus:msg, luvus:codexplugin.
Authentication [supported] Pane env injects socket path and pane id; local OS user trust. Sources: luvus:msg, luvus:security.
Live progress [supported] Sidebar state, agent list and live pane view show child progress. Sources: luvus:agents, luvus:msg.
Retained results [partial] Results persist as retained scrollback and ORCH notes/output; scrollback is bounded (10 MiB default). Sources: luvus:msg, luvus:faq.
Followup [supported] Prompt the same pane again or resume its session. Sources: luvus:msg, luvus:agents.
Beta automations run on one-time, interval, daily or weekly schedules from the detached server (TUI can be closed), starting a fresh ORCH worker or prompting an existing agent, with misfire/overlap policies and bounded history; no event triggers and no automatic retries; stopping the server stops the scheduler.
Scope
Surfaces: Luvus terminal UI and CLI (luvus binary; local, named-session and SSH-attached), Luvus Web (optional browser client bridge, luvus web), Programmatic surface (JSON control socket, CLI verbs, UHP 1.0 NDJSON, uhp access gateway) · Version: v0.14.3 (tag, release 2026-09-30, commit 54003ce9568acb2977e4bbdbb30a61f99faa0465); source pass 2026-11-16 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
Time triggers only; BETA; no retries; owning server must be running.
8 atomic answers
Schedules [supported] Once, interval (≥60s), daily and weekly with IANA timezone. Sources: luvus:auto.
Events [unsupported] Docs state automations are time-triggered and dependencies do not trigger them. Sources: luvus:auto.
Recurring tasks [supported] Each due occurrence creates a fresh ORCH task. Sources: luvus:auto.
Completion conditions [partial] Run history and task gate record result; active-agent delivery is only recorded as delivered. Sources: luvus:auto.
Scheduler location [supported] Detached Luvus server caches the nearest UTC deadline. Sources: luvus:auto.
Overlaps [supported] overlap skip (default) or queue_one. Sources: luvus:auto, luvus:autosrc.
Retries [unsupported] No automatic retry of a failed agent run. Sources: luvus:auto.
Client independence [supported] Closing the TUI does not pause automations; stopping the server does. Sources: luvus:auto.
Humans can steer in any pane, answer blocked prompts, stop or close panes, release tasks and resume agent sessions; blocked state surfaces in the sidebar with optional sound; ORCH marks automation tasks blocked on unknown prompts without auto-approving. No pause primitive and no push notifications.
Scope
Surfaces: Luvus terminal UI and CLI (luvus binary; local, named-session and SSH-attached), Luvus Web (optional browser client bridge, luvus web), Programmatic surface (JSON control socket, CLI verbs, UHP 1.0 NDJSON, uhp access gateway) · Version: v0.14.3 (tag, release 2026-09-30, commit 54003ce9568acb2977e4bbdbb30a61f99faa0465); source pass 2026-11-16 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
No pause/resume of a running agent beyond the agent's own controls; notifications are local sounds, not push.
10 atomic answers
Pause [unsupported] Bounded search of docs and CLI help finds no pause command for running agents. Sources: luvus:agents, luvus:orch.
Steer [supported] Type in the pane, Commander, agent prompt. Sources: luvus:commander, luvus:msg.
Notifications [partial] Optional done/blocked sounds and sidebar state; no remote push. Sources: luvus:agents.
Pending decisions [supported] Blocked agents shown red when a permission prompt is on screen; Mission Control a to answer. Sources: luvus:agents, luvus:msg.
Escalation [partial] ORCH marks scheduled tasks blocked and records the detected prompt. Sources: luvus:orch, luvus:auto.
Visible errors [supported] Gate output, merge conflicts and automation failures are shown on tasks and runs. Sources: luvus:orch, luvus:auto.
Chat terminal parity [supported] The pane is the agent's real terminal, so CLI questions appear as they do natively. Sources: luvus:concepts.
The ◇ orch board lists every task with status, id, title, dependencies, mode and worker location plus leases; the sidebar lists agents with states across workspaces; Mission Control shows agents, tokens, cost and context. No parent/child tree or epic grouping; attention is shown by blocked state.
Scope
Surfaces: Luvus terminal UI and CLI (luvus binary; local, named-session and SSH-attached), Luvus Web (optional browser client bridge, luvus web), Programmatic surface (JSON control socket, CLI verbs, UHP 1.0 NDJSON, uhp access gateway) · Version: v0.14.3 (tag, release 2026-09-30, commit 54003ce9568acb2977e4bbdbb30a61f99faa0465); source pass 2026-11-16 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
No epics or hierarchy view; fleet visualization is a table and sidebar.
8 atomic answers
Fleet fixture [unknown] This catalog does not run products, so no multi-epic fixture was exercised.
Parent child [unsupported] No parent/child tasks. Sources: luvus:orch.
No mandatory workflow: start any agent in a pane or use the board; Manual/Now start, worktree vs workspace mode, access level and schedule are chosen per task/automation. Agent model/effort are agent settings. The UI shows workers, leases and run history; natural-language configuration is whatever the user's agent does through the skill.
Scope
Surfaces: Luvus terminal UI and CLI (luvus binary; local, named-session and SSH-attached), Luvus Web (optional browser client bridge, luvus web), Programmatic surface (JSON control socket, CLI verbs, UHP 1.0 NDJSON, uhp access gateway) · Version: v0.14.3 (tag, release 2026-09-30, commit 54003ce9568acb2977e4bbdbb30a61f99faa0465); source pass 2026-11-16 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
No presets or role templates; coordinator and child roles are not modeled beyond aliases and tasks.
10 atomic answers
Quick task [supported] Start an agent in a pane immediately, or task Now start. Sources: luvus:orch, luvus:readme.
Growing epic [unsupported] No epic concept. Sources: luvus:orch.
Execution is local by default; the same server can run on an SSH-reachable machine you own (luvus --remote or saved machines) where panes keep running after the client disconnects and another device can attach, or a hosted bridge-free SSH app on a phone. Luvus operates no cloud; sleep or shutdown of the host stops execution.
Scope
Surfaces: Luvus terminal UI and CLI (luvus binary; local, named-session and SSH-attached), Luvus Web (optional browser client bridge, luvus web), Programmatic surface (JSON control socket, CLI verbs, UHP 1.0 NDJSON, uhp access gateway) · Version: v0.14.3 (tag, release 2026-09-30, commit 54003ce9568acb2977e4bbdbb30a61f99faa0465); source pass 2026-11-16 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
No vendor cloud; durability depends on the user's host staying up and (on Windows) restarts.
12 atomic answers
Local [supported] Server and PTYs run on the local machine. Sources: luvus:concepts.
Byo remote [supported] luvus --remote host and saved Remote Machine profiles attach to a server on your own host. Sources: luvus:remote, luvus:machines.
Self hosted [partial] The server is local software on any host you run; no separate control plane. Sources: luvus:remote, luvus:concepts.
Managed cloud [unsupported] No vendor-operated compute exists. Sources: luvus:privacy, luvus:site.
Hybrid [supported] Local and remote workspaces sit side by side in one TUI. Sources: luvus:machines.
Provisioning [partial] Setup can install the binary on the remote host over SSH with approval; host provisioning is the user's. Sources: luvus:machines.
Payer [supported] The user pays for their own hosts and agent subscriptions. Sources: luvus:privacy.
Resources [unsupported] Resources are the host's; Luvus imposes none. Sources: luvus:machines.
Region [unknown] Region depends on the user's host.
Expiry [unsupported] No expiry; server lives until stopped or the host reboots. Sources: luvus:concepts.
Client disconnect [supported] Detaching or closing a client leaves server and PTYs running; Luvus Web closing does not stop panes. Sources: luvus:concepts, luvus:web.
Other device continuation [supported] Reattach with luvus --remote, SSH, or a browser bridge from another device. Sources: luvus:remote, luvus:web.
Isolation is worktree-based or none: ORCH worktree mode gives each worker its own Git worktree and branch with merge in a separate integration worktree; workspace mode intentionally shares one checkout. Panes run as the OS user; there are no container or VM options and no network or secret boundaries beyond the agent's own sandbox flags.
Scope
Surfaces: Luvus terminal UI and CLI (luvus binary; local, named-session and SSH-attached), Luvus Web (optional browser client bridge, luvus web), Programmatic surface (JSON control socket, CLI verbs, UHP 1.0 NDJSON, uhp access gateway) · Version: v0.14.3 (tag, release 2026-09-30, commit 54003ce9568acb2977e4bbdbb30a61f99faa0465); source pass 2026-11-16 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
Worktrees are not a security sandbox; access profiles rely on each agent's native flags.
12 atomic answers
Checkout [supported] Workspace mode shares the existing checkout. Sources: luvus:orch.
Branch [supported] Worktree workers use luvus/<task-id> branches. Sources: luvus:orch.
Os sandbox [partial] Only via the agent's native per-run flags (e.g. codex --sandbox read-only); not Luvus-enforced. Sources: luvus:auto, luvus:codexsrc.
Filesystem [partial] Worktrees separate files; panes can access the user's whole account. Sources: luvus:security, luvus:orch.
Process [unsupported] Panes are ordinary user processes. Sources: luvus:security.
Network [unsupported] No network boundary. Sources: luvus:security.
Secrets [unsupported] No secret injection or boundary; agents use the user's environment. Sources: luvus:security.
Code separation [supported] Merges happen in a dedicated integration worktree so the user's checkout is untouched. Sources: luvus:orch.
Security boundary [unsupported] Docs describe a single-user local-trust tool and do not claim hostile-code containment. Sources: luvus:security.
Client detach never stops work; if the server dies (reboot, restart) Luvus saves layout and screens and the next server restores workspaces, tabs, cwd, last screen and resumes supported agent sessions natively (shells restart fresh); orch ledger persists; active workers from a previous server lifetime are recorded as failed. No expiry.
Scope
Surfaces: Luvus terminal UI and CLI (luvus binary; local, named-session and SSH-attached), Luvus Web (optional browser client bridge, luvus web), Programmatic surface (JSON control socket, CLI verbs, UHP 1.0 NDJSON, uhp access gateway) · Version: v0.14.3 (tag, release 2026-09-30, commit 54003ce9568acb2977e4bbdbb30a61f99faa0465); source pass 2026-11-16 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
worker_crash: A crashed pane/agent is detected; ORCH retry creates a new attempt keeping the old record.
task_resume: Tasks persist; running workers become failed on server loss and are retried.
context_loss: Agent-side context returns via native resume where supported; shells and unsupported agents start fresh.
Process reconnect [unsupported] Live processes cannot outlive the server; shells restart. Sources: luvus:concepts.
Task resume [partial] Tasks persist; running workers become failed on server loss and are retried. Sources: luvus:auto, luvus:orch.
State reconstruction [supported] Layout, cwd, last screen and agent sessions rebuilt. Sources: luvus:concepts.
Context loss [partial] Agent-side context returns via native resume where supported; shells and unsupported agents start fresh. Sources: luvus:agents, luvus:concepts.
Duplicate actions [partial] Automations avoid double launch by persisted occurrence keys; uncertain dispatch fails rather than replays. Sources: luvus:auto.
Multi day continuity [partial] Server keeps panes alive until host reboot; after reboot resume restores agents natively. Sources: luvus:concepts, luvus:agents.
Luvus does not manage dependencies, caches, services, ports or secrets for workspaces; worktrees start from Git state and the user or agent installs dependencies. A module worktree provider can run custom creation scripts. Pane environments inject LUVUS_PANE_ID and socket path.
Scope
Surfaces: Luvus terminal UI and CLI (luvus binary; local, named-session and SSH-attached), Luvus Web (optional browser client bridge, luvus web), Programmatic surface (JSON control socket, CLI verbs, UHP 1.0 NDJSON, uhp access gateway) · Version: v0.14.3 (tag, release 2026-09-30, commit 54003ce9568acb2977e4bbdbb30a61f99faa0465); source pass 2026-11-16 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
No automatic dependency, cache, service, port or secret management.
10 atomic answers
Dependencies [unsupported] Bounded search finds no dependency installer; a worktree provider module can run setup. Sources: luvus:worktrees, luvus:modules.
Caches [unsupported] No cache sharing. Sources: luvus:worktrees.
Luvus enforces few limits: a 85% context gate blocks marking a task done until compaction, a quality gate must pass, automation prompts are bounded (32 KiB) with misfire grace and at least 60 s intervals, and agent-pane limits follow the agents. No time, turn, token or spend budgets, and no automatic retries.
Scope
Surfaces: Luvus terminal UI and CLI (luvus binary; local, named-session and SSH-attached), Luvus Web (optional browser client bridge, luvus web), Programmatic surface (JSON control socket, CLI verbs, UHP 1.0 NDJSON, uhp access gateway) · Version: v0.14.3 (tag, release 2026-09-30, commit 54003ce9568acb2977e4bbdbb30a61f99faa0465); source pass 2026-11-16 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
No spend, token, time or turn limits; the context gate depends on the worker reporting heartbeat.
8 atomic answers
Time limits [unsupported] No task timeouts except agent prompt --wait --timeout and gate cancellation on release. Sources: luvus:msg, luvus:orch.
Turn limits [unsupported] No turn limits. Sources: luvus:orch.
Token limits [partial] Context usage gate at 85% blocks done; no token budget. Sources: luvus:orch, luvus:orchsrc.
Spend limits [unsupported] Bounded search of orch/automation/mission for budget or spend limits finds none; cost is display-only. Sources: luvus:orch, luvus:agents.
Timeouts [partial] agent prompt --wait defaults to 300 s (exit 2); gates run in contained processes. Sources: luvus:msg, luvus:orch.
Retries [partial] task retry is manual; automations do not retry. Sources: luvus:orch, luvus:auto.
Provider failures [unsupported] Provider failures appear only in the agent's pane. Sources: luvus:agents.
Enforcement [partial] Context gate and quality gate are enforced; display values are not. Sources: luvus:orch.
Luvus shows live per-agent state, Mission Control tables with tokens, context use and cost, automation run history and health, task output/notes and structured runtime logs that omit pane content. Usage comes from each agent's own store and shows — when unknown; there are no exports, per-project or time series statistics.
Scope
Surfaces: Luvus terminal UI and CLI (luvus binary; local, named-session and SSH-attached), Luvus Web (optional browser client bridge, luvus web), Programmatic surface (JSON control socket, CLI verbs, UHP 1.0 NDJSON, uhp access gateway) · Version: v0.14.3 (tag, release 2026-09-30, commit 54003ce9568acb2977e4bbdbb30a61f99faa0465); source pass 2026-11-16 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
No usage export or time-series/project statistics; usage unavailable for several agents.
13 atomic answers
Logs [supported] Server/client logs under ~/.luvus/logs that exclude pane output and prompts; panes show agent logs. Sources: luvus:faq.
Mission Control shows tokens, context and cost per agent session when the agent records them or Luvus has model pricing, with totals and cost-by-model; unknown usage shows — never zero. No per-task/epic roll-up, alerts or export.
Scope
Surfaces: Luvus terminal UI and CLI (luvus binary; local, named-session and SSH-attached), Luvus Web (optional browser client bridge, luvus web), Programmatic surface (JSON control socket, CLI verbs, UHP 1.0 NDJSON, uhp access gateway) · Version: v0.14.3 (tag, release 2026-09-30, commit 54003ce9568acb2977e4bbdbb30a61f99faa0465); source pass 2026-11-16 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
Several agents report no usage; no per-task cost, alerts or export.
14 atomic answers
Task cost [unsupported] No task-level cost aggregation in ORCH. Sources: luvus:agents, luvus:orch.
Session cost [supported] Mission Control cost per agent session. Sources: luvus:agents.
Child cost [unsupported] No child-agent cost association. Sources: luvus:agents.
Epic cost [unsupported] No epics. Sources: luvus:orch.
Harness aggregation [partial] Totals across agents are known subtotals when coverage is incomplete. Sources: luvus:agents.
Billed vs estimated [partial] Cost from agent record or Luvus pricing estimate; labeled usage_status. Sources: luvus:agents, luvus:pricesrc.
Leases prevent overlapping path work, only one task merges at a time, gates run in contained process trees and are cancelled on release, and Luvus avoids per-agent polling; there are no CPU/RAM limits, queues for checks, throttling or per-host resource scheduling.
Scope
Surfaces: Luvus terminal UI and CLI (luvus binary; local, named-session and SSH-attached), Luvus Web (optional browser client bridge, luvus web), Programmatic surface (JSON control socket, CLI verbs, UHP 1.0 NDJSON, uhp access gateway) · Version: v0.14.3 (tag, release 2026-09-30, commit 54003ce9568acb2977e4bbdbb30a61f99faa0465); source pass 2026-11-16 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
No resource-aware scheduling, check reuse or backpressure.
12 atomic answers
Concurrency [partial] No global concurrency limit; per-project lease conflicts. Sources: luvus:orch.
Queues [supported] Queued tasks and single-merge queue. Sources: luvus:orch.
Cpu ram [unsupported] No CPU/RAM limits or awareness. Sources: luvus:orch, luvus:arch.
Backpressure [unsupported] No backpressure for workers. Sources: luvus:orch.
Host awareness [unsupported] No per-host resource awareness. Sources: luvus:orch, luvus:machines.
Check reuse [unsupported] No gate result reuse. Sources: luvus:orch.
Check deduplication [unsupported] No duplicate-check handling. Sources: luvus:orch.
Bounded tests [partial] Gate runs one command per task in a contained process tree. Sources: luvus:orch.
Cancellation [supported] Release/retry cancels a running gate. Sources: luvus:orch.
Fairness [unsupported] No fairness policy. Sources: luvus:orch.
Recovery [partial] Interrupted integration restores prior state after restart. Sources: luvus:orch.
Shared limits [unsupported] No shared limits. Sources: luvus:orch.
Single-user local tool. Luvus Web can pair up to eight of your own browsers or devices to the same session, read-only by default or with control, and several TUI clients attach at once, each with its own viewport; there is no multi-user identity, comments, presence or ordering rules.
Scope
Surfaces: Luvus terminal UI and CLI (luvus binary; local, named-session and SSH-attached), Luvus Web (optional browser client bridge, luvus web), Programmatic surface (JSON control socket, CLI verbs, UHP 1.0 NDJSON, uhp access gateway) · Version: v0.14.3 (tag, release 2026-09-30, commit 54003ce9568acb2977e4bbdbb30a61f99faa0465); source pass 2026-11-16 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
No user identities, comments, presence or conflict handling; shared devices all act as the same owner.
11 atomic answers
Visibility [supported] Paired browsers and attached TUIs see the same panes. Sources: luvus:web, luvus:concepts.
No organization, project or task roles, membership, SSO or provisioning exist; access is the local OS account plus paired-device authority.
Scope
Surfaces: Luvus terminal UI and CLI (luvus binary; local, named-session and SSH-attached), Luvus Web (optional browser client bridge, luvus web), Programmatic surface (JSON control socket, CLI verbs, UHP 1.0 NDJSON, uhp access gateway) · Version: v0.14.3 (tag, release 2026-09-30, commit 54003ce9568acb2977e4bbdbb30a61f99faa0465); source pass 2026-11-16 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
9 atomic answers
Organization roles [unsupported] Bounded search of src, web and docs (terms role, sso, oidc, saml, scim, member) finds no such feature. Sources: luvus:security, luvus:web, luvus:site.
Project roles [unsupported] Bounded search of src, web and docs (terms role, sso, oidc, saml, scim, member) finds no such feature. Sources: luvus:security, luvus:web, luvus:site.
Task roles [unsupported] Bounded search of src, web and docs (terms role, sso, oidc, saml, scim, member) finds no such feature. Sources: luvus:security, luvus:web, luvus:site.
Membership [unsupported] Bounded search of src, web and docs (terms role, sso, oidc, saml, scim, member) finds no such feature. Sources: luvus:security, luvus:web, luvus:site.
Sso [unsupported] Bounded search of src, web and docs (terms role, sso, oidc, saml, scim, member) finds no such feature. Sources: luvus:security, luvus:web, luvus:site.
Provisioning [unsupported] Bounded search of src, web and docs (terms role, sso, oidc, saml, scim, member) finds no such feature. Sources: luvus:security, luvus:web, luvus:site.
Unauthorized access [unsupported] Access control is the OS account boundary plus one-use pairing; no roles. Sources: luvus:security, luvus:web, luvus:site.
Revocation [unsupported] Stopping the bridge revokes browser authority; devices can be revoked; no membership lifecycle. Sources: luvus:security, luvus:web, luvus:site.
Luvus does not approve tool or command calls itself: blocked prompts of the agent are shown and can be answered by the user through the pane or agent keys; automations never type approvals and map access levels to the agent's native flags. Web control and UHP access are explicit, scoped and expiring; modules require install confirmation.
Scope
Surfaces: Luvus terminal UI and CLI (luvus binary; local, named-session and SSH-attached), Luvus Web (optional browser client bridge, luvus web), Programmatic surface (JSON control socket, CLI verbs, UHP 1.0 NDJSON, uhp access gateway) · Version: v0.14.3 (tag, release 2026-09-30, commit 54003ce9568acb2977e4bbdbb30a61f99faa0465); source pass 2026-11-16 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
No product-enforced command/network/secret policy; approvals are the agent's.
14 atomic answers
Command [partial] Agent permission prompts are detected and shown blocked; answered in the pane. Sources: luvus:agents.
Tool [partial] Same, per agent. Sources: luvus:agents.
Network [unsupported] No network approvals. Sources: luvus:security.
Secret [unsupported] No secret approvals. Sources: luvus:security.
Delivery [unsupported] No delivery approvals; DIFF has no publish action. Sources: luvus:diff.
Approver identity [unsupported] No approver identity. Sources: luvus:security.
Lifetime [partial] Web/UHP access authority expires or ends with the bridge process. Sources: luvus:web, luvus:uhpremote.
Allow [partial] User answers in pane; agent keys can answer prompts. Sources: luvus:msg.
Revoke [supported] Stopping the bridge revokes authority; disabling a skill removes it. Sources: luvus:web, luvus:security.
Tunnels [supported] Bridge authority is process-bound; Ctrl+C revokes. Sources: luvus:web.
Defaults [supported] Web read-only by default; automations default to workspace access; Luvus never changes agent permanent config. Sources: luvus:web, luvus:auto.
Safer modes [supported] Read-only/workspace/full access for scheduled work via native flags. Sources: luvus:auto, luvus:codexsrc.
Enforcement [partial] Access limits enforced by the agent's flags; Luvus refuses unsupported combinations. Sources: luvus:auto.
Luvus keeps task notes, outputs, automation run history, the event stream (luvus events, not persisted as a log) and diagnostics logs that exclude pane content; the session is single-user so actions carry no identities. No audit trail, export or integrity model.
Scope
Surfaces: Luvus terminal UI and CLI (luvus binary; local, named-session and SSH-attached), Luvus Web (optional browser client bridge, luvus web), Programmatic surface (JSON control socket, CLI verbs, UHP 1.0 NDJSON, uhp access gateway) · Version: v0.14.3 (tag, release 2026-09-30, commit 54003ce9568acb2977e4bbdbb30a61f99faa0465); source pass 2026-11-16 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
No audit with retention/integrity; events are streams, not stored.
11 atomic answers
Actions [partial] Events bus for task and automation actions; not persisted. Sources: luvus:orch.
Approvals [unsupported] Approvals are not recorded by Luvus. Sources: luvus:agents.
Edits [partial] Task notes and attempts. Sources: luvus:orch.
Discussion [unsupported] No discussion. Sources: luvus:orch.
Decisions [unsupported] No decision records. Sources: luvus:orch.
Cross user persistence [unsupported] Single user. Sources: luvus:security.
A native read-only DIFF surface lists staged, worktree, untracked and conflicted files, shows split/stack diffs with search, hunk and file navigation, viewed marks and local notes that can be sent to a live agent; the Git tab shows PR details and approve; keyboard-first and mobile-friendly. No request-changes flow or reviewer roles.
Scope
Surfaces: Luvus terminal UI and CLI (luvus binary; local, named-session and SSH-attached), Luvus Web (optional browser client bridge, luvus web), Programmatic surface (JSON control socket, CLI verbs, UHP 1.0 NDJSON, uhp access gateway) · Version: v0.14.3 (tag, release 2026-09-30, commit 54003ce9568acb2977e4bbdbb30a61f99faa0465); source pass 2026-11-16 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
No guided review queue, request changes or shipping guidance; notes are local.
Anyone with access to the same server (SSH account, paired browser) can attach to the same live panes with identical session history and runtime, including after the original client disconnects; ownership is the OS user so there is no distinct person transfer or attribution. Agent conversation can be forked or resumed in another pane of the same agent.
Scope
Surfaces: Luvus terminal UI and CLI (luvus binary; local, named-session and SSH-attached), Luvus Web (optional browser client bridge, luvus web), Programmatic surface (JSON control socket, CLI verbs, UHP 1.0 NDJSON, uhp access gateway) · Version: v0.14.3 (tag, release 2026-09-30, commit 54003ce9568acb2977e4bbdbb30a61f99faa0465); source pass 2026-11-16 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
Single-user model: no separate identities, permissions or attribution; harness transfer not supported.
12 atomic answers
Ongoing takeover [supported] A new client attaches to the running server. Sources: luvus:concepts.
Luvus retains task output and notes, worktrees and branches, DIFF views of current Git layers and scrollback; there is no artifact gallery, screenshot/recording capture or test-report store. Mermaid/Markdown previews are native; web uploads reach the server as files.
Scope
Surfaces: Luvus terminal UI and CLI (luvus binary; local, named-session and SSH-attached), Luvus Web (optional browser client bridge, luvus web), Programmatic surface (JSON control socket, CLI verbs, UHP 1.0 NDJSON, uhp access gateway) · Version: v0.14.3 (tag, release 2026-09-30, commit 54003ce9568acb2977e4bbdbb30a61f99faa0465); source pass 2026-11-16 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
No artifact gallery, recordings or screenshot retention; outputs are scrollback and task fields.
13 atomic answers
Diffs [supported] DIFF and git tab diffs for live Git state. Sources: luvus:diff, luvus:git.
Documents [partial] Markdown and Mermaid preview of files. Sources: luvus:files.
Screenshots [unsupported] No screenshot capture. Sources: luvus:files.
Recordings [unsupported] No recordings. Sources: luvus:files.
ORCH tasks can carry a quality-gate command that must pass before a task is done and can merge; failed gates hold the task in review; the context gate blocks done above 85%. Tests, lint and types run only as the user's chosen gate; no CI integration beyond showing PR checks, no spec checks.
Scope
Surfaces: Luvus terminal UI and CLI (luvus binary; local, named-session and SSH-attached), Luvus Web (optional browser client bridge, luvus web), Programmatic surface (JSON control socket, CLI verbs, UHP 1.0 NDJSON, uhp access gateway) · Version: v0.14.3 (tag, release 2026-09-30, commit 54003ce9568acb2977e4bbdbb30a61f99faa0465); source pass 2026-11-16 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
One gate command per task; no spec conformance or independent-review enforcement.
11 atomic answers
Tests [supported] Gate can be cargo test etc. Sources: luvus:orch.
Lint [partial] Any command can be the gate. Sources: luvus:orch.
Types [partial] Any command can be the gate. Sources: luvus:orch.
Ci [partial] Git tab shows PR checks and notifies when they fail. Sources: luvus:git.
Luvus creates worktrees and branches, merges finished worker branches into luvus/integration in an isolated worktree with clean conflict abort, shows commits/branches/PRs through git and gh and starts gh pr create in a pane. Commits, rebases and review comments are done by agents or users, not by product state.
Scope
Surfaces: Luvus terminal UI and CLI (luvus binary; local, named-session and SSH-attached), Luvus Web (optional browser client bridge, luvus web), Programmatic surface (JSON control socket, CLI verbs, UHP 1.0 NDJSON, uhp access gateway) · Version: v0.14.3 (tag, release 2026-09-30, commit 54003ce9568acb2977e4bbdbb30a61f99faa0465); source pass 2026-11-16 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
No product-managed commits, rebase, PR review comments or CI-response automation.
Approval is by the user: the gate pass plus pressing m merges a task branch into luvus/integration (a Luvus-owned branch, never the user's branch); PR approve through gh from PR detail; no release or deployment features and no exact-revision binding of approvals.
Scope
Surfaces: Luvus terminal UI and CLI (luvus binary; local, named-session and SSH-attached), Luvus Web (optional browser client bridge, luvus web), Programmatic surface (JSON control socket, CLI verbs, UHP 1.0 NDJSON, uhp access gateway) · Version: v0.14.3 (tag, release 2026-09-30, commit 54003ce9568acb2977e4bbdbb30a61f99faa0465); source pass 2026-11-16 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
Integration branch only; no merge to main, release or deploy.
6 atomic answers
Approve [partial] PR detail a approves via gh. Sources: luvus:git.
Merge [partial] Merges into luvus/integration only. Sources: luvus:orch.
Task records branch, worktree and exact integration commit after merge, previous attempts and gate output; retry creates a new attempt without deleting history; no PR/build/deployment links, rollback or revert feature, or stale-approval invalidation.
Scope
Surfaces: Luvus terminal UI and CLI (luvus binary; local, named-session and SSH-attached), Luvus Web (optional browser client bridge, luvus web), Programmatic surface (JSON control socket, CLI verbs, UHP 1.0 NDJSON, uhp access gateway) · Version: v0.14.3 (tag, release 2026-09-30, commit 54003ce9568acb2977e4bbdbb30a61f99faa0465); source pass 2026-11-16 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
No PR, build or deployment links; no revert tooling.
No batch review queue exists; the ORCH board lists done/review/blocked tasks and merges one at a time, with DIFF review per repository and local notes.
Scope
Surfaces: Luvus terminal UI and CLI (luvus binary; local, named-session and SSH-attached), Luvus Web (optional browser client bridge, luvus web), Programmatic surface (JSON control socket, CLI verbs, UHP 1.0 NDJSON, uhp access gateway) · Version: v0.14.3 (tag, release 2026-09-30, commit 54003ce9568acb2977e4bbdbb30a61f99faa0465); source pass 2026-11-16 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
12 atomic answers
Review queue [partial] Board lists tasks by status; merge one at a time. Sources: luvus:orch.
Entire Luvus (server, TUI, web client, docs) is in one public repository under Apache-2.0 (LICENSE, Cargo.toml); vendored alacritty_terminal and vte keep their own licenses. There is no hosted extension or closed component.
Scope
Surfaces: Luvus terminal UI and CLI (luvus binary; local, named-session and SSH-attached), Luvus Web (optional browser client bridge, luvus web), Programmatic surface (JSON control socket, CLI verbs, UHP 1.0 NDJSON, uhp access gateway) · Version: v0.14.3 (tag, release 2026-09-30, commit 54003ce9568acb2977e4bbdbb30a61f99faa0465); source pass 2026-11-16 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Fully self-hosted local software: no vendor service is required; state lives in ~/.luvus (config, session, orch ledger, modules); an update check contacts luvus.dev unless disabled. No import/export tooling beyond plain JSON files and the user's own Git; agent conversations stay in each agent's store.
Scope
Surfaces: Luvus terminal UI and CLI (luvus binary; local, named-session and SSH-attached), Luvus Web (optional browser client bridge, luvus web), Programmatic surface (JSON control socket, CLI verbs, UHP 1.0 NDJSON, uhp access gateway) · Version: v0.14.3 (tag, release 2026-09-30, commit 54003ce9568acb2977e4bbdbb30a61f99faa0465); source pass 2026-11-16 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
No export/import feature; history portability is limited to local files.
Prompts, code and terminal content stay on the user's machine; the project receives none (privacy policy) and states Luvus has no telemetry; only update checks to luvus.dev and requested HTTPS/GitHub theme/module fetches use the network. Logs omit pane output; saved pane screens can be disabled. Data sent to model providers is each agent's.
Scope
Surfaces: Luvus terminal UI and CLI (luvus binary; local, named-session and SSH-attached), Luvus Web (optional browser client bridge, luvus web), Programmatic surface (JSON control socket, CLI verbs, UHP 1.0 NDJSON, uhp access gateway) · Version: v0.14.3 (tag, release 2026-09-30, commit 54003ce9568acb2977e4bbdbb30a61f99faa0465); source pass 2026-11-16 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
retention: Local until deleted; scrollback budget 10 MiB per pane.
subprocessors: Only Cloudflare for the website; none for the app.
15 atomic answers
Code data [supported] Stays local; not received by the project. Sources: luvus:privacy.
Prompts [supported] Not received; agents send to their providers. Sources: luvus:privacy.
Luvus is free: no price, plan, seat or usage fee appears in the repository, site, privacy or terms pages; separate model subscriptions/API costs and any remote hosts are paid by the user.
Scope
Surfaces: Luvus terminal UI and CLI (luvus binary; local, named-session and SSH-attached), Luvus Web (optional browser client bridge, luvus web), Programmatic surface (JSON control socket, CLI verbs, UHP 1.0 NDJSON, uhp access gateway) · Version: v0.14.3 (tag, release 2026-09-30, commit 54003ce9568acb2977e4bbdbb30a61f99faa0465); source pass 2026-11-16 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
Absence of pricing is established from the checked first-party pages only; third-party agent costs vary.
12 atomic answers
Currency [not-applicable] No price. Sources: luvus:site.
Interval [not-applicable] No billing. Sources: luvus:site.
Seats [not-applicable] No seats. Sources: luvus:site.
Platform cost is zero for one, two or five developers because the software is free and local; model and compute costs depend entirely on the chosen agents and hosts and are not modeled by Luvus.
Scope
Surfaces: Luvus terminal UI and CLI (luvus binary; local, named-session and SSH-attached), Luvus Web (optional browser client bridge, luvus web), Programmatic surface (JSON control socket, CLI verbs, UHP 1.0 NDJSON, uhp access gateway) · Version: v0.14.3 (tag, release 2026-09-30, commit 54003ce9568acb2977e4bbdbb30a61f99faa0465); source pass 2026-11-16 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
No scenario workload pricing: model/compute costs are unknown without an agent plan.
Open-source project, GA releases through GitHub (v0.14.3 on 2026-09-30, frequent minor releases), a changelog in the repo, GitHub issues and private security advisories for support; no stated response commitments or status page.
Scope
Surfaces: Luvus terminal UI and CLI (luvus binary; local, named-session and SSH-attached), Luvus Web (optional browser client bridge, luvus web), Programmatic surface (JSON control socket, CLI verbs, UHP 1.0 NDJSON, uhp access gateway) · Version: v0.14.3 (tag, release 2026-09-30, commit 54003ce9568acb2977e4bbdbb30a61f99faa0465); source pass 2026-11-16 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
No response-time commitments, status page or deprecation policy.
8 atomic answers
Release stage [supported] Version 0.14.x with GA release assets; Automations marked BETA. Sources: luvus:release, luvus:auto.
Access restrictions [supported] None; public download. Sources: luvus:release.
Support [partial] GitHub issues and private security reporting. Sources: luvus:readme.
Trial [not-applicable] No trial is needed. Sources: luvus:site.
Credits trial [not-applicable] No credits. Sources: luvus:site.
Self host cost [supported] Runs on the user's machine; no license fee. Sources: luvus:license.
Paid only [unsupported] Not paid-only. Sources: luvus:site.
Early access [unsupported] No gated early access; releases are public. Sources: luvus:release.
Free scenarios [partial] BYO subscriptions, remote host, issue (read-only) and review scenarios work for free; no mobile app, collaboration or managed compute. Sources: luvus:readme, luvus:web.
Card required [supported] No card. Sources: luvus:site.
Usage caps [supported] No caps beyond local limits. Sources: luvus:auto.
Paid evaluation [unsupported] No payment needed. Sources: luvus:site.
Transparent: free open-source software with no pricing units, limits, markup, minimum commitment or cancellation; model/compute costs are billed by other parties.
Scope
Surfaces: Luvus terminal UI and CLI (luvus binary; local, named-session and SSH-attached), Luvus Web (optional browser client bridge, luvus web), Programmatic surface (JSON control socket, CLI verbs, UHP 1.0 NDJSON, uhp access gateway) · Version: v0.14.3 (tag, release 2026-09-30, commit 54003ce9568acb2977e4bbdbb30a61f99faa0465); source pass 2026-11-16 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
9 atomic answers
Units [not-applicable] No priced units. Sources: luvus:site.
Included limits [not-applicable] None. Sources: luvus:site.
Mission control for AI coding agents: persistent workspaces, agent awareness, worktrees and orchestration, Luvus Web, remote machines over SSH, modules, UHP 1.0. Install via curl/Homebrew/PowerShell. Platforms macOS, Linux, FreeBSD, Windows. Apache-2.0. Supported-agent table with live status, resume and hook columns.
Detached server owns panes, PTYs and agents; clients are disposable; named sessions are independent servers; workspace > tab > pane; agents are watched not wrapped; every UI action is a CLI command over a local socket.
agent list/name/prompt/read/keys/start commands let one agent hand a task to another pane, wait or hand off, and read results; pane env injects LUVUS_PANE_ID and socket; optional skill.
Live blocked/working/done/idle state by process and screen detection; Mission Control usage tokens and cost from agent-native stores; session resume and fork per agent; hooks add precision.
Kind
documented
Locator
AGENTS sidebar, Usage in Mission Control, session resume, fork
luvus web starts a loopback bridge (127.0.0.1:4174) with one-use pairing links; read-only by default, --control opt-in; up to 8 devices; phone access needs a trusted TLS tunnel; stopping the bridge leaves the server running.
Kind
documented
Locator
Start locally, pairing, control, tunnels, security model
Git tab: commits, flow, branches, PRs, issues, status; PRs/issues/checks via gh CLI; in PR list c starts gh pr create; PR detail can approve or check out.
Native read-only DIFF review of staged/worktree/untracked/conflict layers with split/stack views, local notes and handoff of notes to a live agent; no stage/commit/push action.
Windows notes (Windows Terminal; no per-pane cwd tracking); runtime logs never include pane output or prompts; ~/.luvus holds session, config, orch ledger, modules.
Modules are ordinary programs in any language declared by a manifest; GitHub topic luvus-module discovery; install shows declared commands for confirmation; no SDK or runtime.
Assets for aarch64/x86_64 macOS (tar.gz), x86_64/aarch64 Linux musl (tar.gz, rpm, deb), x86_64 FreeBSD, x86_64 Windows MSVC (zip) with sha256 files; no Windows ARM64, no Android/iOS artifact.
Durable one-time/interval/daily/weekly automations (BETA) owned by the detached server; new-worker or active-agent targets; misfire and overlap policies; no automatic retry; read-only/workspace/full access mapped to native agent flags; bounds 256 definitions.
Luvus is local software; the project operates no hosted agent service and does not receive prompts, terminal output or files; no first-party analytics on luvus.dev; Cloudflare Pages hosts the site.
Static documentation site (Astro on Cloudflare Pages) describing the free open-source local tool; no pricing, account or hosted service offered in the checked pages.
Saved SSH machine profiles place remote workspaces beside Local in one TUI; setup can install a compatible Luvus binary on the remote host with approval; luvus machine add/list/status.
Single-user local-trust tool; state dir 0700, sockets 0600; modules confirm declared commands; --remote rides plain ssh with no listener; "Luvus has no telemetry"; network limited to update checks and explicit installs.
Kind
documented
Locator
local control endpoint, what runs commands, Remote
Docs show an example module (examples/modules/agent-ping) that posts a webhook when an agent goes blocked or finishes; the webhook URL is a secret module setting. It is module code, not a built-in Luvus feature.
Single-writer ORCH state with statuses, path leases rejecting overlapping globs with lease_conflict, 85% context-compaction gate and sequential ids t1, t2.
Server/client split; named sessions each own a server, PTY tree and orchestration ledger; single-writer event loop makes task claims and leases race-free; pure Rust single binary.
Fuzzy finder over sessions, workspaces, tabs, panes, agents, file names/paths and retained terminal output; does not search file contents or agent transcripts.
Codex automation access maps read-only to --sandbox read-only and full to --dangerously-bypass-approvals-and-sandbox: native per-run flags, not a Luvus sandbox.