XENEON EDGE Agent Command Center

A native Omarchy command center for the Corsair XENEON EDGE. It keeps Herdr as the session and interaction authority while providing a dedicated 2560x720 touch surface for agent status, safe triage, provider capacity, and connected tool status.

Watch the XENEON EDGE Agent Command Center in action on X.

Note

This is an early, hardware-specific project developed and validated on Omarchy with a Corsair XENEON EDGE. There is not yet a general-purpose packaged release; use the source installer and commissioning flow below.

Highlights

• A glanceable command center and animated Ambient view for Herdr agents.
• Exact, fail-closed display and touchscreen identity checks.
• Typed, narrowly scoped agent actions mediated by the Rust daemon.
• Normalized Claude, Codex, OpenCode, host-health, and connected-tool status.
• Reversible user-owned installation in XDG locations; no packaged Omarchy files are modified.

Production output matching is fail-closed: the portal creates no surface unless the commissioned EDID, model, serial, and touchscreen all match exactly and uniquely. The connector name is resolved at runtime so a normal port rename after reboot or replug does not weaken the hardware identity.

Components

• xeneon-agentd: Rust user daemon for Herdr state, host health, normalized AI usage and Codex Micro status, safe actions, optional Voxtype dictation, reconnects, and output/focus integration.
• xeneon-agentctl qml-bridge: NDJSON bridge used by Quickshell.
• quickshell/: standalone touch portal plus deterministic and live previews.
• config/ and scripts/: reversible user-service, exact-identity hotplug, and Omarchy integration.

Herdr remains authoritative. The portal can never send arbitrary text, keys, or shell commands. Open and zoom are narrow public Herdr API calls. Interrupt requires a short-lived capability issued and revalidated by a compatible Herdr server; approval is deliberately unavailable until a current prompt can be grounded safely.

For the full boundary model, see the architecture and protocol documentation.

Develop and preview

Requirements on Omarchy are Rust, Quickshell, Qt 6 QML tooling, Lua's luac, Python 3, Herdr, and just through mise.

mise install
mise exec -- just check
mise run preview

The preview is a normal 1280x360 window on the current display and uses a deterministic fixture. Explicit preview windows are the only path that may use the primary display. Other fixture states can be selected explicitly:

scripts/preview health.ndjson
scripts/preview disconnected.ndjson

A live source preview builds private development binaries, starts a temporary daemon/socket, and displays the same normalized Herdr and Voxtype state used by production without installing files, enabling services, or changing the fail-closed output identity:

scripts/preview --live
scripts/preview --live --ambient-after 6

The control center shows safe Herdr identity, state duration, repository and worktree context, plus normalized Claude, Codex, and OpenCode capacity. The daemon consumes Omarchy's schema-v1 Claude/Codex agent records, keeps legacy cache compatibility, and derives OpenCode's local soft-budget windows from its newly processed token counters (input, output, reasoning, and cache-write; reused cache-read context is excluded) in the read-only SQLite message ledger. The AI footer shows both reported usage windows, resets, plan/freshness state, and bounded today/hour token activity when available. Header controls use typed daemon actions to focus or launch the fixed ChatGPT Desktop and Claude Desktop entries. The Micro control opens a read-only virtual projection of the connected device and current agent slots. The Order control reads and writes Herdr's own grouped/priority setting, so the Herdr Agents panel and EDGE cards stay synchronized instead of keeping separate preferences. The upper-right Motion and Screen controls are shared by the command-center and Ambient views. Motion snaps the ambient constellation to fixed positions and removes perimeter/trail animation; Screen applies a reversible near-black portal veil. These presentation settings persist across portal restarts.

Portal chrome follows Omarchy's active runtime theme. The named Quickshell configuration reads the allowlisted colors in $XDG_STATE_HOME/omarchy/current/theme/colors.toml and watches the stable theme.name file, so omarchy theme set updates backgrounds, surfaces, text, borders, and semantic accents without restarting the portal. Missing or invalid colors fall back safely. State meaning stays stable while its hue comes from the active theme: working uses blue, blocked uses yellow, review-ready uses green, and errors use red. Light Omarchy themes are translated into contrast-checked dark EDGE chrome while retaining their palette hues. The top-right Palette control shows the live Omarchy swatches and lets you map those allowlisted theme roles onto XENEON's Ready, Success, Working, Needs Help, Review Ready, Error, Unknown, Recording, and Processing meanings. Mappings apply immediately to the command center and Ambient view, persist beside the Motion and Screen preferences, and can be reset to the reviewed defaults. Arbitrary colors are not accepted; chrome and text contrast remain automatic.

