01
Your repository
A durable project workspace keeps source, generated changes and Git history together.
Solutions / builders
Your agent can work where your code already lives.
OpenLink Local keeps the project, runtime and durable session state on your machine. Add self-hosted or VTSLX AO cloud capability only when the work calls for it.
Local project
READY$Review the checkout flow and fix the failing test
01Read project context
02Update implementation
03Run local verification
04Prepare reviewable diff
FILES
LOCAL
SESSION
DURABLE
RUNTIME
PROJECT
The default is a choice
Cloud-only tools move the center of gravity away from the project.
When source, sessions, previews and execution begin in a hosted workspace, local control becomes an integration problem. OpenLink makes local operation a complete product mode instead of a limited companion.
No mandatory hosted workspace for local projects
No silent switch between local and cloud identity domains
No silent fallback to a different configured model
A complete local stack
Local is the workspace, not just the editor.
OpenLink Local starts the services needed for a complete project loop and keeps durable project state inside an independent local identity and data domain.
02
Your agent sessions
Local sessions remain locally authoritative until you explicitly choose a cloud workflow or migration.
03
Your browser context
Persistent browser profiles and live previews stay inside the same project loop as the agent.
04
Your project state
Local identity, database, realtime, storage and runtime services form an independent operating domain.
One project loop
From intent to a reviewable result—without context switching.
The agent, browser preview, runtime and repository share the same project boundary, so verification happens beside the change rather than in a disconnected cloud surface.
01
Describe
Start with the outcome inside the active project.
02
Build
The agent reads, edits and runs inside the project runtime.
03
Preview
Inspect the working product without leaving the workspace.
04
Keep
Review the diff and preserve the result in your repository.
Grow without rewriting the workflow
Stay local. Self-host. Or add cloud capability.
Deployment is an explicit choice, not a hidden dependency. Use the boundary that fits the project today and adopt another through a deliberate migration or cloud workflow.
OPENLINK LOCAL
Keep the complete workspace on the machine.
Identity, project state, sessions, storage and runtime services operate as an independent local domain.
SELF-HOSTED
Run the control plane inside your infrastructure.
Use the same workspace contracts while your organization owns the deployment boundary and operating policy.
VTSLX AO CLOUD
Add managed cloud capability by choice.
Use project-scoped cloud runtimes, remote access and organization controls when the workflow needs them.
Local-first describes where OpenLink runs and persists project state. If you choose an external model provider, the context sent to that provider follows the provider configuration you selected.
Keep the center of gravity
Build with an agent that stays attached to the project.
See how OpenLink combines a durable project workspace, agent sessions, browser preview and runtime services in one local-first loop.