GitHub Search

RAG search within GitHub repositories (code and docs).

What it does

Searches GitHub for repositories, code, issues or users. Mostly of use to technical projects — an agent watching a dependency, or researching how something is done.

What you need

Personal access token from GitHub. GitHub → Settings → Developer settings → Personal access tokens. Read-only scopes are enough; this tool only searches.

Connecting it

Credentials belong to one project, not to your workspace and not to you. A system built for one client never runs on another client's account, and a package handed to a business runs on theirs.

1. Open the project and stay on the Visual Editor tab.
2. Open the Tools & Integrations rail on the right.
3. Find this tool, open it, and paste the credential.

To change it later, open the same panel — you can leave the key blank to keep the stored one and change only the other field.

Using it in a step

An Action step runs one tool with the arguments you type, exactly as written, with no model involved — so it costs nothing per run and behaves the same every time. Add one from the canvas toolbar, choose GitHub Search, and fill in:

Values can carry results forward: {{previous}} is the step before, and {{row:column}} is a column from the row this run is about when the trigger fans out.

Press Try it to run the step on its own before committing to a whole sequence.

Using it with an agent

Tick GitHub Search on any agent that should be able to call it, and the agent decides when to. Use an agent when the judgement matters and an Action step when the certainty does.

A worked example

An agent watches a client's open-source dependency for new issues mentioning a security fix, and raises anything that appears.

When it goes wrong

Rate limited without a token. Connect a GitHub key on the project; unauthenticated search is throttled hard.

See also

• Action steps — the step kind this is used in
• Sequences — how steps fit together
• Triggers — running it on a schedule