Roadmap

Current release: v1.7.0 — Artemis · Moghbeli.

The static catalog contains 338 sites.

It contains 1896 registered commands. The runtime also adds core and host-discovered commands.

Shipped

• Local bilingual operation search and command contracts
• v2 success and error envelopes
• Web, browser, desktop, local-tool, file, and protocol operators
• Browser profiles, sessions, targets, and background or foreground visibility
• Desktop accessibility and visual provider routing
• Local permission profiles, approvals, and run records
• YAML adapter authoring, user adapters, and repair verification
• CLI, MCP, and ACP entry points
• Generated operation catalog and bilingual documentation

In progress

Contract parity

Core commands and adapter commands are converging on one operation contract across CLI, MCP, ACP, dry-run, generated agent files, and docs.

Browser and desktop reliability

The current focus is stable background browser control, clearer provider health, durable target ownership, and repeatable accessibility paths for common desktop applications.

Evidence after actions

Mutating operations are gaining clearer post-action state and effect status so agents can distinguish dispatch from an observed result.

Harness evolution

The 1.2 development line adds private evidence packets, isolated adapter candidates, paired baseline comparison, held-out promotion gates, conflict-safe rollback, and Agent Plugins 1.0 skill discovery. The first editable component is one YAML adapter. Skills, routing policy, and delivery policy remain later component types after the adapter gate has enough transfer evidence.

Adapter authoring

The authoring loop is moving toward shorter scaffolds, reusable site notes, focused fixtures, and repair output that can be applied directly by coding agents.

Compact discovery

Search, deferred MCP tools, and generated agent indexes select the commands and schemas relevant to each task.

Later

• More page-native and application-specific operators
• Broader Windows and Linux desktop coverage
• Additional registry inputs that map cleanly to the operation contract
• Verified persistent state for long-running workflows
• Scoped model and domain affinity in discovery ranking
• Local aggregation of verified patches without uploading raw traces

How priorities are chosen

A roadmap item advances when it improves a real operation path, a shared contract, or the ability to diagnose a failure. Release history lives in CHANGELOG.md.