Would public documentation search fit the native ChatAgent agents? They can already execute registered capabilities and consume their results, but have no built-in public web search. This could help look up framework and API documentation during authorized assessments.
I'd add search and page-fetch capabilities using Parallel Search MCP, with free search powered by Fast mode and no account or API key required. Parallel would be the default search provider when none is configured, with a setting to disable external lookup for isolated runs. Explicitly registered tools and target HTTP behavior would be preserved. Queries and URLs go to an external service, so private target data and credentials should stay out of them, and retrieved content should be treated as untrusted.
I'd test dispatch through the existing capability registry and agent history, configuration overrides, disabled lookup, timeouts, cancellation, errors, and per-run search identity before a PR.
I work at Parallel.
Activity
0No activity yet.