Skip to main content
A task turns one goal into finished, multi-step work. You describe the outcome you want, and Locus calls the right tools with your credits, checks the results, and gives you a table or answer, files, and the exact cost. Tasks are available on Locus Pro and Locus Pro Enterprise, with no separate plan or setup.

​
How it works

  1. You describe the outcome. Locus turns your goal into a fixed set of requirements: the deliverable, the count, the fields, and the criteria each result must meet.
  2. Locus does the work. It finds the right tools in your catalog and calls them with your credits and spending controls. A task can only use tools your connection can already call.
  3. Locus checks the result. Every delivered value must be backed by a response from one of the task’s calls. See How Locus checks task results.
  4. You get the result. A table or answer, downloadable files, the status of each requirement, and the settled cost.
Example goals

​
Choose a task or another option

​
Start a task

Connect your agent through MCP, then ask for the outcome:
Try this prompt
Your agent starts the task and waits for the result. Waiting never starts a new task or charges again. Read-only MCP connections cannot run tasks.

​
Follow a task to the end

Tasks run in the background on Locus. Closing your connection or timing out your request does not stop a task. Locus saves progress after every step, so an interrupted task continues from its last saved step.

​
Continue, cancel, or resume

  • Wait or check status at any time. Both are free.
  • Answer a question to let the task continue.
  • Cancel to stop further calls. A running task stops after its in-flight calls finish, and work already done stays charged.
  • Resume a partial or failed task to continue from its recorded work, for example after you add credits. You can set a new budget, as long as it covers what the task has already spent.
  • Retry safely. Repeating a start request with the same idempotency key returns the original task instead of starting a second one.

​
Key limits

  • Up to 5 queued or running tasks per account.
  • A task’s deadline is 15 minutes by default and can be up to one hour. Time spent waiting for your answer does not count.
  • Up to 80 steps per task.
  • The response holds the first 200 rows; the file holds every row.
  • Files are kept for 7 days, and download links last 1 hour.

​
What tasks do not do

Tasks gather, combine, and check information. Locus refuses endpoints that look like they take action, such as sending messages, posting, buying, booking, or deleting. If your goal asks for one of those actions, the task cannot meet that requirement and does not complete. Locus recognizes these endpoints by their method and name, so keep action tools disabled for connections that run tasks if you want a hard boundary. Your inputs and the content the task retrieves are treated as data. They cannot change the task’s budget, tools, or permissions.

​
Next steps

How Locus checks task results

See what a task returns and how every value is verified.

Task costs and budgets

Understand what a task costs and how its ceiling works.

MCP

Connect an agent and run tasks alongside the other Locus tools.

Locus Pro API

Start and follow tasks from your own code.