Skip to content

docs: add FAQ section#1280

Open
meichuanyi wants to merge 2 commits into
VoltAgent:mainfrom
meichuanyi:docs/add-faq-section
Open

docs: add FAQ section#1280
meichuanyi wants to merge 2 commits into
VoltAgent:mainfrom
meichuanyi:docs/add-faq-section

Conversation

@meichuanyi
Copy link
Copy Markdown

@meichuanyi meichuanyi commented May 13, 2026

Summary

This PR adds a comprehensive FAQ section to the README.md, addressing common questions users may have about VoltAgent.

Changes

Added ❓ FAQ section covering:

  • Platform Overview: What is VoltAgent (framework + VoltOps Console)
  • Framework Comparison: How VoltAgent differs from LangChain/CrewAI (TypeScript-first, built-in observability, declarative workflows)
  • Installation: Quick start with npm create voltagent-app@latest
  • LLM Providers: All major providers (OpenAI/Anthropic/Google/Groq) via AI SDK
  • Multi-Agent Systems: Supervisor + Sub-Agents architecture
  • Custom Tools: How to register tools with @voltagent/core
  • MCP Support: Model Context Protocol integration
  • Memory: Durable adapters (LibSQL/In-Memory)
  • VoltOps Console: Production operations platform (observability/automation/deployment)
  • RAG: Built-in retrieval capabilities
  • Voice: TTS/STT support
  • Evals: Evaluation system
  • Guardrails: Input/output validation
  • Standalone Usage: Core framework without VoltOps Console
  • Help Resources: Documentation/Discord/Issues/Twitter

Motivation

VoltAgent README lacks a FAQ section, which is valuable for:

  • New users to understand the platform quickly
  • Answering common questions without searching documentation
  • Improving project accessibility and friendliness

Checklist

  • FAQ content is accurate and helpful
  • Markdown formatting is correct
  • Links are valid and working
  • Questions reflect real user needs

Related

Addresses a common documentation gap for AI agent frameworks.


Thanks for reviewing! 🚀


Summary by cubic

Adds a FAQ section to the README to answer common VoltAgent questions and help new users get started quickly.

  • New Features
    • Overview and framework comparison.
    • Install: npm create voltagent-app@latest.
    • Provider support via AI SDK; multi‑agent supervisors/sub‑agents; custom tools with @voltagent/core and MCP.
    • Core capabilities: memory adapters, RAG, voice, evals, guardrails.
    • Ops and support: VoltOps Console and links to docs/Discord/issues/Twitter.

Written for commit 4c6a6a3. Summary will update on new commits.

Summary by CodeRabbit

  • Documentation
    • Added a comprehensive FAQ section to the README addressing common questions about VoltAgent, including features, installation, supported LLM providers, custom tools, MCP support, memory behavior, VoltOps Console capabilities, RAG usage, voice support, evaluations, guardrails, and troubleshooting resources.

Review Change Stack

@changeset-bot
Copy link
Copy Markdown

changeset-bot Bot commented May 13, 2026

⚠️ No Changeset found

Latest commit: 4c6a6a3

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 13, 2026

📝 Walkthrough

Walkthrough

A comprehensive FAQ section was added to the README documenting VoltAgent's features, setup, capabilities, and how it compares to other frameworks like LangChain and CrewAI. The section addresses installation, supported providers, tools, MCP, memory, RAG, voice, evaluations, guardrails, and VoltOps Console integration.

Changes

FAQ Documentation

Layer / File(s) Summary
FAQ section
README.md
FAQ section added with 20+ subsections answering common questions about VoltAgent architecture, setup, framework comparisons, feature support, and console capabilities.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

  • VoltAgent/voltagent#923: Documentation-only PR modifying README.md structure with new content blocks, similar non-code update pattern.

Poem

