copilot cloud agent is becoming an automation api

GitHub quietly crossed an important line this month: Copilot cloud agent tasks can now be started through a REST API.

That sounds like a small product update. Another endpoint. Another preview feature.

But I think this is one of those boring-looking changes that tells you where the whole category is going.

Once an agent can be started by an API, it becomes automation infrastructure.

Not "ask the assistant to fix this file."

More like: an internal developer portal creates a repo, opens a tracked agent task, watches progress, and collects the pull request. Or a migration script fans out dependency upgrades across repositories. Or the release workflow asks an agent to prepare the weekly PR.

That is useful.

It is also where the real problems begin.