-
Notifications
You must be signed in to change notification settings - Fork 3
Asking Atlas
Atlas is the browser + research sub-agent. It opens URLs, takes screenshots, fetches HTML, clicks buttons, and reads pages. Multiple Atlas calls in the same turn run in parallel.
Just describe what you want — the orchestrator recognizes browser, web, and shell work and hands it to Atlas on its own. There's no magic phrase (saying Delegate to Atlas: works, but it's never required). Atlas runs in the background in its own context window — the orchestrator gets a job ID back immediately and stays free for your next message. When Atlas finishes, the result lands in the orchestrator's inbox and it reports back in the chat.
Open example.com and take a screenshot.
If two tasks are independent, ask for both and say they can run in parallel. The host runs them concurrently.
In parallel:
(1) screenshot example.com, AND
(2) fetch the title of example.org.
Screenshot a page — Screenshot example.com. Returns the rendered page as an image Atlas can read.
Read a URL — Open docs.example.com/api and tell me the auth options. Atlas reads the page text and summarizes.
Click + screenshot — Open the app, click "Sign in", screenshot the result. Atlas can interact with the page, not just read it.
Compare two pages — delegate two screenshots in parallel, then ask the orchestrator to compare them.
Atlas is never fire-and-forget. While a job runs, the orchestrator checks in on it every 45 seconds — elapsed time, tool-call count, and what it last did — and decides: leave it alone, stop it if it's stuck or looping, or redirect it.
If a job fails or gets stopped, the orchestrator reads the full output, works out what went wrong, and automatically retries with a reworked task. You only hear about a failure when it can't be recovered.
Atlas can't reach pages on private networks unless the host can. Pages behind login walls need credentials configured. Pages that block bots may return empty results — Atlas reports this honestly rather than fabricating.
The orchestrator does not code or edit files itself — it delegates those to Atlas. If you ask "fix the bug" without a file path, Atlas will have to guess; give it the path and the expected outcome.