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

Adapters

Tree view of all installed adapters with expandable detail sections:

• Info — tools count, spec type, usage stats, token status
• Logs — request history from requests.jsonl with status icons, duration, and relative timestamps. Hover for full request/response details in a markdown table.
• Policies — rate limits, timeouts, retry, circuit breaker, and logging configuration parsed from policies.json

Right-click context menu:

• Configure Token — set a token value for adapters missing credentials
• Verify Connection — run proof-of-life play to test the adapter
• Browse Catalog — search 635+ API adapters, view specification details, 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).

Plays

Tree view of all locally installed plays. Grouped by org when multiple orgs exist. Click any play to open it in the editor.

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 deno run --allow-all.

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 deno install, 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. 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.

Requirements

• rote CLI installed and on PATH (or configure modiqo.executablePath)
• VSCode 1.85.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 an installed pre-snapshot CLI, such as Rote 0.83.0 (the minimum supported release):

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

Commands

All commands are accessible via Cmd+Shift+P with the modiqo: prefix:

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.