Conversation
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (6)
🚧 Files skipped from review as they are similar to previous changes (1)
Included review availability: Your plan provides up to 10 included reviews per hour; 8 remain after this review. 📝 WalkthroughWalkthroughThis PR adds a ChangesBaizhi research example
Priority: ⬇️ Low Estimated code review effort: 3 (Moderate) | ~25 minutes Change: Feature Sequence Diagram(s)sequenceDiagram
participant CLI as src/index.ts
participant Session as openResearchSession
participant MCP as Baizhi MCP service
participant Agent as VoltAgent Agent
CLI->>Session: Open session with API key and AbortSignal
Session->>MCP: Connect with Bearer authentication
MCP-->>Session: Discover research tools
CLI->>Agent: Generate answer with session tools
Agent->>Session: Call research tool
Session->>MCP: Forward validated request
MCP-->>Session: Return redacted result
Agent-->>CLI: Return research answer
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
All reported issues were addressed across 10 files
Reply with feedback, questions, or to request a fix.
Re-trigger cubic
What is the current behavior?
Existing MCP examples show how to connect an agent to tools. This example adds a complete public-web research question: search candidate sources, read the relevant pages, and extract fields for a cited comparison.
What is the new behavior?
Adds
examples/with-baizhi-research, a one-shot VoltAgent CLI using Baizhi's hosted MCP service over Streamable HTTP. The example discovers tool names but exposes onlywebsearch_search,web_scrapeandweb_extract, with explicit schemas, six shared tool-call attempts, cancellation, request/run deadlines and connection cleanup. Discovery stops once the three required tools are found; a missing-tool result and the ten-page limit have distinct safe errors. The CLI distinguishes cancellation and run timeout. API-key echoes are replaced in output; raw remote errors are not logged or returned to the model.Baizhi is a paid external tool service, not an LLM provider. Users provide both Baizhi and OpenAI credentials. The README documents data flow, usage charges, public-source restrictions and the limits of these controls. No service backend, released framework package, model provider or registry listing is added.
Validation
--env-file. Example TypeScript build and test-source typecheck pass against published package dependencies.tools/listconfirmed the three names/input shapes. No paid tool invocation or live LLM answer is claimed by this validation.Notes for reviewers
Prepared with AI assistance as part of the Baizhi Agent Toolkit outreach effort. The official MCP SDK wrapper makes per-operation cancellation and the shared tool budget explicit without changing framework APIs. Tests need no credentials. This private example is ignored by
.changeset/config.json(voltagent-example-*), so no released-package changeset is included.Related scope proposal: #1419. The contribution guide recommends opening an issue first; this PR provides the concrete example for review. Maintainer scope acceptance is still pending.
PR Checklist