The live preview exposes the real narrow agent-focus, desktop-app, and voice actions. Voice dictation is push-to-talk: press starts a portal-owned Voxtype recording, release transcribes without automatic submission, and Cancel discards it. The floating preview restores the last exact non-portal window before voice start and stop so that window remains the laptop transcription target. The preview also applies exact per-window opaque compositor properties so desktop content cannot bleed through its dark surface.

--ambient-after accepts 1 through 300 seconds and only changes the explicit preview window. It is useful for reviewing the staged dashboard-to-orbit animation without changing the production 60-second inactivity policy. The reference timing and motion breakdown live in docs/concept-motion.md.

Install without activating

Install the two local binaries, then seed simulator-safe user configuration:

cargo install --path crates/xeneon-agentd --root "$HOME/.local" --force
cargo install --path crates/xeneon-agentctl --root "$HOME/.local" --force
scripts/install.sh

The default installer copies the named Quickshell configuration and rendered user units, plus an XDG desktop launcher named XENEON EDGE Command Center. The launcher starts the two fixed user services without restarting an already running portal; its secondary desktop action performs an explicit restart. The default installer does not enable either service, edit Hyprland, or match any production output. Existing user-owned or modified files are refused or preserved.

The daemon reads Voxtype's runtime state when Omarchy Dictation is available. Portal voice start/stop/cancel requests remain typed daemon actions; QML never executes the voxtype CLI. Service startup and shutdown clean up only a portal-owned recording. The same cleanup can be invoked directly for a private preview daemon:

xeneon-agentd --config ~/.config/xeneon-edge-agents/config.toml --cleanup-dictation

scripts/check.sh
scripts/uninstall.sh

check.sh reports the physical gate as blocked in simulation mode. Uninstall removes only installer-recorded files whose content is unchanged.

Commission the physical EDGE

First capture the connected hardware identity without changing anything:

scripts/detect-hardware.sh

Production installation requires the complete output and touch identity together:

scripts/install.sh \
  --apply-production \
  --connector '<DRM-CONNECTOR>' \
  --edid-sha256 '<64-CHARACTER-EDID-SHA256>' \
  --screen-serial '<EXACT-EDID-SERIAL>' \
  --screen-model '<EXACT-SCREEN-MODEL>' \
  --touch-device '<EXACT-HYPRLAND-DEVICE-NAME>' \
  --touch-bustype '0003' \
  --touch-vendor '<EXACT-USB-VENDOR-ID>' \
  --touch-product '<EXACT-USB-PRODUCT-ID>' \
  --touch-phys '<EXACT-KERNEL-PHYS>'

Use --touch-uniq when the device exposes a stable non-empty uniq; phys is the fallback only when uniq is empty because the USB topology path can change across boots. Providing both records both values but runtime identity prefers the stable uniq. A live production install performs the full output and touchscreen check before changing any user file. Without --activate, it stages the generated module but deliberately leaves hyprland.lua and all service states untouched. Add --activate only after that exact identity passes while the device is connected. Activation inserts the one user-owned require, validates and reloads Hyprland, and enables the lightweight hotplug reconciler. Native Hyprland monitor events then resolve the current connector, verify the complete identity, map only the commissioned touchscreen, and start or stop the daemon and portal together. A user-level /dev/input path watcher covers USB-only touch disconnects/reconnects; the exact touch device stays disabled during every transition until the full identity gate passes. The generated module leaves Omarchy's monitors.lua ownership untouched.

The remaining physical checklist covers touch coordinates, focus restoration, hotplug, DPMS, suspend/resume, lock-screen privacy, and read-only DDC discovery. Brightness control stays disabled until exact read/restore is proven.

See the commissioning guide for the complete safety and verification checklist. TODO.md is the resumable implementation ledger.

Security and privacy

The portal intentionally excludes terminal contents, prompts, credentials, and raw provider payloads. Production display matching fails closed when hardware identity is absent or ambiguous, and QML cannot execute arbitrary shell input.

Please report security issues through the process in SECURITY.md instead of opening a public issue.

Contributing

Contributions are welcome. Start with CONTRIBUTING.md, keep the authority and hardware-safety boundaries intact, and run the repository checks before opening a pull request.

License

This project is available under the MIT License.