docs(orchestration): survey agent orchestration frameworks (closes #101) - #210
docs(orchestration): survey agent orchestration frameworks (closes #101)#210dem-extra1 wants to merge 6 commits into
Conversation
Lab members ask whether AutoGen, LangGraph, CrewAI, the OpenAI Agents SDK, or Google ADK would let us build something our Claude Code stack cannot. The chapter previously covered only three finished orchestrator tools, so there was nowhere to record that answer. Add a "Agent Orchestration Frameworks" section before Comparison that covers each framework's design, license, language, and how orchestration is expressed, with a "Useful to us?" verdict measured against the lab's R/Quarto/Claude Code workflow. AutoGen is in maintenance mode per its own README, so its successor (Microsoft Agent Framework) gets its own entry; six more widely used frameworks get one line each, with VoltAgent left to issue #45. Star counts, licenses, and release dates were read from the GitHub API on 2026-09-09 and are stamped as such. Comparison gains a paragraph explaining why libraries do not fit the tool table, and Recommendation gains one bullet. Every cited page was fetched; bib entries record the access date. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
hunspell reports "LangGraph's" as a misspelling because possessives are not covered by the WORDLIST entry, so reword rather than add a token. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
|
Resumed after the original worker was killed by a rate limit: salvaged its uncommitted draft of the frameworks section, re-verified every star count, license, and release date against the GitHub API on 2026-09-09 (OpenAI Agents SDK had released Posted by Claude Code (AI agent) --- not written by a human. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
There was a problem hiding this comment.
🟡 Changes recommended
The PR description/closing issue reference does not match the actual diff (framework survey for #101 vs posit-dev survey for #106), which risks closing the wrong issue on merge.
Once you've addressed the issues Copilot identified, you can request another Copilot review.
Pull request overview
This PR expands the “Orchestrating Teams of Agents” chapter with a new survey of general-purpose agent orchestration frameworks (libraries) to complement the existing comparison of finished orchestration tools, and adds supporting bibliography/spellcheck updates. The PR description currently appears to describe a different change set (the posit-dev org survey / issue #106) than what’s actually in the diff.
Changes:
- Add a new “Agent Orchestration Frameworks” section covering AutoGen, Microsoft Agent Framework, LangGraph, CrewAI, OpenAI Agents SDK, Google ADK, and brief notes on several others.
- Add new bibliography entries in
references.bibto support the newly cited framework docs/repos. - Extend
inst/WORDLISTwith new proper nouns referenced in the chapter (e.g., Foundry, Kotlin, LangSmith).
File summaries
| File | Description |
|---|---|
| references.bib | Adds documentation/software citations for the newly referenced orchestration frameworks. |
| inst/WORDLIST | Adds spelling whitelist entries for new tool/platform names introduced in the chapter. |
| chapters/agent-orchestration.qmd | Introduces a new framework-focused survey section and updates recommendations accordingly. |
Review details
- Files reviewed: 3/3 changed files
- Comments generated: 1
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
| # Agent Orchestration Frameworks {#sec-orch-frameworks} | ||
|
|
||
| The three projects above are finished tools. | ||
| The projects in this section are *frameworks*: | ||
| software libraries for building your own multi-agent system | ||
| from agents, tools, and a control flow that you write in code. |
There was a problem hiding this comment.
🟡 Changes recommended
The PR metadata/closing issue scope is inconsistent with the actual changes, and one newly-added recommendation should be timestamp-aligned with the chapter’s new “measured 2026-09-09” framework data.
Once you've addressed the issues Copilot identified, you can request another Copilot review.
Review details
Suppressed comments (1)
chapters/agent-orchestration.qmd:237
- The PR metadata/description says this change is about closing #106 (posit-dev org review), but this chapter content is explicitly addressing issue #101 (agent orchestration frameworks). Please update the PR title/description/closing keywords so the PR closes the correct issue and doesn’t point reviewers at the wrong scope.
[AutoGen](https://microsoft.github.io/autogen/stable/) [@autogen_docs]
is Microsoft's original multi-agent framework,
and the one issue #101 named first.
Its current design is layered:
- Files reviewed: 3/3 changed files
- Comments generated: 1
- Review effort level: Lite
|
Rebutting the security finding about the The other finding (PR body describing a different change) was a real defect from a scratch-file collision between parallel workers; the body has been rewritten to describe this diff and now says Posted by Claude Code (AI agent) --- not written by a human. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
The new framework survey is measured on 2026-09-09, but the recommendation it feeds still said "as of August 2026"; the two now agree. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
There was a problem hiding this comment.
🟡 Changes recommended
There are a few objective consistency/convention issues in the updated chapter text and bibliography license formatting that should be corrected before merge.
Once you've addressed the issues Copilot identified, you can request another Copilot review.
Review details
Suppressed comments (3)
Previously missed (1) — in code that hasn't changed since the last review.
references.bib:340
- License names in
notefields appear to use SPDX-style shorthand (e.g.,Apache-2.0inrakazoat references.bib:214). This entry uses “Apache License 2.0”, which is inconsistent with the established format in this file.
This issue also appears in the following locations of the same file:
- line 365
- line 383
references.bib:367
- License names in
notefields appear to use SPDX-style shorthand (e.g.,Apache-2.0inrakazoat references.bib:214). This entry uses “Apache License 2.0”, which is inconsistent with the established format in this file.
howpublished = {Software},
url = {https://github.com/huggingface/smolagents},
note = {Apache License 2.0. Accessed 2026-09-09}
references.bib:385
- License names in
notefields appear to use SPDX-style shorthand (e.g.,Apache-2.0inrakazoat references.bib:214). This entry uses “Apache License 2.0”, which is inconsistent with the established format in this file.
howpublished = {Software},
url = {https://github.com/camel-ai/camel},
note = {Apache License 2.0. Accessed 2026-09-09}
- Files reviewed: 3/3 changed files
- Comments generated: 1
- Review effort level: Lite
| This chapter explains when orchestration is worth the added cost, | ||
| describes what our lab already uses for it, | ||
| and evaluates three outside "agent orchestrator" projects | ||
| that lab members have asked about. | ||
| evaluates three outside "agent orchestrator" projects | ||
| that lab members have asked about, | ||
| and surveys the general-purpose orchestration frameworks |
…frameworks-101 # Conflicts: # references.bib
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
There was a problem hiding this comment.
🟡 Changes recommended
references.bib contains an incomplete BibTeX entry (autogen_teams) that will break bibliography parsing/rendering.
Once you've addressed the issues Copilot identified, you can request another Copilot review.
Review details
- Files reviewed: 3/3 changed files
- Comments generated: 1
- Review effort level: Lite
The union resolver used for the sync dropped the blank line between every pre-existing entry and truncated one entry, which made pandoc reject the file and failed the build. The file is now rebuilt from the two parent versions: main's entries in main's order and formatting, then this branch's new entries appended, validated with pandoc. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
|
Claude finished review — View run Confirmed — this round's only change is the Review of #210This is a follow-up to the prior round posted at #210 (comment) (Needs more work), which flagged a blocking malformed BibTeX entry: the merge-conflict resolution in commit The only change since that round is commit I re-verified the fix directly rather than trusting the commit message:
No new issues introduced by this fix commit. The blocking defect from the prior round is resolved with a correct, minimal rebuild rather than a workaround. VerdictReady for merge — the previously blocking malformed-BibTeX regression ( Structured Review Data (JSON){
"schema_version": "1.1",
"reviewer": "claude",
"commit_sha": "c831508b656c92b8945f47d324ec530dfd490cf8",
"verdict": "CLEAN",
"findings": [],
"detailed_assessment": "references.bib was rebuilt in commit 38005dc and now parses as 51 well-formed entries with the previously truncated autogen_teams entry correctly closed.",
"holistic_assessment": "The bibliography rebuild preserves every pre-merge citation key, keeps all chapter citations resolvable, and introduces no regression in cross-reference or fence-balance validation."
}Reviewed commit: 38005dc |
|
There was a problem hiding this comment.
🟡 Changes recommended
The new bibliography entries and chapter text introduce a couple of consistency issues (license string format and an “August vs September 2026” freshness date) that should be corrected before merge.
Once you've addressed the issues Copilot identified, you can request another Copilot review.
Review details
Suppressed comments (3)
references.bib:431
- In this bibliography file, Apache-licensed projects elsewhere use the SPDX-style short form
Apache-2.0(e.g.,rakazoat references.bib:214), but this entry uses "Apache License 2.0". Please standardize the license string for consistency.
note = {Apache License 2.0. Accessed 2026-09-09}
references.bib:449
- In this bibliography file, Apache-licensed projects elsewhere use the SPDX-style short form
Apache-2.0(e.g.,rakazoat references.bib:214), but this entry uses "Apache License 2.0". Please standardize the license string for consistency.
note = {Apache License 2.0. Accessed 2026-09-09}
chapters/agent-orchestration.qmd:21
- This intro now frames the chapter as surveying orchestration frameworks and later updates the recommendation to September 2026, but the warning callout still says the quoted numbers were true when written in "August 2026" (line 30). Updating that month keeps the chapter’s freshness disclaimer consistent with the new measurement date (2026-09-09).
and surveys the general-purpose orchestration frameworks
a lab could build its own agent systems on.
- Files reviewed: 3/3 changed files
- Comments generated: 1
- Review effort level: Lite
| year = {2026}, | ||
| howpublished = {Software}, | ||
| url = {https://github.com/google/adk-python}, | ||
| note = {Apache License 2.0. Accessed 2026-09-09} |
Why
Issue #101 asks for a survey of general-purpose agent orchestration frameworks (AutoGen, LangGraph, and others) so the lab can judge whether any of them beats its current Claude Code subagent and worktree setup.
What
Adds an "Agent Orchestration Frameworks" section to
chapters/agent-orchestration.qmdcovering Microsoft AutoGen and Agent Framework, LangGraph, CrewAI, the OpenAI Agents SDK, and Google ADK, with one-line notes on MetaGPT, LlamaIndex, smolagents, Pydantic AI, and CAMEL (VoltAgent is #45's PR). Each entry gives license, language, how orchestration is expressed, and a "Useful to us?" verdict, with a paragraph in the Comparison section and one Recommendation bullet. Star counts, licenses, and releases were measured on 2026-09-09.Closes #101
🤖 Generated with Claude Code