GitHub user richardchen874-sys added a comment to the discussion: 📢 CloudStack CMK Skill for AI Agents — Automating CloudStack with LLMs
The provider behavior behind "CloudStack CMK Skill for AI Agents Automating CloudStack with LLMs" is what I would test first: latency, usage fields, tool calls, streaming, and fallback can diverge even when the first request succeeds. I would log route choice, provider/model, tool-call support, latency, usage, and retry/fallback reason together. Agent failures are much easier to debug when the route decision is visible. I am testing a multi-model OpenAI-compatible API layer around official Chinese models, so the routing and usage-accounting parts of this are directly relevant to me. For cloudstack, is the harder problem provider compatibility, routing quality, or keeping per-run cost predictable? GitHub link: https://github.com/apache/cloudstack/discussions/13640#discussioncomment-17954373 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
