mirror of
https://github.com/fabro-sh/fabro.git
synced 2026-09-14 23:22:51 +00:00
4ce57f8aae
Follow-up cleanup on the profile-builder refactor. AgentProfileBuilder::build now borrows instead of consuming, removing the builder.clone().build() dance at all seven call sites. Deletes with_command_timeouts, which had no caller but its own test, and the with_summarizer constructors on all three profiles, whose only remaining caller was each profile's own new(). Replaces the fifth copy of the profile-kind match (guardrails.rs) with the builder, and swaps the parity matrix's hand-maintained provider list for Catalog::effective_agent_profile so a new catalog provider cannot silently skip the matrix. Collapses web_search_provider_test! into a secrets = arm on provider_test! and uses EnvVars::BRAVE_SEARCH_API_KEY over a literal. Drops the Brave key from the Ask Fabro session: AskFabroToolAccessPolicy denies web_search, and both tools() and the prompt are filtered through that policy, so the vault read only registered an uncallable tool. Makes NativeToolOptions::for_profile match exhaustively so a new profile kind must state its timeout, restores Anthropic's borrowed prompt sections and Gemini's static prompt (placeholder substitution rather than format! over 110 lines with doubled braces), and introduces WEB_SEARCH_TOOL_NAME for the registry lookups that keep tool availability and prompt guidance in sync. Updates the product docs, which still described web_search as always registered and as erroring at call time when unconfigured. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
93 lines
3.7 KiB
Text
93 lines
3.7 KiB
Text
---
|
|
title: "Brave Search"
|
|
description: "Give Fabro agents web search capabilities via the Brave Search API"
|
|
---
|
|
|
|
Fabro's [`web_search`](/agents/tools#web_search) tool lets agents search the web during workflow execution. It uses the [Brave Search API](https://brave.com/search/api/) to return titles, URLs, and descriptions for any query. Setting the API key is the only configuration needed — the tool is then registered for all provider profiles (Anthropic, OpenAI, Gemini). Without a key the tool is not registered at all, so agents are never offered a search tool they cannot use.
|
|
|
|
## Setup
|
|
|
|
1. Get a Brave Search API key from the [Brave Search API dashboard](https://brave.com/search/api/)
|
|
|
|
2. Store it on the Fabro server:
|
|
|
|
```bash
|
|
fabro secret set BRAVE_SEARCH_API_KEY BSA...
|
|
```
|
|
|
|
3. Verify the key is working:
|
|
|
|
```bash
|
|
fabro doctor
|
|
```
|
|
|
|
The doctor output should show **Brave Search** as "connected". If the key is missing, web search is reported as a warning — workflows still run, but the `web_search` tool is omitted from the agent's tool set and its system prompt, so agents fall back to other tools.
|
|
|
|
The Fabro server reads this key from the vault only. It does not read `BRAVE_SEARCH_API_KEY` from process env or `server.env`.
|
|
|
|
## How it works
|
|
|
|
Agents call the `web_search` tool with a query string. Fabro sends the query to the Brave Web Search API (`/res/v1/web/search`) and returns numbered results with title, URL, and description:
|
|
|
|
```
|
|
1. Rust Lang
|
|
https://rust-lang.org
|
|
A systems language
|
|
|
|
2. Rust Book
|
|
https://doc.rust-lang.org/book
|
|
The Rust book
|
|
```
|
|
|
|
If `BRAVE_SEARCH_API_KEY` is not configured in the vault, the tool returns an error explaining that the key is required. The agent can then fall back to other approaches.
|
|
|
|
See the [`web_search` tool reference](/agents/tools#web_search) for parameters and details.
|
|
|
|
## Permissions
|
|
|
|
`web_search` is classified as a `shell` category tool, requiring the `full` [permission level](/agents/permissions) for auto-approval. At lower permission levels:
|
|
|
|
- **Interactive mode** — the user is prompted to approve each call
|
|
- **Non-interactive mode** (`--auto-approve`) — calls are denied
|
|
|
|
## Example workflow
|
|
|
|
A workflow that researches a topic before writing about it:
|
|
|
|
<Frame>
|
|
<img src="/images/brave-search-research.svg" alt="Research workflow: Start → Research → Summarize → Exit" />
|
|
</Frame>
|
|
|
|
```dot title="research.fabro"
|
|
digraph Research {
|
|
graph [goal="Research and summarize a topic"]
|
|
rankdir=LR
|
|
|
|
start [shape=Mdiamond, label="Start"]
|
|
exit [shape=Msquare, label="Exit"]
|
|
|
|
research [label="Research", prompt="Use web_search to find recent information about {{ goal }}. Save your findings to research.md."]
|
|
summarize [label="Summarize", shape=tab, prompt="Read research.md and write a concise summary of the key findings."]
|
|
|
|
start -> research -> summarize -> exit
|
|
}
|
|
```
|
|
|
|
## Troubleshooting
|
|
|
|
**"BRAVE_SEARCH_API_KEY is not configured"** — Add the key with `fabro secret set BRAVE_SEARCH_API_KEY <key>`. Run `fabro doctor` to verify.
|
|
|
|
**"Brave Search API returned status 401"** — The API key is invalid or expired. Generate a new key from the [Brave Search API dashboard](https://brave.com/search/api/).
|
|
|
|
**"Brave Search API returned status 429"** — Rate limit exceeded. The Brave Search free tier has usage limits. Upgrade your plan or reduce the frequency of `web_search` calls.
|
|
|
|
## Further reading
|
|
|
|
<Columns cols={2}>
|
|
<Card title="Tools" icon="wrench" href="/agents/tools#web_search">
|
|
Full `web_search` tool reference — parameters, output format, and error handling.
|
|
</Card>
|
|
<Card title="Permissions" icon="lock" href="/agents/permissions">
|
|
How tool permissions control web search access.
|
|
</Card>
|
|
</Columns>
|