Preview inside the project loop
Preview
Preview
Open the relevant project result before a reviewer has to reconstruct which environment or version was checked.
OpenLink / Browser & preview
Review the work in a real browser.
Keep a supported browser session close to the project, so a change can be previewed, inspected and reviewed where the work actually runs.
Supported Browser Host · Self-hosted first
Browser HostIllustrative session
localhost:3000/projectsPreview ready
01 · Input
Start from the project result.
Project list preview
Atlas onboarding
Repository cleanup
Browser validation
Review handoff
Open the running preview attached to the project instead of recreating the environment in a separate tool.
Code changesBrowser resultYour review
From preview to review
The page result belongs beside the task.
A browser observation is useful when it preserves the request, the changed surface and the reviewer's decision in one project loop.
Illustrative flow
Browser HostIllustrative session
localhost:3000/projectsPreview ready
01 · Input
Start from the project result.
Project list preview
Atlas onboarding
Repository cleanup
Browser validation
Review handoff
Open the running preview attached to the project instead of recreating the environment in a separate tool.
Code changesBrowser resultYour review
Evidence produced: Project preview
Browser capability
A result you can inspect is easier to trust.
OpenLink does not turn a visual into proof by itself. It keeps the page observation near the context needed to evaluate it.
Inspect the changed surface
Observe
Observe
For supported Browser Host sessions, navigation and page observations can stay connected to the same task context.
Carry evidence into review
Review
Review
Keep the browser result alongside the request and code changes, so approval is based on more than a progress message.
Controls and boundaries
See the page without losing the boundary.
Browser availability depends on the selected agent, Browser Host and local configuration. The browser is one review surface in the project—it does not replace your deployment, access or model-provider controls.
Review agent setupYour environment first
Self-hosted execution begins with the runtime and host configuration you choose.
Configuration still matters
Tools, browser access and behavior vary by the selected agent and local setup.
Human review remains explicit
Use the browser result as context for a decision, not an automatic approval signal.
Browser & preview
Questions before you inspect a result.
What the current browser workflow is for, and what still depends on your setup.
It provides a review surface for supported configurations: you can keep a project preview and browser observations close to the task, code changes and subsequent review.