Skip to main content
Each step in a workflow runs an agent: a model with instructions and a set of tools. You set them on the workflow proposal’s Agents tab when you create a workflow.

Models

Pick each agent’s model and Reasoning level on the Agents tab. Larger models and higher reasoning levels handle harder tasks, but they’re slower and use more credits.

Tools

Approval

A tool that makes changes shows an Approval setting once you select it:
  • Don’t ask: runs now: the agent calls the tool right away.
  • Ask later: runs once OK’d: the call is saved and the agent carries on. The call runs once a person clicks Approve, even after the run ends.
  • Ask first: waits for OK: each call waits until a person clicks Approve or Deny.
See Approve tool calls.
Web pages and repository content are written by others and can mislead an agent. Before you give an agent that reads them tools that make changes, set those tools to Ask first: waits for OK.

File issues in Linear or Jira

A workflow can file issues in Linear or Jira where you choose.
1

Connect the tracker

Connect Linear or Jira in Settings → Integrations.
2

Choose where issues go

On a workflow proposal’s Agents tab, click Edit tools and select the Linear or Jira tool. Pick an account, then the team or project that issues go to.
A saved workflow files each problem once. When a later run finds a problem it already filed, it reuses the existing issue.

Save reports and files

An agent can save a deliverable, such as a report, a CSV, or a PDF, to the run’s Outputs tab. When you create the workflow, tell Research what to deliver, for example “save a Markdown report of what you found”. See Results.

Open pull requests

An agent can deliver its changes as a pull request. When you create the workflow, ask Research for it, for example “open a pull request with the fix”. The proposal then gives that agent write access to the run’s repository.
  • Write access works only in a workflow run on a single repository.
  • There’s no approval step. An agent with write access can push whenever the workflow runs.
  • The repository’s push rules still apply.
The agent reads repository content and runs the repository’s own scripts. Content that misleads the agent can misuse its access. Give write access only to agents that need it.