helixgen-tui 0.3.0

Terminal UI for helixgen: tone library, setlists, and Line 6 Helix Stadium device control.

helixgen-tui

A terminal UI for helixgen: manage your tone library, setlists, and a Line 6 Helix Stadium over the LAN — from the terminal, no editor app.

⚠️ Unofficial tool — use at your own risk. Not affiliated with or endorsed by Line 6 / Yamaha. Line 6, Helix, and HX are trademarks of Yamaha Guitar Group, Inc. The MIT LICENSE disclaims all warranty.

Repo family

Repo	What it is
helixgen-core	The helixgen Python package: libs, CLI, MCP server
helixgen	The Claude Code plugin — /tone, /setup, /device skills + marketplace
helixgen-tui (this repo)	Terminal UI for tones, setlists, and device control

Install

uv tool install helixgen-tui
# or
pipx install helixgen-tui

Then run it as helixgen-tui or the shorter hxg.

Usage

The app is the librarian: browse and manage tones, setlists, and device sync, plus setting the active tone on the hardware — all inside a tabbed shell:

Tab	Key	What it does
Library	1	Browse tones, view details, filter, make a tone active, sync it to the device
Setlists	2	Manage setlist membership and order, sync a setlist or all setlists
IRs	3	Push local IRs to the device, rename/delete/prune device IRs
Device	4	Device info, active tone, backup/restore, lock status, retry connect

Press ? anywhere for the full key-binding reference, q to quit.

Tone editor: press enter on a Library tone to open its signal chain. The chain renders left-to-right — an input node, the blocks (both DSP paths stacked when parallel-routed), then the output node. Arrow keys walk the chain; tab switches to the params inspector, where left/right nudge a value and enter types one. Structural keys: a add a block, x remove, b bypass/enable, w swap the model. Selecting the output node edits its level/pan; the input node's source is read-only. Add/remove refuse on a parallel-routed path. Edits write to the local library file on s — never to the device.

Offline-first: the app works fully with no device on the LAN — Library, Setlists, and IRs stay browsable from local state. Device-mutating actions (activate, sync, push, backup, restore, ...) simply refuse with a reason in the status bar when no Helix is reachable, and reconnect automatically (or via r on the Device tab) once one is.

Design principle: slots are invisible. The UI speaks in tones and setlists only — slot addresses like 5A are an implementation detail the user never sees or types.

Note: device restore and device-side tone delete are not yet wired — they await core-side verbs (a restore that carries its target preset, and a single-pool-preset delete). The UI surfaces a clear reason until then. See docs/BACKLOG.md #6.

The long-term goal is full parity with the Helix Stadium desktop app (tracked in helixgen-core's docs/stadium-app-parity.md); this v1 ships the librarian and the tone editor (param editing plus signal-flow editing — block add/remove/swap, bypass, output level/pan), with more screens (global settings, tuner/meters) to follow. See docs/BACKLOG.md.

Development

Managed with uv; the package layout is src/helixgen_tui/, depending on helixgen[device] from PyPI (never vendor core source here).

uv run pytest          # test suite
uv run ruff check .    # lint
uv run helixgen-tui    # run the app
uv build               # sdist + wheel

CI (GitHub Actions) runs ruff + pytest on every PR and push to main; publish.yml releases to PyPI via OIDC trusted publishing on v* tags.