A Crystal Code plugin that gives the agent live web search and page fetch.
This is a disk plugin for Crystal Code. websearch queries one of several hosted search backends and returns ranked, model-ready results; webfetch reads one HTTP or HTTPS page and converts it to text, Markdown, or raw HTML. Use /web to inspect the selected provider and /web provider <name> to change it immediately. Both tools remain available in Plan and Work, and network calls are classified as Network authority by the host approval policy.
Features · Tools · Configuration · Build from source
- Search the live web.
websearchuses Parallel by default and can be switched to Exa, Tavily, Bocha, Perplexity, Jina, or Firecrawl. Parallel and Exa work anonymously; the other providers require an API key. - Readable results. Structured payloads are normalized into
Title,URL,Published, andHighlightsblocks; text from Exa and Jina passes through unchanged. - Model-controlled volume.
numResultsapplies to Exa, Tavily, Bocha, Perplexity, Jina, and Firecrawl; Parallel uses its server-side default.contextMaxCharacterssteers the Exa engine, andmaxCharacterscaps the returned text for every backend with a truncation note. - Read specific pages.
webfetchperforms one HTTP GET, rejects non-text content, retries a Cloudflare challenge once, and converts HTML to plain text or Markdown. - Stay bounded. Search responses are capped at 512 KiB and pages at 5 MiB. Search has a 25-second request timeout;
webfetchhonors its model-visibletimeout. The host per-call timeout still applies. - Keep credentials out of commands and logs. The manifest and tool arguments never carry secrets. Provider keys are read from
web.jsonor the process environment and never written to output or logs. A missing required key fails before any network request. - Fit the plugin contract. The plugin joins Plan and Work and contributes
websearch,webfetch,/web, and Network approval classification.
| Tool | What it does |
|---|---|
websearch |
Search the live web through Parallel (default), Exa, Tavily, Bocha, Perplexity, Jina, or Firecrawl and return ranked results as text |
webfetch |
Fetch one http(s) page as Markdown (default), plain text, or raw HTML |
| Argument | Default | Meaning |
|---|---|---|
query |
Required | The web search query |
numResults |
8 (1–20) | Requested number of search results; providers may return fewer. Parallel uses its own default |
contextMaxCharacters |
10000 (1–50000) | Context size the search engine returns; currently honored by Exa |
type |
auto |
Search effort: auto, fast, or deep; Exa and Tavily honor all three, Perplexity honors fast only (deep uses standard web search), and other providers ignore it |
livecrawl |
fallback |
Exa live crawl: fallback or preferred; other providers ignore it |
session_id |
None | Stable conversation id reused across related Parallel calls; other providers ignore it |
model_name |
None | Exact model identifier for Parallel product analytics only; other providers ignore it |
maxCharacters |
None (1–100000) | Cap on the returned text; the tool truncates and notes it |
| Argument | Default | Meaning |
|---|---|---|
url |
Required | The http or https URL to fetch; credentials in the URL are rejected |
format |
markdown |
Returned representation: text, markdown, or html |
timeout |
30 (1–120) | Request timeout in seconds |
maxCharacters |
None (1–100000) | Cap on the returned page text; the tool truncates and notes it |
| Variable | Required | Purpose |
|---|---|---|
PARALLEL_API_KEY |
No | Parallel credential; anonymous use works within free-tier limits |
EXA_API_KEY |
No | Exa credential; anonymous use works within free-tier limits |
TAVILY_API_KEY |
No | Overrides the stored Tavily credential |
BOCHA_API_KEY |
No | Overrides the stored Bocha credential |
PERPLEXITY_API_KEY |
No | Overrides the stored Perplexity credential |
JINA_API_KEY |
No | Overrides the stored Jina credential |
FIRECRAWL_API_KEY |
No | Overrides the stored Firecrawl credential |
CRYSTAL_EXA_MCP_URL |
No | Overrides the Exa endpoint; defaults to https://mcp.exa.ai/mcp |
CRYSTAL_PARALLEL_MCP_URL |
No | Overrides the Parallel endpoint; defaults to https://search.parallel.ai/mcp |
CRYSTAL_TAVILY_SEARCH_URL |
No | Overrides the Tavily endpoint; defaults to https://api.tavily.com/search |
CRYSTAL_BOCHA_SEARCH_URL |
No | Overrides the Bocha endpoint; defaults to https://api.bocha.cn/v1/web-search |
CRYSTAL_PERPLEXITY_SEARCH_URL |
No | Overrides the Perplexity endpoint; defaults to https://api.perplexity.ai/search |
CRYSTAL_JINA_MCP_URL |
No | Overrides the Jina endpoint; defaults to https://mcp.jina.ai/v1 |
CRYSTAL_FIRECRAWL_SEARCH_URL |
No | Overrides the Firecrawl endpoint; defaults to https://api.firecrawl.dev/v2/search |
Keyed providers validate their key before sending a request. Jina's search_web and Firecrawl's search endpoint both require a key; their free tiers are quota-based rather than anonymous. Provider selection and API keys are read from web.json under the resolved Crystal Home directory, including any --home override. Environment API-key variables override the stored value. Keep this file private and never commit it.
{
"provider": "tavily",
"apiKeys": {
"tavily": "your-api-key-here",
"exa": "your-api-key-here"
}
}Publish the plugin and place all published files, including plugin.json, in one directory under ~/.crystal/plugins:
dotnet publish CrystalCode.Web/CrystalCode.Web.csproj -c Release -o ~/.crystal/plugins/webRestart the session, or run /plugins reload, to load the plugin. A project plugin at <workspace>/.crystal/plugins/web/ replaces the home plugin for that workspace. The directory name is the plugin identity; this plugin installs as web.
You need the .NET 10 SDK, a sibling checkout of Crystal at ../Crystal, and a CrystalCode checkout at ../CrystalCode for the plugin contract project reference.
dotnet build CrystalCode.Web.sln
dotnet test CrystalCode.Web.sln
dotnet publish CrystalCode.Web/CrystalCode.Web.csprojCrystal.Tools and CrystalCode.Plugins are referenced as sibling source projects. The production project adds no NuGet packages; the test project uses xUnit and Microsoft.NET.Test.Sdk only. The host loads the assembly described by plugin.json in one isolated load context. Search and fetch calls use the host's approval policy, output truncation, and timeout.