Bird vs Discourse
Side-by-side trajectory, velocity, and editorial themes.
Bird is shipping AI agents far outside its CX/messaging roots — Travel Explorer and an autonomous code pipeline.
Bird's last three monthly notes describe a CX latency win (60% chat response-time cut via router bypass and greeting fast path), a consumer AI travel agent (Travel Explorer with destination research, hotel recs, itinerary building), and an autonomous code-delivery pipeline (Forge: AI review, tiered testing, zero-touch deploys with rollback). The remaining tracked entries are duplicate aggregator views of the same three releases.
Despite being categorized as customer support and messaging, Bird's actual shipping pattern reads like a generic AI-agent platform: a messaging speedup that benefits the legacy product, plus two agent-shaped surfaces (consumer travel, autonomous DevOps) that have nothing to do with CX. The company is using its CRM/messaging customer base as a distribution channel for adjacent AI-agent products rather than deepening the support tooling itself.
Expect more vertical AI-agent surfaces wrapped under the Bird brand — likely commerce, scheduling, or recruiting agents — alongside continued latency and routing improvements to the chat core. The next pricing question is whether these agents bundle into the existing CX seat or detach into separate metered SKUs.
Discourse opens its AI bot to any external MCP server, treating the forum as an agent host.
Discourse runs on a monthly main release plus periodic security intermediates, and the editorial focus across recent posts is clearly AI plumbing. March added Bring-Your-Own MCP server support to the Discourse AI Bot, alongside documented AI credentials management and SSO auto-provisioning for forum admins. The team has also been adjusting its release-communication process, with backdated intermediate-release topics filling earlier gaps.
Discourse is positioning the forum as an environment that hosts agents, not just a place that uses AI features. By accepting any MCP-compatible tool provider as a backend, it makes itself the substrate community managers extend with arbitrary external capabilities — search, ticketing, knowledge bases, whatever the host wires in. SSO auto-provisioning and structured form templates round out the admin surface that this agent-host posture needs.
Expect deeper agent UX inside topics — more entry points and persona configuration — alongside audit and observability tooling for what external MCP tools do on a forum. Community trust depends on that side staying explainable.
See more alternatives to Bird →
See more alternatives to Discourse →