Give an agent a bounded research-to-deliverable task with account-scoped tools.
Conversation & research · Documented · Documentation checked 2026-10-04
Perplexity search, Research, Projects, and Computer; API access has separate billing.
Free, Pro, Max, and Enterprise access differ. Brain is a Research Preview for eligible Computer users.
The worked example is illustrative and has not been tested in a signed-in product account.
What it does and how it connects
Give an agent a bounded research-to-deliverable task with account-scoped tools.
Computer pursues a deliverable through research, files, and connected tools. A connector grants access to another service; an agent uses those capabilities in a task loop. This can help with varied intermediate steps, while a fixed workflow is easier to audit when the route is already known.
Walkthrough
Use the product named in the access panel. The steps below combine documented controls with the editorial example.
- Choose an eligible Computer task and define a small output with success criteria.
- Provide approved sources and narrowly scoped account connections.
- Begin with read-and-draft work and inspect tool activity.
- Review the output and proposed external actions before any broader or recurring task.
Worked example
Combine three public reports into an AI literacy briefing. An optional approved file connector can add the workshop agenda. The task should produce a draft, not invite participants or publish an event.
Create a private briefing from these approved reports and the named agenda file. Cite every factual claim and list missing evidence. Read and draft only. Stop if the correct account or source cannot be established. Do not send messages, change source records, or publish.
Inspect and verify the result
Check source identity, artifact contents, and the actual connected-account activity. Confirm every consequential action against destination and parameters. A finished report does not reveal every tool side effect by itself.
Limits and troubleshooting
Access and usage differ by plan. Recurring agent work needs exception handling and a stop condition, not just a broad goal. If a tool fails, stop or use an explicitly approved alternative source; do not imply success.
Data, permissions, and actions
Connected requests use external identities and can read or change service data. Scope tools by project and account. A recurring task retains ongoing authority until disabled or access is revoked.
Related reading
Personal Computer and local files
Separate a desktop-connected task from work that only has cloud or uploaded context.
From search evidence to a usable deliverable
Create a verified research brief and an inspectable file from public sources.
A project-scoped preparation agent
Prepare a workshop draft pack using approved project files and narrowly scoped connected context.
Permissions and meaningful approvals
Decide what a system may read, what it may change, and when someone needs to authorize a concrete action.
Sources and verification
Documentation checked 2026-10-04. Examples are illustrative unless described otherwise.
Computer at Work guide · Perplexity
Subscription plans and API boundaries · Perplexity