Welcome to Goa AI Discussions! #3
Replies: 2 comments
|
Thanks for the thoughtful introduction. Better Agent’s choice to preserve provider-native sessions rather than flatten them aligns well with Goa-AI’s separation of contracts from runtime adapters. At the tool boundary, this works today: a Goa design can own stable input schemas, validation, typed results, and generated MCP adapters while Claude, Codex, and Gemini retain their own session and event models. There is one important caveat around policy. Goa-AI generates tool tags and confirmation metadata and enforces allowlists and approval gates when its runtime owns execution. That policy metadata is not currently exposed as a portable envelope through MCP tools/list, and MCP itself does not standardize cross-client approval semantics. Native CLIs would therefore share the typed tools and results, but not automatically the same approval behavior. The clean integration boundary seems to be: generated MCP services provide the canonical capability contract; Better Agent preserves each provider’s event stream; and one dispatch boundary enforces tool admission and approval before side effects. Exposing a typed projection of Goa-AI’s generated policy metadata for that boundary would be an interesting direction to explore. A concrete Better Agent integration would be very useful for shaping it. |
Uh oh!
There was an error while loading. Please reload this page.
Welcome to Goa-AI Discussions! 👋
We're excited to have you here! This is the place to connect with the Goa-AI community—from newcomers exploring design-first AI backends to experienced developers building production MCP servers.
What to use Discussions for:
Community Guidelines:
Get Started:
Drop a comment below and introduce yourself! Tell us:
Looking forward to seeing what you build with Goa-AI! 🚀
For maintainers: Consider linking question-related issue templates to Discussions and converting old "question" or "discussion" labeled issues.
All reactions