Roadmap

Roadmap

Phases, not dates. We sequence work by what unblocks the most users; we do not publish deadlines because we cannot honor them honestly. For live status on individual items, see the server repo's Issues.

Shipped

OSS conversion

All four repos (server, Node SDK, Python SDK, marketing site) MIT-licensed and public. Hosted-billing path removed.

Operator mode

Human-in-the-loop sessions with the agent / human / paused control state machine. Live viewer + event stream over SSE.

Vision agent

Built-in vision-based agent that takes a natural-language task and drives the browser using Claude or GPT.

Profile persistence

Persistent Chrome user-data directories for login state across sessions.

Shipping now

First public release (v1.0.0)

Multi-arch Docker image on GHCR, Node SDK on npm with provenance, Python SDK on PyPI via Trusted Publishing. Coordinated launch across all four repos.

Show HN

Drafted; fires when v1.0.0 publishes cleanly.

Next

OpenAPI 3.0 spec generation

Generate openapi.json from the server's zod schemas so the SDKs can be partly auto-generated and third-party clients have a contract to read.

More SDK language coverage

Go and Rust. Community PRs welcome.

Test coverage on the existing SDKs

SSE streaming, file upload, profile lifecycle, release_all / release_batch.

mkdocs-material site for the Python SDK

Currently README + skill.md + docstrings. mkdocs adds searchable HTML reference.

First-party Playwright Connect-by-CDP example

Today the SDK exposes the websocketUrl and puppeteer-core.connect() is documented; Playwright equivalent should ship as a first-class example.

Not planned

Things we have considered and decided not to do.

  • A hosted SaaS version operated by this project.
  • Telemetry, phone-home, or auto-update behavior.
  • Anti-detection improvements aimed specifically at sites that have opted out via robots.txt or ToS.
  • A built-in admin web UI. SSE endpoints + the SDK are the contract; consumers build their own UIs.

Have an idea?

Open a Discussion on the server repo. Significant feature proposals should land there before code lands.

Open a Discussion