Availability
What's real today, what isn't yet.
allwright is being built in public, and “available” should mean something specific: real and working, not finished. Web automation runs today against real Chromium and Firefox browsers, but only through a small, minimal set of actions — nowhere near full web test coverage yet. This page is the detailed, continuously updated picture behind the status pills you see elsewhere on the site — surface by surface, capability by capability, and language by language.
Surfaces
Web is the only surface with a real, installable plugin today. The rest have a reserved place in the plugin catalog but no runtime build yet — installing them isn't possible until that changes.
Web
Available nowChromium and Firefox both work, but only a small core action set — not yet full web test coverage.
Mobile
Not yet availableAndroid & iOS, native and hybrid apps.
Desktop
Not yet availablemacOS, Windows, and Linux applications.
API
Not yet availableBackend checks in the same test run.
Web, capability by capability
“Available now” means the web plugin is real, installable, and the actions below genuinely work against Chromium and Firefox — not that web automation is done. This is a small, deliberately minimal core action set today, and on its own it is not yet enough to cover a real web test suite. The list on the right is what's still missing before it is.
Available now
- Launch a real Chromium or Firefox browser — no separate driver to install or version-match
- Open and close tabs within a browser session
- Navigate to a URL
- Click an element
- Type into a field
- Hover over an element
- Press a key on an element
- Focus an element
- Highlight matching elements for debugging
- Count matching elements
- Read visible or raw text from an element
- Wait for an element to appear or become visible
- Retrying, Playwright-style text/count/visibility assertions (via @allwright.dev/vitest)
Not yet available
- Screenshots and visual snapshots
- File upload and download handling
- Browser dialogs (alerts, confirms, prompts)
- Network mocking or request interception
- Cookies and saved session state
- Geolocation and other device permissions
- Mobile viewport and device emulation
- Drag and drop
- Multiple isolated browser profiles per session
- Safari / WebKit (Chromium and Firefox only today)
Every client language exposes this same capability set — there is no language-exclusive functionality on the web surface today.
Mobile, desktop, and API
These have a reserved slot in the plugin catalog and are part of the direction, but there is no installable plugin and nothing to try yet.
Mobile
Not yet availableAndroid & iOS, native and hybrid apps.
Desktop
Not yet availablemacOS, Windows, and Linux applications.
API
Not yet availableBackend checks in the same test run.
Client languages
“Published” means a normal package-manager install. “From source” means the client is complete and working, but you build it from the repository instead of pulling it from a package registry.
Rust
PublishedThe engine itself, plus a high-level client.
View example →Go
PublishedA Playwright-style Browser and Page API.
View example →Java
From sourceA Gradle-based client for JVM test suites.
View example →Python
From sourceA client that feels at home in pytest.
View example →TypeScript
PublishedCore client plus Vitest fixtures, for TypeScript or plain JavaScript.
View example →This page changes as allwright ships
Follow the repository to see new capabilities and surfaces land in real time, or head back to see how the plugin model fits together.