Support multiple agent frameworks including Cargo AI and Mastra#7
Closed
ryw wants to merge 2 commits into
Closed
Conversation
…pport Co-authored-by: Ry <4283+ryw@users.noreply.github.com>
…gent formats Co-authored-by: Ry <4283+ryw@users.noreply.github.com>
ryw
added a commit
that referenced
this pull request
May 22, 2026
PR #7 argued — correctly — that the v0.1 AGENT_FORMAT decision's universal diff-readability premise breaks down once you account for v0.2's YOLO mode (CI as the gate) and v0.4's RBAC (production review applies regardless of format). Capturing that intent here rather than merging #7, which conflicts with the deleted Node CLI placeholder and pre-dates PR #5/#6 + the v0.1 scaffold. - context/0.3/README.md: new "Direction (v0.3+): Multi-framework agent runtime support" section names LangGraph / OpenAI Agents SDK / Mastra / CrewAI / Pydantic AI code mode as candidate first-class supported runtimes, defines what "supported" means (runtime, git, runs/logs, HITL, observability, governance), and explicitly defers shipping pacing to pilot demand. Adds matching FAQ + open questions. - context/0.3/USER_STORIES.md: US-0.3-13 — run a code-defined agent with full parity on governance, dashboards, and HITL. - context/0.1/AGENT_FORMAT.md: forward-pointer from "Why we did not pick a code-first framework" to the v0.3 direction, and a matching bullet in the v0.3 row of the per-phase table. Closes-in-intent: #7 (PR closed manually; substance recorded here). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Member
Author
|
Closing in favor of c2b4829 on Why not merge as-is
What got captured in c2b4829
Key argument from this PR that survives: YOLO mode (per v0.2 PR policy) breaks the "universal diff-readability" premise the v0.1 AGENT_FORMAT decision rests on. Format is not the governance lever; the policy engine is. That reasoning is now in the v0.3 README direction section. What was not pulled forward
Thanks for the research and the well-argued case — it shifted the decision. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
context/0.1/AGENT_FORMAT.md, recommending Pydantic AIAgentSpecand Cargo AI JSON as declarative defaults.agents/README.mdto explain supported agent formats and usage guidance.README.md,DEMO_SCRIPT.md,USER_STORIES.md) to reflect multi-format support and governance model.AgentSpecYAML agent starter file (hello-world.yaml).This PR researches, documents, and implements multi-format agent support, including cargo-ai and Mastra, with recommendations and starter templates.