OpenHands just shipped the control plane your coding agents didn't know they needed

77,000-star OpenHands just turned terminal coding sessions into event-driven engineering workflows.

Agent Canvas dropped June 16. It's the new interface for OpenHands — and it changes the shape of how you interact with coding agents.

Here's what it actually does:

One browser UI drives any agent. OpenHands, Claude Code, Codex, Gemini CLI — connected via ACP (Agent Client Protocol). Your existing subscriptions. Your existing models. Nothing changes.

But the real shift is automations. Set up a Slack trigger that starts an agent conversation when someone posts a bug report. Wire a GitHub webhook that auto-reviews every PR. Schedule a cron job that sweeps stale issues every morning.

Your coding agent stops being a terminal session you manually start and monitor. It becomes a workflow that runs when engineering events happen.

The architecture is local-first, cloud-ready. Start on your laptop with `npm install -g @openhands/agent-canvas`. Connect a remote VM when you want always-on execution. Scale to OpenHands Cloud when your team needs shared infrastructure.

The backend flexibility is the key detail most people miss. Agent Canvas connects to multiple agent servers simultaneously. One agent running on your H100 cluster doing experiments. Another on a CPU cluster processing data. A third at home implementing features. All managed from one interface.

ACP is the open protocol that makes this possible. Any agent harness that implements it can connect. This isn't a vendor lock-in play — it's an interoperability layer for the agentic era.

Stop prompting your agents by hand. Install Agent Canvas, connect your first automation, and let engineering events drive your agent workflows.

SOURCE: https://www.openhands.dev/blog/introducing-agent-canvas
VERIFIED: OpenHands blog (June 16, 2026), OpenHands docs, Graham Neubig X post
SIGNAL: The shift from ad-hoc agent prompting to event-driven agent automation is the architectural pattern that separates toy deployments from production systems.