Skip to content

feat(runtime): a single, user-extensible runtime catalog - #83

Merged
lvndry merged 1 commit into
feat/acp-runtime-configfrom
feat/pluggable-runtimes
Sep 19, 2026
Merged

lvndry merged 1 commit into
feat/acp-runtime-configfrom
feat/pluggable-runtimes

Conversation

@lvndry

@lvndry lvndry commented Sep 19, 2026

Copy link
Copy Markdown
Owner

What & why

Makes Quartet's runtime list easy to extend — both for us and for people running their own agents. Adding a built-in shortcut used to mean editing four places that had to stay in sync (a config type union, the preset catalog, the wizard's list, and a hand-written error string); those now collapse into one catalog, so a built-in is a single entry.

More importantly, a machine can register its own agents in ~/.quartet/runtimes.json — no rebuild. Each entry (name → command/args/label/installHint) shows up in the quartet connect wizard, answers to --runtime <name>, and gets its own "not on PATH" install hint. Built-in and reserved names (jazz, acp, …) can't be shadowed. This is the "plug in your own harness later" ask, as long as the harness speaks ACP; anything that doesn't still needs its own TurnRunner, which is the intended seam.

Any ACP agent already worked via --runtime acp --runtime-command …; this just gives your own agents the same first-class treatment the built-ins get.

How to verify

  • With no ~/.quartet/runtimes.json, quartet connect lists exactly the built-ins (Jazz, Claude, Codex, Hermes, Pi, Other) — unchanged.
  • Add { "amp": { "command": "amp-acp", "args": ["--stdio"], "label": "Amp" } } to ~/.quartet/runtimes.json; run quartet connect and confirm Amp appears in the wizard and --runtime amp selects it.
  • A malformed entry or one reusing a built-in/reserved name is skipped with a ! note, and the built-ins still load.
  • --runtime bogus errors with a message listing the available names (built-ins plus your catalog).

Stacked on #82. Base that first.

🤖 Generated with Claude Code

The four places that had to agree on the preset list — the config type union, the ACP_PRESETS
record, the wizard's CHOICES, and the hand-written error string — collapse into one catalog in
runtime-catalog.ts, so adding a built-in is a single entry. A machine can register its own
agents in ~/.quartet/runtimes.json (name → command/args/label/installHint); they appear in the
wizard, answer to --runtime <name>, and carry an install hint, with built-in and reserved names
protected. An agent that does not speak ACP still needs its own TurnRunner; this is only about
the ACP shortcuts.
@vercel

vercel Bot commented Sep 19, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
quartet Ready Ready Preview Sep 19, 2026 10:39am UTC

@lvndry
lvndry merged commit 7af19f2 into feat/acp-runtime-config Sep 19, 2026
5 checks passed
@lvndry
lvndry deleted the feat/pluggable-runtimes branch September 19, 2026 10:44
lvndry added a commit that referenced this pull request Sep 19, 2026
…tet (#82)

* feat(runtime): discover and set ACP session config options

An ACP agent advertises its session config options — model, reasoning level, mode — on
session/new, and takes session/set_config_option to change them. The ACP runtime now captures
those options, reapplies the operator's saved choices to every session (a fresh session starts
at the agent's defaults), tracks config_option_update the agent pushes on its own, and exposes
a setter. Choices persist per identity in config.json and are relayed into the bridge snapshot,
so a model or effort picked once survives restarts.

* feat(app): configure an ACP agent's model and reasoning from the dashboard

The runtime view was a read-only note telling you to configure the agent elsewhere. It now
renders a selector per option the agent discloses, bound to the live snapshot, and writing a
choice back through /api/runtime/config. Options appear once a room exists to read them from;
anything the agent does not expose stays configured in the agent, as the footer still says.

* feat(runtime): discover ACP config options on demand, without a room

The options only exist once a session does, so the runtime screen opened to an empty page
telling you to go open a room first. It now asks the bridge to probe — open one throwaway
session, read the options (applying saved selections), close it — when the screen is shown,
with a loading line while it runs and a retry if the agent could not be reached.

* feat(runtime): one runtime catalog, extensible without a rebuild (#83)

The four places that had to agree on the preset list — the config type union, the ACP_PRESETS
record, the wizard's CHOICES, and the hand-written error string — collapse into one catalog in
runtime-catalog.ts, so adding a built-in is a single entry. A machine can register its own
agents in ~/.quartet/runtimes.json (name → command/args/label/installHint); they appear in the
wizard, answer to --runtime <name>, and carry an install hint, with built-in and reserved names
protected. An agent that does not speak ACP still needs its own TurnRunner; this is only about
the ACP shortcuts.

This branch was successfully deployed

1 active deployment
Preview — c603815c Deployed Sep 19, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant