Skip to main content

Welcome to the CAO blog

· 2 min read
CAO Maintainers
CAO Maintainers
CLI Agent Orchestrator team

The reference documentation tells you what CAO does. It's a poor fit for the other half of the story — the walkthrough that takes an hour, the design decision that needs three diagrams to justify, the write-up of an orchestration that worked on real work and the two that didn't. This blog is where that goes.

Anyone who contributes to CLI Agent Orchestrator can publish here. Posts live in docusaurus/blog/ and ship through the same pull request review as the rest of the repository.

What belongs here​

  • Tutorials and how-tos — a task followed end to end, with commands a reader can run.
  • Deep dives — how a subsystem works and why it's built that way. Sessions, the MCP server, and provider adapters all have more depth than their reference pages carry.
  • Orchestration patterns in practice — handoff, assign, and send-message composed into something real.
  • Case studies — what you built, what it cost, and where it fell over. The failures are the useful part.

What doesn't​

Release announcements. CHANGELOG.md and GitHub Releases already carry them, and a blog that mirrors a changelog becomes a stale changelog. We're deliberately not doing that.

Marketing. No product pitches, no competitor comparisons, no claims a reader can't verify from the repository.

Publishing a post​

The contributing guide has the mechanics: the file layout, the front matter, registering yourself in blog/authors.yml, and the style rules the build enforces. The short version is that a post is a directory, a Markdown file, and a pull request.

If you're not sure whether an idea fits, open a discussion and ask before you write. It's a cheaper conversation than a rejected draft.