---
title: research
description: Gather repo and external context for a request.
---

`research` asks a tool-capable agent to inspect the repo and gather relevant context before planning or implementation.

```bash
bunx smithers-orchestrator workflow run research --prompt "How should we add audit logs?"
```

<Frame caption="The research UI shows the tool-capable agent inspecting the repo and external sources before any planning.">
  <img src="/images/workflow-ui/research.png" alt="research workflow UI showing a research agent gathering repo and external context" />
</Frame>

## Inputs

| Input | Type | Default |
| --- | --- | --- |
| `prompt` | string | `"Research the given topic."` |

## Use it when

- The task touches unfamiliar code.
- External docs or dependency behavior matter.
- You want file references and prior art before committing to a plan.

Follow with `plan` or `mission`.

## Use something else when

- You already have enough context and just need a plan: use [`plan`](/workflows/plan).
- You are ready to build: use [`research-plan-implement`](/workflows/research-plan-implement), which runs this research step for you.

## Resume & retry

`research` is read-only; it gathers context without changing the repo and returns it in the run output. Runs are durable and resume with `up --resume`.
