> ## Documentation Index
> Fetch the complete documentation index at: https://openrush.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Agent setup

> Create useful marketing agents with OpenRush.

After MCP is connected, you can turn OpenRush into a repeatable marketing workflow.

Think of an agent as a saved way of working. It should know what job to do, when to use OpenRush, what answer format you want, and when to stop.

<div className="or-hero-line or-hero-line-small">
  Start with a <span className="or-pill or-pill-violet">marketing job</span>, give the agent <span className="or-pill or-pill-green">clear rules</span>, then reuse it whenever you need the same answer again.
</div>

## Good agent jobs

Start with one job. Keep it narrow enough that you can tell whether the answer is useful.

<div className="or-feature-grid">
  <div className="or-feature-card">
    <span className="or-feature-icon">
      <Icon icon="globe" size={30} color="#3B82F6" />
    </span>

    <span>Competitor scan</span>
  </div>

  <div className="or-feature-card">
    <span className="or-feature-icon">
      <Icon icon="chart-line" size={30} color="#8B5CF6" />
    </span>

    <span>Keyword gap review</span>
  </div>

  <div className="or-feature-card">
    <span className="or-feature-icon">
      <Icon icon="sparkles" size={30} color="#10B981" />
    </span>

    <span>Opportunity list</span>
  </div>

  <div className="or-feature-card">
    <span className="or-feature-icon">
      <Icon icon="image" size={30} color="#F59E0B" />
    </span>

    <span>SERP snapshot</span>
  </div>

  <div className="or-feature-card">
    <span className="or-feature-icon">
      <Icon icon="shield" size={30} color="#06B6D4" />
    </span>

    <span>Website audit</span>
  </div>

  <div className="or-feature-card">
    <span className="or-feature-icon">
      <Icon icon="users" size={30} color="#EC4899" />
    </span>

    <span>Weekly growth brief</span>
  </div>
</div>

## Write the agent instructions

Use a short brief. Good agents do not need long prompts.

```md theme={null}
You are my organic growth analyst.

Use OpenRush when you need fresh search, keyword, competitor, SERP, or website data.

Your job:
- Find the most important organic growth opportunities for {domain}.
- Compare the site against obvious search competitors.
- Explain what changed, why it matters, and what to do next.

Output:
- 5 bullet summary
- 3 best opportunities
- 3 risks or weak spots
- next actions I can give to a writer, founder, or marketer

Rules:
- Use plain language.
- Do not invent metrics.
- Cite the source or tool result when you make a claim.
- Ask me before doing anything outside OpenRush or the connected workspace.
```

## Use Claude Code

Claude Code supports custom subagents. Use a subagent when you want a reusable specialist, such as a growth analyst, SEO reviewer, or content brief writer.

To create a subagent:

1. Connect OpenRush with MCP from [Setup](https://openrush.io/dashboard/connect).
2. In Claude Code, run `/agents`.
3. Create a personal or project agent.
4. Give it a clear description, such as `Use this agent for organic search research with OpenRush`.
5. Limit tools where possible. A research agent usually only needs read and connector access.
6. Test it with one site before using it repeatedly.

<Tip>
  Claude Code subagents are useful when research would fill your main conversation with too much detail. The subagent can do the search work and return a clean summary.
</Tip>

Learn more in the [Claude Code subagents docs](https://code.claude.com/docs/en/sub-agents).

For scheduled work, use Claude Code routines. A routine is a saved prompt, repository, and connector setup that can run on a schedule.

Good OpenRush routine examples:

* Every Monday, create a competitor brief for your domain.
* Every Friday, find new keyword gaps to review.
* After a launch, check priority keywords and search results.
* Monthly, audit the site and list the highest-impact fixes.

Create routines at [claude.ai/code/routines](https://claude.ai/code/routines), or use `/schedule` in Claude Code when it is available for your account.

<Note>
  Claude Code routines are in research preview. Review the first few runs before you rely on them.
</Note>

Learn more in the [Claude Code routines docs](https://code.claude.com/docs/en/routines).

## Use Codex

In Codex, make the workflow durable with three pieces:

* **MCP**: connect OpenRush so Codex can call the data tools.
* **AGENTS.md**: save your working rules, voice, output format, and review checklist.
* **Automations**: schedule recurring checks when the task is stable.

A simple `AGENTS.md` section can be enough:

```md theme={null}
## OpenRush marketing workflow

- Use OpenRush for fresh search, keyword, competitor, SERP, and website data.
- Write for marketers and founders.
- Keep answers short, concrete, and action-oriented.
- Separate facts from recommendations.
- Do not claim a trend changed unless OpenRush data supports it.
```

Use Codex automations for repeatable checks, such as a weekly competitor brief or a monthly site audit. Test the prompt manually first, then schedule it once the output is reliable.

Learn more in the [Codex automations docs](https://developers.openai.com/codex/app/automations) and [AGENTS.md docs](https://developers.openai.com/codex/guides/agents-md).

## Schedule useful marketing tasks

Scheduled tasks work best when the job has a clear cadence and a clear output. Use Claude Code routines or Codex automations depending on where you already work.

| Schedule       | Task                                           | Output                                   |
| -------------- | ---------------------------------------------- | ---------------------------------------- |
| Every Monday   | Compare our domain with top search competitors | Short growth brief                       |
| Every weekday  | Inspect one important keyword or SERP          | What changed and why it matters          |
| Every Friday   | Find keyword gaps against competitors          | Prioritized content ideas                |
| Monthly        | Audit the site                                 | Fix list for marketing and website teams |
| After a launch | Inspect our product and category keywords      | Launch visibility report                 |

## Prompt templates

### Weekly competitor brief

```md theme={null}
Every Monday, use OpenRush to review {domain}.

Find the main search competitors, the strongest pages, important keyword gaps, and any obvious organic growth opportunities.

Return:
- 5-line executive summary
- top 3 competitor moves
- top 5 keyword opportunities
- 3 recommended actions for this week

Only report changes or claims supported by OpenRush data.
```

### Keyword gap queue

```md theme={null}
Use OpenRush to compare {domain} with {competitor_1}, {competitor_2}, and {competitor_3}.

Find keywords competitors rank for where we are missing or weak.

Return a prioritized list with:
- keyword or topic
- why it matters
- suggested page type
- difficulty or confidence if available
- next action for a marketer
```

### Website audit

```md theme={null}
Use OpenRush to audit {domain}.

Focus on issues that affect organic growth, content clarity, and search visibility.

Return:
- what is working
- what is weak
- the 5 fixes with the highest expected impact
- what to check again next month
```

## Best practices

* Start with one narrow job.
* Test manually before scheduling.
* Keep the output format the same every time.
* Ask for a short answer first, then drill into details.
* Review the first few scheduled runs before trusting the workflow.
* Keep credit usage in mind. Recurring jobs use the same OpenRush account credits as normal MCP and API calls.

<Note>
  OpenRush provides the marketing data. Your AI client controls agent setup, memory, scheduling, and permissions.
</Note>