Compose the browser.
Set it in orbit.
Turn browser work into a visual graph. A durable cloud browser runs it; live status streams back.
What is or-bit?
A visual builder for durable browser workflows. Compose a graph with a trigger, deterministic actions, browser interactions, observations, and AI agents. When it runs, a real cloud Chrome does the work — and every meaningful update streams back to the canvas so your team can see what happened, not merely that it happened.
Every node is a real thing the browser does.
Compose them on a canvas, run them as durable background jobs, and watch each step resolve against a live page in real time.
Compose the run on a visual graph
Drag triggers and browser steps onto a canvas and wire them in the order work happens. Each node carries its own config and hands its output to the next.
Deterministic navigation
Point a step at a URL and the cloud browser lands there every run — a stable starting page for everything downstream.
Act from plain language
Describe the action — “click Export”, “fill the login form” — and the agent performs it on the live page. No brittle selectors to maintain.
Read real values off the page
Pull the number, status, or text you care about straight from the rendered page, so every run reads live data instead of a stale export.
Build it together, live
Everyone in the workspace shares one canvas. See teammates’ cursors, edits, and running steps stream in as they happen — no refresh, no stepping on each other.
Hand off a goal, not a script
State an outcome in a sentence and the agent drives a real Chrome to reach it — opening pages, entering data, and adapting as the site responds.
Close the loop with a notification
End a workflow by mailing the result to whoever needs it — the observed value, a summary, or a done signal — the moment the run finishes.
or-bit vs tab-parade runbooks
| or-bit | Runbook | |
|---|---|---|
| Shows the full sequence of work | ✓ | ✗ |
| Runs in a durable background job | ✓ | ✗ |
| Uses a real cloud browser | ✓ | △ |
| Streams progress to the team | ✓ | ✗ |
| Keeps the logic available to improve | ✓ | ✗ |
Frequently asked.
How does a workflow start?+
Start nodes are the first point in a graph. They establish the run and give every later node a clear, inspectable path from trigger to outcome.
What can the browser actually do?+
Open URL steps navigate deterministically. Act, Observe, and Agent nodes then work against the live page to enter data, find values, or pursue a browser goal from plain language.
Does a run stop when I close the tab?+
No. Workflow execution is a durable background job. The visual canvas is where you monitor and control a run, rather than the fragile place the run lives.
How is workspace data separated?+
Every workflow query and write is scoped to the active Clerk organization. A workflow ID is never treated as an authorization token.