Welcome to Goa AI Discussions! #3
Replies: 1 comment
-
|
I maintain Better Agent, a local web workspace for supervising native Claude, Codex, and Gemini coding sessions. The core design choice is to preserve each provider’s real session and capabilities while projecting approvals, files, parent/delegated work, and restart recovery into one inspectable operator surface. What brought me to Goa-AI is its design-first treatment of tools, policies, MCP servers, and durable execution. Better Agent currently integrates provider-native CLIs rather than imposing a common agent runtime, so a useful boundary would be generated, typed MCP services that sessions can consume without flattening provider-specific semantics. I am especially curious whether Goa-AI’s generated contracts can express a shared policy envelope—allowed tools, approval requirements, and structured results—while letting Claude, Codex, and Gemini retain different session/event models behind that envelope. That would make the integration contract stable without pretending the providers behave identically. It is source-available and free for non-commercial use; commercial use requires separate permission. AI-assistance disclosure: this comment was drafted by Codex under the maintainer’s authorization and reviewed in Better Agent. |
Beta Was this translation helpful? Give feedback.
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.
Beta Was this translation helpful? Give feedback.
All reactions