modiqo
VSCode extension for rote — Execution Context Engineering.
Provides a sidebar explorer, play runner, workspace dashboard, and registry browser that surface everything happening inside ~/.rote.
Features
Reference
Open Info from Studio, then select a grammar topic, tool alternative, or guide.
The reference panel reads rote guidance <id>, such as rote guidance grammar/query.
The extension probes document support once per CLI configuration and caches the result.
CLIs with canonical documents use path IDs; older CLIs use the equivalent legacy command,
even when both builds report the same version.
The minimum supported CLI is 1.0.0. A reference without a legacy equivalent asks you to run rote update.
CLI failures appear in the reference panel.
Adapters
The adapters panel (modiqo: Open Adapters) lists every installed adapter and opens a detail view for each:
- Info — adapter ID, spec type, tools count, auth type and variable, group, usage, and success rate. Token status shows in the header; the base URL is on the Manifest tab.
- Logs — today's requests from
logs/requests_<date>.jsonl with status icons, duration, and relative timestamps that update every minute and when the panel becomes visible
- Policies — rate limits, timeouts, retry, circuit breaker, and logging configuration parsed from
policies.json
Every installed release is its own card. Releases that share a name are grouped under one heading, and by publisher when more than one publisher ships that name. Each card shows its release (<publisher>/<name>@<version> or @development/<name>) under the title. Tokens are stored by environment variable, so all releases that read the same variable share one token.
Background refreshes keep the selected adapter release and detail tab open. Tab changes and unchanged refreshes preserve unsaved Manifest edits; Cancel reloads the saved values. The Hub status compares the refreshed local version with the last fetched published version. A local version ahead of the published version shows “Update available”.
From the panel you can configure auth, edit manifest fields, push to the registry, and open the catalog of 635+ API adapters to view specifications and get install commands.
The adapter detail panel exposes name, description, and base_url. For other manifest fields (tags, sensitivity_tier, additional_headers, enable_parameter_cleaning), use rote adapter set (see rote adapter set --help).
When several releases of one adapter are installed, the detail view shows an "Other releases" row that jumps to each of them. On a registry release the name, description, and version bump are read-only; fork the adapter to @development to edit it. Its base URL stays editable: the CLI keeps the change in the release's config overlay, and the panel shows that effective value rather than the published one.
Plays
Tree view of all locally installed plays. Grouped by org when multiple orgs exist. Click any play to open it in the editor.
Background refreshes keep the selected play and detail tab open. Unchanged pages keep their scroll and search state; a removed play returns to the list. A failed refresh keeps the last page visible and offers Retry.
Right-click to Run Play. The panel resolves each play's contract from
rote play info <path> --json (falling back to reading the play's frontmatter
when the CLI is older), so it understands both crystallization shapes:
- Biplanar / steps plays (frontmatter
steps:, the current crystallization
default) execute via rote play run. steps_with_presentation plays also
pass --output=json and render the presentation payload as a result card.
- Legacy body plays (no
steps:) execute via rote play run, with positional
arguments after --.
Array parameters offer JSON entry such as ["bug","auth"], Empty list, and
Use default when a default is declared. Optional arrays without a default start
with Empty list, which explicitly sends name=[]. An empty list also satisfies
a required array input. Use default leaves named inputs for the CLI to default.
The panel validates string lists and integer lists before Run, Resume, or Open in Terminal.
Integer arrays declare items: {type: integer} and preserve every signed 64-bit integer,
including IDs above JavaScript’s safe-integer limit. Array
execution is enabled only when rote play info --json confirms type: "array"
for each array input, plus items.type: "integer" for integer lists. A CLI that reports a string, or failed inspection, blocks
array execution with an update message. Dev and prerelease builds work when they
report array support; scalar plays retain their existing CLI support. String arrays require
rote 0.90.0 or later (rote update). Integer-array CLI support is not yet released;
until it ships, use a development build containing that support. Unknown item types
block execution. Integer input rejects -0; use 0.
Defaults and parameter examples come from CLI metadata when available. The panel
accepts native JSON values from newer CLIs and legacy strings from older versions.
Older CLIs without parameter examples use the play file as a fallback. Invalid parameter
metadata produces a named error; ambiguous duplicate parameter properties report their
JSON path. Published summaries normalize array defaults independently, so an invalid
array default does not hide the remaining capabilities.
When a run fails with a recoverable error, the results view offers a Resume
action (reusing completed steps) and surfaces the CLI's own remediation command
(e.g. rote runtime install deno, or rote deno install on a CLI without
rote runtime, or rote play bind/grant for fingerprint-v2 plays).
Workspaces
Open Canvas from Studio to browse explorations and play runs returned by rote workspace list --json, including nested run directories. Commands, Trace, Plan, and Stats display the recorded workspace classification as a play, exploration, unclassified, or unavailable badge. Badges refresh when the classification changes. Browser plans retain their browser stdio label. Refresh lists installed adapters again before rereading workspaces, so an adapter installed from a terminal clears a removed mark. Each workspace provides:
- Trace — opens a Gantt timeline panel showing request durations, token usage, and success rates. Bars are color-coded (green = success, red = error) with opacity encoding token intensity. Hover for detailed tooltips.
- Commands — opens a split-panel view with command timeline on the left and request/response JSON (syntax-highlighted) on the right. Supports
HttpRequest, SetVariable, and QueryRead command types.
- Response files (
@1.json, @2.json, ...) — click to open directly in the editor.
Registry
Connects to the Modiqo registry with automatic authentication handling:
- Auth check — runs
rote registry whoami --verbose to detect valid/expired tokens
- Login — if expired, click to pick Google or GitHub OAuth. Browser opens automatically; the view polls for completion and refreshes when authenticated.
- Adapters — lists all adapters in the bootstrap community with fingerprints. Click for a detail panel showing specification, bound skills, and install command.
- Skills — lists all skills with their adapter bindings. Click for a detail panel showing adapter fingerprint cross-references.
- Overview (graph icon in title bar) — Skill-Adapter Fingerprint Map. A heatmap grid where rows are skills, columns are adapters, and active cells show fingerprint bindings on hover.
Loading states show animated spinners during auth check and data fetch. Adapters and skills load in parallel.
Status Bar
Shows adapter health at a glance: rote: 8/10 adapters with warning icon when tokens are missing.
File Watcher
Monitors ROTE_HOME (default ~/.rote) for adapter, token, play, and workspace-root changes. Workspace and run roots use non-recursive watches; roots created after activation are attached automatically, with a five-second retry if needed. Canvas polls the CLI for nested workspace activity while visible, backs off when idle, and pauses when hidden.
Token notifications check the vault database's file state after events settle. Read-only vault access leaves views alone; database updates, replacement, and removal refresh them. If secrets/ is created after activation, a five-second retry attaches its watcher and detects the first token write. The same retry attaches adapters/ and flows/ when the CLI creates them later, and lists adapters and plays again once, since the folder and its first entry arrive together.
Requirements
- rote CLI installed and on PATH (or configure
modiqo.executablePath)
- VSCode 1.93.0+
CLI compatibility
Older supported CLIs retain local play listing, inspection, execution, and deletion.
Deletion uses the identity returned by the CLI. The editor checks that identity again before deleting.
Ambiguous names require an updated CLI that can select an exact local copy.
Hub publishing requires immutable snapshot support, which ships in Rote 0.85.0. The editor reads rote --version to decide; on an older CLI the play panel shows an update action.
Older dependency scans retain known plays and warn that other local copies may be omitted.
Missing provenance stays unknown. The editor does not infer it from registry markers.
Run the compatibility tests against a historical pre-snapshot CLI, such as Rote 0.83.0:
ROTE_COMPAT_BINARY=/absolute/path/to/rote npm test -- client/legacyPlayBinary.test.ts
These tests create temporary homes and synthetic local authentication. They do not use live credentials.
Configuration
| Setting |
Default |
Description |
modiqo.executablePath |
rote |
Path to the rote binary. Set this if rote is not on your PATH. |
Telemetry
The extension records usage and error events only when VS Code's global telemetry setting is on.
The extension hands events to rote after 20 events or 30 seconds, whichever comes first. rote decides whether to upload them. To turn uploads off, run rote telemetry upload-disable. This also deletes events that are waiting to upload.
rote stores accepted events locally and uploads at most once per upload_interval_secs (set in ~/.rote/config/telemetry.json, default 5 minutes). An upload runs when rote is next used after that interval, so queued events can wait longer when rote is idle.
rote queues events only while you are logged in, and uploads them only under the account that was logged in when they were queued. Events handed off while you are logged out are dropped.
Commands
All commands are accessible via Cmd+Shift+P with the modiqo: prefix:
| Command |
Description |
modiqo: Refresh Adapters |
Reload adapter list |
modiqo: Configure Token |
Set a token for an adapter |
modiqo: Verify Connection |
Run proof-of-life for an adapter |
modiqo: Browse Adapter Catalog |
Search and explore available adapters |
modiqo: Run Play |
Execute a play in the terminal |
modiqo: Refresh Plays |
Reload play list |
modiqo: Refresh Workspaces |
Reload workspace list |
modiqo: Show Trace Timeline |
Open Gantt timeline for a workspace |
modiqo: Show Commands |
Open command request/response viewer |
modiqo: Refresh Registry |
Reload registry data |
modiqo: Registry Login |
Authenticate with Google or GitHub |
modiqo: Show Registry Overview |
Open skill-adapter fingerprint map |
License
Business Source License 1.1 — same as rote.
Play UI tests
npm run test:ui launches VS Code and clicks the Plays list, detail page, and run page.
The tests verify source opening, execution results, and confirmed deletion against the installed Rote CLI.
They use temporary Rote homes and VS Code profiles. No live credentials are used.
Set ROTE_UI_BINARY to test a specific CLI binary.
Set VSCODE_EXECUTABLE_PATH to use an existing VS Code executable instead of downloading the stable version.
On Linux, run xvfb-run npm run test:ui.
Failed tests save a screenshot and Playwright trace under test-results/.
Set ROTE_COMPAT_BINARY to run the pre-snapshot UI case and real CLI compatibility tests.
CI pins that binary to Rote 0.83.0.
Snapshot publishing tests use a fixture CLI to simulate Hub responses and record subprocess arguments.
They exercise real webview clicks and extension handlers, but do not contact a registry service.