PicoClaw
PicoClaw tests keyless MCP search paths beside provider demand
PicoClaw contributors added copy-paste setup proposals for Parallel Search and Pilot MCP while users continue asking for broader OpenAI-compatible providers. The strongest proposal discloses vendor affiliation, benchmarks the external service cautiously and leaves Sogou as the default pending project-specific tests.
sipeed/picoclaw PR #3368 is the inspected primary source: “docs: add Parallel Search MCP setup example.” The related records were inspected as supporting context rather than independent confirmation.
The facts
- sipeed/picoclaw PR #3368 was created 2026-09-05T00:22:25Z and was open at inspection; its title is “docs: add Parallel Search MCP setup example.” - sipeed/picoclaw PR #3367 was created 2026-09-04T21:39:44Z and was open at inspection; its title is “docs: add Pilot MCP setup example.” - sipeed/picoclaw issue #3366 was created 2026-09-04T14:53:51Z and was open at inspection; its title is “[Feature] Add support for OpenAI compatible providers.” - The repository reported 29938 stars, 47 open issues, default branch main, and last push 2026-09-03T17:15:19Z. - The latest tagged-release baseline checked was nightly published 2026-07-02T01:26:53Z.
What changed
sipeed/picoclaw PR #3368 reports: Description This adds a copy-paste setup for Parallel Search MCP to the existing CLI guide. It gives PicoClaw web search and page extraction without a Parallel account or API key, with instructions for removing it and a clear explanation of what gets sent to Parallel. PicoClaw enables Sogou by default for its built-in search, though provider-native search takes precedence when available. That's the default I'd like to evaluate Parallel against. One reason to try it: Artificial Analysis's August 31 leaderboard gives Parallel Search (fast) **80/100 on DeepSearchQA F1** and **73/100 on its overall Search Index**. Fast is also the mode used by the anonymous MCP connection in this example. These are Search API benchmark results, not a PicoClaw evaluation, and Artificial Analysis doesn't include Sogou, so they don't establish a win over the current default. If better default search results are the goal, I'd suggest testing Parallel against Sogou on PicoClaw's own tasks and considering it as the default if it wins. This PR makes it easy to try; it only changes the docs and leaves the current default in place. I work at Parallel, which operates this service. Type of Change [x] Documentation update AI Code Generation [x] Fully AI-generated (100% AI, 0% Human) Related Issue None. This adds an example to the existing setup guide. Technical Context (Skip for Docs) Parallel
sipeed/picoclaw PR #3367 reports: Summary add the Pilot Protocol setup command to the native MCP CLI quick start include the PicoClaw health-check command clarify that setup preserves existing configuration and needs no API key Validation make lint-docs git diff --check AI Code Generation AI-assisted; reviewed and validated by the contributor. Disclosure: I contribute to Pilot Protocol.
sipeed/picoclaw issue #3366 reports: The Goal / Use Case I would like to have custom OpenAI compatible providers. This would allow to add self-hosted routers e.g. 9Router. Proposed Solution Add a custom provider, named "OpenAI Compatible". Potential Implementation (Optional) The provider can be a copy of OpenAI. I'm currently using OpenAI with my 9router endpoint and key and works fine. Impact & Roadmap Alignment [ ] This is a Core Feature [X] This is a Nice-to-Have / Enhancement [ ] This aligns with the current Roadmap Alternatives Considered For now, just the workaround mentioned in the implementation section. Additional Context Can provide if any!
Why it matters
Small-agent projects need pluggable discovery without turning vendor examples into unearned defaults. Keyless setup lowers trial friction, but transport, data disclosure and comparative quality still need explicit tests. The practical test is whether the system remains bounded and its receipts still describe the action after failure, retry or restart.
Current
The primary record was open when captured on 2026-09-05. The tagged-release baseline was nightly published 2026-07-02T01:26:53Z. Repository metadata, source bodies, current pull requests and issues, releases, Google News, Hacker News, Lobsters, Metamesh and the rendered ClawCharts row were inspected. ClawCharts selected the subject; it did not prove the claim.
Evidence
The primary URL is https://github.com/sipeed/picoclaw/pull/3368. Supporting records are https://github.com/sipeed/picoclaw/pull/3367 and https://github.com/sipeed/picoclaw/issues/3366. Source bodies, timestamps and states are preserved in the daily evidence bundle. Test counts and reproductions remain attributed to their authors unless identified as independently rerun.
Source boundary
Open work is described as open, closed work as closed, and operator reports as reports. A pull request is evidence of proposed or reviewed direction, not proof of a shipped release. Search residue, package mirrors and historically published source spines were excluded.
Operator take
Treat the additions as inspectable setup recipes, retain removal and health-check commands, compare search providers on PicoClaw tasks, and keep vendor benchmark claims separate from an in-project evaluation. Preserve a before-state receipt, make the smallest reversible change, and verify the original failure independently.
Caveat
Public project records are mutable. Status, scope and evidence can change after publication. This brief records the inspected state and does not authorize changes to a reader’s deployment.
Source inspected; source state, environment and release boundary remain explicit.