You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are the ColomboAI integration team. We are integrating MC-1 — Auto Intelligence, our Intelligence Control Plane, with agent and developer frameworks.
Models generate intelligence. Agents turn intelligence into action. MC-1 controls the system between them. It is the layer that decides how intelligence is selected, governed, evaluated, and improved. Google ADK therefore gains an adaptive intelligence layer without requiring the framework or its users to choose a permanent model-provider winner.
ADK's existing LiteLlm, LlmAgent, and Runner seams appear sufficient, so we are not proposing a dedicated model class or community extension. Our provider-neutral recipe uses openai/colomboai/mc-1, https://mc1.cairo.sh/v1, and MC1_API_KEY.
Would a concise generic OpenAI-compatible endpoint recipe be useful in adk-docs, or is another documentation surface preferred? We would welcome guidance before opening any issue, code change, or documentation pull request, and are interested in a deeper documentation and conformance partnership around the existing generic model seam.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Hello Google ADK maintainers,
We are the ColomboAI integration team. We are integrating MC-1 — Auto Intelligence, our Intelligence Control Plane, with agent and developer frameworks.
Models generate intelligence. Agents turn intelligence into action. MC-1 controls the system between them. It is the layer that decides how intelligence is selected, governed, evaluated, and improved. Google ADK therefore gains an adaptive intelligence layer without requiring the framework or its users to choose a permanent model-provider winner.
ADK's existing
LiteLlm,LlmAgent, and Runner seams appear sufficient, so we are not proposing a dedicated model class or community extension. Our provider-neutral recipe usesopenai/colomboai/mc-1,https://mc1.cairo.sh/v1, andMC1_API_KEY.The reviewed evidence uses Google ADK 2.7.1 with LiteLLM 1.97.0. The bounded no-network released-host proof, wheel-lock evidence, configuration guide, and known limitations are public. Authenticated MC-1 production validation remains separate and is not presented as complete.
Would a concise generic OpenAI-compatible endpoint recipe be useful in
adk-docs, or is another documentation surface preferred? We would welcome guidance before opening any issue, code change, or documentation pull request, and are interested in a deeper documentation and conformance partnership around the existing generic model seam.Technical overview: https://cairo.sh/MC-1
Regards,
ColomboAI integration team
All reactions