A fuzzy friend hops through the docs so bright,
With FAQ's answers, everything feels right,
No code was changed, just knowledge to share,
VoltAgent's guide blooms with helpful care! 📚✨

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and concisely describes the main change: adding a FAQ section to documentation.
Description check ✅ Passed The description is comprehensive, covering what was added, why it matters, and includes a detailed checklist; however, it lacks linked issues and changeset information required by the template.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@README.md`:
- Around line 376-384: The comparison table currently misstates LangChain and
CrewAI capabilities: update the LangChain row (the "Sequential chains" and
"External tools" cells) to reflect stateful, graph-based workflows and agent
patterns (e.g., LangGraph) and to list LangSmith as built-in observability with
tracing/monitoring/dashboards/alerts; update the CrewAI row (the "Role-playing
teams" and "Limited" observability cells) to reflect Flows'
`@start/`@listen/@router multi-step pipelines and built-in AMP observability with
OpenTelemetry tracing and performance metrics while keeping CrewAI's "No" for
Voice Support; also ensure the second table instance noted (lines ~395-400)
receives the same corrections and keep the model examples line current (gpt-5.x,
claude-sonnet-4-6, gemini-2.5/3.x, llama-3.3-70b).
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 23fdb71b-c871-4c9d-9170-f6a2f79a7395

📥 Commits

Reviewing files that changed from the base of the PR and between 08414ed and 4c6a6a3.

📒 Files selected for processing (1)
  • README.md

Comment thread README.md
Comment on lines +376 to +384
| Feature | VoltAgent | LangChain | CrewAI |
|---------|-----------|-----------|--------|
| **Architecture** | TypeScript-first | Python-first | Python-first |
| **Workflow Engine** | Declarative workflows | Sequential chains | Role-playing teams |
| **Memory** | Multiple adapters | In-memory + options | Shared memory |
| **Observability** | Built-in VoltOps Console | External tools | Limited |
| **Deployment** | One-click cloud | Manual setup | Manual setup |
| **Voice Support** | Built-in TTS/STT | External providers | No |

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major | ⚡ Quick win

🧩 Analysis chain

🌐 Web query:

Verify current public docs for LangChain and CrewAI feature support (workflow model, observability, voice) and confirm listed model examples for OpenAI/Anthropic/Google/Groq are still accurate as of May 2026.

💡 Result:

LangChain and CrewAI both support workflow models, observability, and voice features as of May 2026, per their official docs. Listed model examples for OpenAI (e.g., gpt-5.x), Anthropic (e.g., claude-sonnet-4-6), Google (e.g., gemini-2.5/3.x), and Groq (via langchain-groq integration with models like llama-3.3-70b) remain accurate and current.[1][2][3][4][5] LangChain: - Workflow model: LangGraph enables stateful, graph-based workflows with nodes, edges, persistence, and agent patterns.[6][7][8] - Observability: LangSmith provides tracing, monitoring, dashboards, alerts, feedback, and integrations.[9][10] - Voice: Official docs detail voice agents using STT + LangChain agent + TTS (e.g., AssemblyAI, Cartesia).[11] CrewAI: - Workflow model: Flows with @start, @listen, @router for multi-step pipelines, state management, crews integration.[12][13][14][15] - Observability: Built-in tracing (CrewAI AMP), OpenTelemetry, performance metrics, LangSmith/CrewAI integrations.[16][17] - Voice: No explicit native voice support found in docs; general LLM streaming possible but not voice-specific.[18][19] Model support confirmed via LangChain docs (init_chat_model with provider prefixes) and Groq integration (ChatGroq).[1][2][3][5] CrewAI inherits via LLM flexibility (e.g., OpenAI/gpt-4o-mini).[13]

Citations:


Update comparison table with current capabilities; several LangChain and CrewAI claims are now inaccurate.

The table at lines 376-384 understates LangChain and CrewAI capabilities:

  • LangChain "Sequential chains": LangGraph now provides stateful, graph-based workflows with agent patterns, not just sequential execution.
  • LangChain "External tools" (Observability): LangSmith is the official observability platform with tracing, monitoring, dashboards, and alerts—not merely external options.
  • CrewAI "Limited" (Observability): CrewAI AMP provides built-in tracing with OpenTelemetry and performance metrics; this is understated.
  • CrewAI "Role-playing teams" (Workflow Engine): Flows support @start, @listen, @router for multi-step pipelines beyond role-based teams.

CrewAI's "No" for voice support remains accurate. Model examples (gpt-5.x, claude-sonnet-4-6, gemini-2.5/3.x, llama-3.3-70b) are current as of May 2026.

Also applies to: 395-400

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@README.md` around lines 376 - 384, The comparison table currently misstates
LangChain and CrewAI capabilities: update the LangChain row (the "Sequential
chains" and "External tools" cells) to reflect stateful, graph-based workflows
and agent patterns (e.g., LangGraph) and to list LangSmith as built-in
observability with tracing/monitoring/dashboards/alerts; update the CrewAI row
(the "Role-playing teams" and "Limited" observability cells) to reflect Flows'
`@start/`@listen/@router multi-step pipelines and built-in AMP observability with
OpenTelemetry tracing and performance metrics while keeping CrewAI's "No" for
Voice Support; also ensure the second table instance noted (lines ~395-400)
receives the same corrections and keep the model examples line current (gpt-5.x,
claude-sonnet-4-6, gemini-2.5/3.x, llama-3.3-70b).

Copy link
Copy Markdown
Contributor

@cubic-dev-ai cubic-dev-ai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

1 issue found across 1 file

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="README.md">

<violation number="1" location="README.md:381">
P2: The comparison table contains inaccurate characterizations of competitor capabilities:
- LangChain's workflow engine is not just "Sequential chains" — LangGraph provides stateful, graph-based workflows with agent patterns.
- LangChain's observability is not "External tools" — LangSmith is their official built-in observability platform with tracing, monitoring, and dashboards.
- CrewAI's observability is not "Limited" — CrewAI AMP provides built-in tracing with OpenTelemetry and performance metrics.
- CrewAI's workflow engine is not just "Role-playing teams" — Flows support `@start`, `@listen`, `@router` for multi-step pipelines.

Publishing misleading comparisons undermines credibility. Consider updating to reflect current capabilities accurately.</violation>
</file>

Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.

Comment thread README.md
| **Architecture** | TypeScript-first | Python-first | Python-first |
| **Workflow Engine** | Declarative workflows | Sequential chains | Role-playing teams |
| **Memory** | Multiple adapters | In-memory + options | Shared memory |
| **Observability** | Built-in VoltOps Console | External tools | Limited |
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2: The comparison table contains inaccurate characterizations of competitor capabilities:

  • LangChain's workflow engine is not just "Sequential chains" — LangGraph provides stateful, graph-based workflows with agent patterns.
  • LangChain's observability is not "External tools" — LangSmith is their official built-in observability platform with tracing, monitoring, and dashboards.
  • CrewAI's observability is not "Limited" — CrewAI AMP provides built-in tracing with OpenTelemetry and performance metrics.
  • CrewAI's workflow engine is not just "Role-playing teams" — Flows support @start, @listen, @router for multi-step pipelines.

Publishing misleading comparisons undermines credibility. Consider updating to reflect current capabilities accurately.

Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At README.md, line 381:

<comment>The comparison table contains inaccurate characterizations of competitor capabilities:
- LangChain's workflow engine is not just "Sequential chains" — LangGraph provides stateful, graph-based workflows with agent patterns.
- LangChain's observability is not "External tools" — LangSmith is their official built-in observability platform with tracing, monitoring, and dashboards.
- CrewAI's observability is not "Limited" — CrewAI AMP provides built-in tracing with OpenTelemetry and performance metrics.
- CrewAI's workflow engine is not just "Role-playing teams" — Flows support `@start`, `@listen`, `@router` for multi-step pipelines.

Publishing misleading comparisons undermines credibility. Consider updating to reflect current capabilities accurately.</comment>

<file context>
@@ -363,6 +363,157 @@ VoltAgent is a community effort, and it keeps getting better because of people l
+| **Architecture** | TypeScript-first | Python-first | Python-first |
+| **Workflow Engine** | Declarative workflows | Sequential chains | Role-playing teams |
+| **Memory** | Multiple adapters | In-memory + options | Shared memory |
+| **Observability** | Built-in VoltOps Console | External tools | Limited |
+| **Deployment** | One-click cloud | Manual setup | Manual setup |
+| **Voice Support** | Built-in TTS/STT | External providers | No |
</file context>

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants