How to Use Relace Search in OpenClaw
Relace Search finds the code needed to investigate bugs or plan changes. It follows multiple search paths and returns relevant code sections for a coding agent to use.
Prompts to try with Relace Search in OpenClaw
Copy an example into OpenClaw, or ask in your own words.
Each morning, use Relace Search to investigate each new login issue using its supplied code excerpts. Return the relevant sections, supporting evidence, and unanswered questions.
For each incoming checkout incident, use Relace Search to identify relevant branches in the code excerpts included with the incident. Produce a short investigation brief without claiming a fix.
Each weekday, use Relace Search to examine the code excerpts attached to new feature requests. Identify existing behavior that the implementing developer should understand.
For each new failing-test report, use Relace Search to compare the stated expectation with the supplied implementation and test excerpts. Point to the sections that explain the mismatch.
Every Friday, use Relace Search to review this week's edge-case reports and their supplied code excerpts. For each report, identify the relevant conditions and any missing evidence.
How to set up Relace Search in OpenClaw
Pick the way that suits you. Each takes about two minutes.
Use the Spiral skill
- Send OpenClaw this message
Your agent reads Spiral's skill and sets itself up.
set up https://spiral.ai/SKILL.md
- Sign in or paste a key
Approve Spiral in the browser, or give the agent a key from the console.
Use Spiral's MCP server
- Add the server
On the machine that runs OpenClaw's Gateway:
openclaw mcp add spiral \ --url https://api.spiral.ai/mcp \ --transport streamable-http \ --auth oauth
- Sign in
In Settings › MCP, select Sign in on the Spiral server, sign in to Spiral and click Authorize. No API key.
openclaw mcp login spiral
- Reload and check
A running Gateway may keep its old tool list: restart it, or Save & Publish in the Control UI.
openclaw mcp reload openclaw mcp doctor spiral --probe
Use the Spiral CLI
- Install and sign in
Installs the Spiral CLI, signs you in and adds its skill to your coding agents.
npx -y spiral-cli@latest init
Call the Spiral API
- Create an API key
In the console, under API keys.
- Run Relace Search
One request; the result comes back by polling or a webhook.
curl https://api.spiral.ai/v1/runs \ -H "Authorization: Bearer $SPIRAL_API_KEY" \ -H "Content-Type: application/json" \ -H "Idempotency-Key: $(uuidgen)" \ -d '{ "provider": "openrouter", "model": "relace/relace-search", "input": { "messages": [ { "role": "system" } ] } }'
Then paste one of the prompts above: OpenClaw finds Relace Search on Spiral, shows the price and runs it.
Relace Search providers and prices
Spiral runs Relace Search through OpenRouter. Open a card for today's price, with every fee included.
Up to $0.01602 per run at the default inputs. $1.30 per 1M input tokens, $3.90 per 1M output tokens.
Settings you can ask for
Ask OpenClaw for any of these in your prompt.
| Setting | Allowed values | Default | Description |
|---|---|---|---|
| Seed | a whole number | ||
| Top p | 0 to 1 | ||
| Max tokens | 1 to 128000 | The most output tokens to generate. | |
| Temperature | 0 to 2 |
Every API field of Relace: Relace Search is on its tool page: open its card above.
What can you do with Relace Search in OpenClaw?
Prepare recurring investigation briefs from incoming issue descriptions and supplied code context. Use Relace Search to select supporting sections and flag gaps for a developer to resolve.
Find a bug's likely entry points
Use Relace Search to locate the code associated with a reported symptom and collect the sections worth investigating first.
Trace authentication behavior
Ask Relace Search to follow authentication checks and identify the code that accepts or rejects a request.
Scope a feature change
Use Relace Search to identify existing behavior and the code a developer should understand before adding a feature.
Investigate an edge case
Ask Relace Search to trace empty inputs, missing values, or boundary conditions and report the relevant branches.
Prepare a refactor
Use Relace Search to follow related code paths and collect the context needed to assess a proposed refactor.
Build an implementation handoff
Ask Relace Search for a focused collection of relevant code sections, with reasons for including each one, before assigning implementation.
More on Relace Search and OpenClaw
Overview
Relace Search in other agents
Questions about Relace Search in OpenClaw
Can OpenClaw use Relace Search?
Yes. Add Spiral to OpenClaw as an MCP server, and OpenClaw can find and run Relace Search like any built-in tool.
How much does Relace Search cost in OpenClaw?
Up to $0.01602 per run at the default inputs. $1.30 per 1M input tokens, $3.90 per 1M output tokens. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your OpenClaw plan is separate.
Do I need an OpenRouter account to use Relace Search in OpenClaw?
No. Spiral runs Relace Search on its own OpenRouter account. You sign in to Spiral once and never paste a key.
How long does it take to set up Relace Search in OpenClaw?
About two minutes: add the server, then sign in, then reload and check.
Does OpenClaw wait while Relace Search runs?
Relace Search runs in the background. OpenClaw starts the run, checks on it and gives you the text, json when it's ready.
What is Relace Search best for?
Finding the code relevant to a bug report, behavior question, or proposed change. It gathers context that a coding agent can use for implementation.
Does Relace Search fix the code it finds?
Its documented role is to investigate and report relevant code. Treat the report as the starting point for implementation and testing.
What does a search result contain?
The documented report identifies relevant files and line ranges. Ask for an explanation of why each section matters to your question.
How much context can Relace Search handle?
The context window is 256,000 tokens, with up to 128,000 completion tokens. For an investigation, ask for the relevant sections and a short explanation.
How should I phrase a code investigation?
Describe the behavior you want to understand, including expected results and edge cases. Ask the model to trace the control flow and explain the evidence behind its findings.
Start using Relace Search in OpenClaw
One Spiral account for every tool your agent needs. No subscription; you pay per run.
Paste this into OpenClaw:
set up https://spiral.ai/SKILL.md


