Use SearchAgentSky for cited answers from public sources with no setup. When a task needs a signed-in browser, give Unchained the outcome—not every click. It handles the multi-step browser work in a dedicated Chrome workspace on this computer while you review the result and keep final actions under your control.
You set the outcome and boundaries. Unchained handles the browser steps. You review the result.
Choose the right pathThe local connector should earn its setup. Start with the lightest product that can finish the task.
SearchAgentSky searches live public pages, builds a cited answer, and lets you publish or share the result. It runs in the browser with no local client.
The guided Unchained path opens its own Chrome workspace on this computer. Sign in there only to sites the job needs, then let a supported AI path navigate, collect, compare, or prepare browser actions.
What the guided connector means: it does not attach to the Chrome profile you are currently browsing in. It launches a dedicated Unchained Chrome workspace whose files stay on this computer. Commands, browser-derived page context, and tool results needed for the task may be sent to Unchained and the selected AI provider. Quit the local agent to stop browser automation. Review the privacy policy before connecting sensitive work.
Choose a job below. Each guided example runs in the dedicated local workspace and ends with a result or prepared action you can review.
Unchained handles browser steps in a local Chrome workspace. Start with read-only work and keep consequential actions with you.
Describe the result you want from a signed-in site or multi-step browser workflow—not every click along the way.
The guided connector launches a dedicated Chrome workspace. You sign in there only to the sites the job needs.
Use Unchained web chat or connect a supported Claude, Codex, OpenCode, or MCP workflow.
Check the result, the pages used, and any prepared action before you ask the agent to send, buy, or submit.
The value is not another public-web answer. It is giving the workflow a browser session that can stay signed in and take steps on this computer.
The guided path uses its own on-machine Chrome data directory, so the workspace can retain its sign-in state between runs.
Use the guided Unchained web experience or a supported Claude, Codex, OpenCode, or MCP client.
Quit the local agent to stop browser automation, and keep final send, purchase, and submit actions with you.
Ask for a linked shortlist, status report, comparison, or prepared browser change rather than a vague automation run.
Watch one public task first. If your own task needs a signed-in browser session and actions, use the guided connector. Developers can go straight to MCP or a supported CLI lane.
Best if you want to see the browser loop before connecting anything.
Best when the task depends on a site login or browser actions and is worth using a dedicated local workspace.
Best if you already work from Claude, Codex, OpenCode, or another MCP client.
Use SearchAgentSky for public research. When the job needs a signed-in browser session, open the dedicated Unchained workspace or use a supported developer path.