Set up a read-only background research agent

A user had a Dot start a separate research worker with web and docs access while other jobs were already running.

Done with Dots· Intermediate· Oct 2026

What they did
The user had already filled the Dot’s own cloud computer and a linked Linux machine with other tasks, then asked it to launch another agent anyway. Dot agreed, took a limited research assignment, and made sure this new worker had no computer or filesystem target. It ran with only read-only web and documentation tools.
How it went
The background agent worked at the same time as the two other jobs, so the user treated it as its own non-computer helper. No performance metrics or detailed findings were shared from that run.
Tips
This is useful for research that only needs reading and summarizing, not actions on a machine. If you rely on multiple Dots or connected systems, keep track of how usage is being counted so you do not lose sight of limits.

Try it yourself with Dots

Create a background research agent for [topic]. Give it read-only access to [web sources] and [documentation sources], and ask it to answer [specific questions] with a short summary and links to the sources it used. Do not give it any computer, terminal, or filesystem target. Once it is ready, tell me what tools it can use and how I can request status updates. Before it does anything irreversible, such as sending, submitting, deleting, or paying, pause and ask for my approval first.

Fill in the [brackets]. Agents can make mistakes, so review anything before it is sent, paid or deleted.

Get 3 agent uses like this every morning

With the day's top AI news. Free, and one click to unsubscribe.