← Plugin catalog
Productivity

Luvus

Riz v0.4.2

Mission control for AI Agent

Create a free account to save this plugin.

From the developer

Declared capabilities

  • Interactive
  • Write

Not specified in the available declarations: limitations, pricing & account requirements.

Onboarding example

Delegate a review to the Luvus agent named reviewer.
Sources & dates

Developer declarations; not independently tested. Listing last checked Nov 16, 2026. Package observed Nov 15, 2026.

View package source →

Description

From the marketplace listing

Control a local Luvus session from Codex. Delegate work, fork agent sessions, arrange workspaces, review DIFF notes, coordinate tasks, and build capability-driven UHP automation. Requires an installed Luvus client and a running Luvus session.

Language: English · Automatically detected from descriptions.

Matches for “agent code”

Exact text from the indicated source. A mention alone does not establish support for your task.

Publisher keywords · listing

luvus terminal agents orchestration codex

Publisher description

Control Luvus agents, workspaces, and UHP automation from Codex.

Publisher full description

Control a local Luvus session from Codex. Delegate work, fork agent sessions, arrange workspaces, review DIFF notes, coordinate tasks, and build capability-driven UHP automation. Requires an installed Luvus client and a running Luvus session.

Publisher subtitle

Mission control for AI Agent

What changed

Keywords

Files & skills

File archives

Plugin package10 files · 11.4 KBBrowse files →
Skill instructions
luvus17.9 KB

View saved version →

---
name: luvus
description: "Control Luvus through its local CLI and UHP. Use only for a line beginning with `=target message`, an explicit request naming Luvus, a request to delegate to a named live Luvus agent or pane, or an explicit Luvus operation involving sessions, workspaces, tabs, panes, agents, files, Git, DIFF, worktrees, tasks, leases, modules, themes, Luvus Bar, configuration, UI, integrations, or Luvus UHP. Do not use for ordinary coding, file edits, Git operations, tests, task planning, generic agent work, or parallelization unless the user explicitly connects the request to Luvus. Being inside Luvus does not trigger this skill by itself. Inside Luvus use the inherited session; outside use the installed production Luvus command and configured session."
---

# Luvus

Use Luvus's semantic CLI and UHP to delegate work, control the live workspace,
and build explicit harness integrations. The skill adds no service, event loop,
or polling process.

## Route `=target` delegation first

Treat `=target message` as Luvus delegation only when `=` is the first
non-whitespace character on a line, `target` contains no spaces, and a message
follows it. Do not treat equations, assignments, or `=` in prose as delegation.
Codex skill invocations keep their `$skill-name` syntax.

Examples:

- `=reviewer inspect this diff` sends `inspect this diff` to the agent named
  `reviewer`.
- `=7 run the migration` addresses pane 7.
- `=codex add tests` addresses the unique agent named or kinded `codex`.

For every delegation line:

1. Run `luvus agent send <target> "<message>"` directly without `--wait`.
   `agent send` resolves live names, numeric pane ids, and unique agent kinds
   authoritatively. Do not run `agent list` first.
2. On success, accept the returned pane, agent, name, and status, tell the user
   where the work was sent, and end the turn. Do not reread or poll.
3. Only after `not_found` or `ambiguous_target`, run `luvus agent list` once to
   show the live choices. Never guess or retry a different target without the
   user's choice.
4. For any other error, report it without listing agents. Never absorb or
   perform the delegated task locally after delivery fails. Start an agent only
   when the user clearly requested it.

Plain-language delegation requests follow the same workflow. Never delegate
merely because another agent could help.

## Select exactly one session

Never run bare `luvus` because it launches or attaches the TUI. Examples below
say `luvus` for readability. Substitute the client selected here.

### Inside a Luvus pane

When `LUVUS_ENV=1`, control the inherited session:

- Require `LUVUS_BIN_PATH`, `LUVUS_SOCKET_PATH`, and `LUVUS_PANE_ID`.
- Invoke the exact `LUVUS_BIN_PATH`. Let it use the inherited socket.
- Keep `LUVUS_PANE_ID` as the caller and default split anchor.
- Never replace the inherited socket or binary with a default, a PATH lookup,
  or another Luvus session.

Act on the inherited session only because the user is already inside that
session and explicitly asked for delegation or control.

### Outside Luvus

Use the installed production Luvus client:

- Resolve `luvus` once with the current shell's command lookup, such as
  `command -v luvus` on Unix or `(Get-Command luvus).Source` in PowerShell.
- Invoke that exact resolved path for the rest of the request. This supports
  Luvus installed by Cargo, Homebrew, `install.sh`, or another PATH-managed
  installation.
- Preserve an explicitly configured `LUVUS_HOME` or `LUVUS_SOCKET_PATH`.
  Preserve `LUVUS_SESSION` too. When the user explicitly names a server
  session, pass `--session <name>` directly to every related Luvus command.
  Do not list sessions first, and do not silently fall back to `default`.
  Otherwise let the installed release binary use its production default at
  `$HOME/.luvus/luvus.sock`.
- Never substitute `LUVUS_BIN_PATH` or a repository build for a missing
  installed command.
- Only after an attempted Luvus action cannot run

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 3 — file references are metadata, not package contents.

Package details

Publisher declarations from the archived package. These are separate from our research and the live service's terms.

Package license
Apache-2.0
Package author
Riz
Keywords
See keywords

Declared capabilities

  • Interactive
  • Write

Package observed Nov 15, 2026.

Technical details
First seen
Sep 30, 2026 · 22:02 UTC
Last seen
Nov 16, 2026 · 06:00 UTC
Collection status
Collected

plugins_6a8552ad93c081918cc3e61bfaaa5f6e

Download plugin data (JSON)

Plugin details: freshly prepared. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.