AI NewsDev toolsAnnouncement

GitHub Copilot now connects to Supabase, Box, Calendly and five more

GitHub added public preview connectors to Copilot for Box, Buildkite, Calendly, ClickUp, Mixpanel, Supabase, Webflow and Wix.

AI News

Editorial2 min read

LinkedInX
Signal field artwork from the Reveneau library, used for a Copilot connectors story

Why it mattersCopilot can now read a failed Buildkite run and fix the code in the same chat. The agent reaches the systems the developer uses, so the developer stops being the courier between them.

A coding agent that only sees the editor is blind to the rest of the stack. Why a build failed, which task is late, what the analytics show after a release: all of that sits in other tools, and the developer is the one who copies the answer back. GitHub posted a changelog entry that cuts one trip out of that loop. Copilot can now sign in to eight more third-party services and act inside them from the chat.

The new connectors

The eight new services are Box, Buildkite, Calendly, ClickUp, Mixpanel, Supabase, Webflow and Wix. Each one maps to a specific job. GitHub lists them side by side in the changelog, with one line each.

Box lets Copilot "search and manage content, and use Box AI". Buildkite lets it "work with pipelines and builds". Calendly handles "scheduling and meetings". ClickUp lets it "track tasks and projects". Mixpanel lets it "explore product analytics". Supabase covers projects and databases, and Webflow and Wix both let Copilot manage sites and content.

The sample use case in the post is the one most developers would notice first. GitHub says a user can ask Copilot why their latest Buildkite build failed. Then, the post adds, Copilot can "fix the code in the same session". The agent reads the build log, finds the problem, and proposes a change in the chat.

Who gets them, and when

The new services are in public preview. "Connectors are in public preview for all Copilot plans", GitHub states. That covers Copilot Free, Copilot Pro, Copilot Business and Copilot Enterprise. The paid plans add a step. On Copilot Business or Copilot Enterprise, an admin has to enable "Editor preview features" first.

The post does not list a date for full availability. It does not list a price for the connector traffic, either. A team planning on the new behaviour should expect the rules to tighten later.

What this is not

The connectors give Copilot read and write access to a signed-in user's account on each service. That is a strong permission to hand to a chat window. Sign-in goes through OAuth, scoped per user. The agent can only do what the user who signed in could do. So a developer piloting a connector on their own Calendly or ClickUp is giving Copilot the same reach they have.

The quieter effect is on where the evaluation of a Copilot deployment happens. Three months ago, the question was whether Copilot could write a function. This month, it is whether Copilot acting on a production Supabase project is a decision the security team has seen. The eval surface is the one the connector reaches.

Source

GitHub, Connect Supabase, Box, Calendly, and more to Copilot.

SourceGitHub

This item was written by an AI system from the linked source. Reveneau is responsible for what it publishes.

Share
LinkedInX
Start a project