Back to blog
Guide8 min read
How to Automate Linken Sphere with AI — No Scripts Required
Operate authorized Linken Sphere workspaces through natural language and use Ornold Vision to test visible page elements across multiple sessions.
Jul 17, 2026AI Operation, Not Another Script
Linken Sphere provides isolated browser workspaces with separate storage, cookies, and network settings. The missing layer is often operation: somebody still has to prepare approved test sessions, launch them, open pages, inspect what loaded, and repeat the same QA actions across the batch.
Ornold connects an MCP-compatible AI agent — Claude Code, Codex, Cursor, Windsurf, or another client — directly to Linken Sphere. You describe the result in ordinary language. The agent chooses the appropriate Ornold tools, while Sphere remains the browser environment where the work happens.
Three Layers, One Workflow
- **Linken Sphere** creates and isolates browser profiles, controls their lifecycle, and exposes profile management through its local API.
- **Ornold MCP** translates the agent’s plan into explicit browser and Sphere operations: create, name, start, navigate, inspect, click, type, wait, and verify.
- **Ornold Vision** analyzes what is actually visible on the screen and returns element coordinates, so interaction does not depend only on fragile CSS selectors.
1. Create and Start Profiles in Plain Language
With Ornold Pro, an AI agent can use Linken Sphere’s native management API instead of asking you to prepare every profile manually. It can create quick sessions, assign clear names, configure connection and GEO settings when provided, start selected sessions, and connect them for browser automation.
The joint Linken Sphere × Ornold publication will include a campaign code that activates Ornold Pro for three days, so readers can repeat profile creation and the vision workflow before choosing a plan.
2. Automate the Work, Not Just the Launch
Starting a profile is only the first step. The same agent can navigate a selected group of sessions, wait for a page state, fill inputs, upload files, take screenshots, and check which profiles completed the action. Every command can target only the session IDs created for the task, leaving existing workspaces untouched.
This is the practical difference between a chat answer and an operator. The agent does not merely suggest a script. It calls typed MCP tools, receives structured results, and can verify the browser state before moving on.
3. Why Ornold Built Its Own Vision Model
Selector-based automation assumes the page structure stays stable. Real profiles may receive different layouts because of locale, responsive breakpoints, A/B tests, consent banners, or asynchronous loading. A selector that works in one profile may be absent in another even though a human can still see the same button.
Ornold’s own vision model works from the rendered page instead. The vision pipeline captures screenshots, groups sessions that show the same state, finds visible interactive elements, and returns normalized bounding boxes. Ornold then clicks the center of the selected box using coordinate-based mouse movement.
- **Screenshot first.** The model observes the page the user actually sees, not an assumed DOM structure.
- **Grouped analysis.** Matching page states are analyzed together instead of spending one full analysis per identical profile.
- **Visible element detection.** Buttons, inputs, links, and controls are returned with labels and coordinates.
- **Targeted recovery.** If one profile diverges, the agent can re-analyze that profile without repeating the successful batch.
Vision makes automation more resilient to layout and markup changes; it does not guarantee compatibility with every third-party platform or workflow.
Live Demo: Three Disposable Sessions
The final co-published demo uses three new sessions with the same locale and viewport. No accounts, cookies, or proxy credentials are added. The agent creates and names the sessions, starts them, opens ls.app, uses Ornold Vision to find the Blog navigation item, clicks it in all three browsers, waits for the Blog page, verifies a 3/3 result, and stops the sessions.
After Ornold MCP is connected and the three-day Pro code is active, paste this prompt into your AI agent:
Run a safe Linken Sphere + Ornold Vision demo.
Rules:
- Never touch my existing Linken Sphere sessions.
- Create exactly 3 new quick sessions and keep their UUIDs as the only targets.
- Name them ornold-demo-01, ornold-demo-02, and ornold-demo-03.
- Do not add accounts, cookies, or proxies.
Steps:
1. Create and name the three sessions, then start only those sessions.
2. Confirm all three are connected with browser_list.
3. Navigate only those browser IDs to https://ls.app.
4. Run grouped vision analysis. Find the visible “Blog” navigation item for each page-state group and click it by its returned coordinates.
5. Wait until the Blog page is visible, then run browser_status and take a final grouped screenshot.
6. If any session is behind, re-run vision analysis only for that session and report the recovery.
7. Stop all three demo sessions when finished.
8. Ask for my explicit confirmation before deleting them.
Finish with a concise report: created, connected, reached Blog, recovered, stopped.
A successful run ends with all three demo browsers on the Linken Sphere Blog page. If ls.app changes its navigation label or layout before publication, the demo must be re-recorded and the prompt updated rather than presenting an old result as current.
Connect Ornold to Linken Sphere
You need Linken Sphere running on Windows or macOS, Node.js 20+, an Ornold token, and an MCP-compatible AI agent. Review the Linken Sphere integration page or let your agent read the public install guide and configure itself.
Install Ornold MCP for Linken Sphere automation.
Read the official agent guide first:
https://raw.githubusercontent.com/ornold-ai/ornold-mcp/main/AGENTS.md
Ask me for my Ornold token and Linken Sphere port (default 40080). Configure this AI agent with Linken Sphere enabled and mode=vision. Install the Ornold skill where supported, then verify the connection with browser_status. Explain any failure in plain language.
Create your token, copy the ready configuration, and use the three-day Pro campaign code when the joint publication goes live.
Connect Ornold to Linken SphereWhat to Automate Next
- Linken Sphere integration — supported connection methods and authorized workflow examples.
- Claude Code integration — connect Ornold to an MCP-compatible coding agent.
- Pricing — compare concurrent session limits for QA and internal operations.