Work Everywhere: Copilot Integrations for Linear, Teams & Slack

[ebndev]

Copilot coding agent now plugs into the tools you already live in—Linear for issue tracking, Teams and Slack for chat-based delegation. Assign work where it starts, track progress in context, and let Copilot handle the GitHub heavy lifting in the background.

---

📋 Linear: Issue-to-PR in One Click (Public Preview)

When you assign a Linear issue to Copilot:

1. Analyzes the issue description and opens a draft pull request.
2. Works independently in an ephemeral GitHub Actions environment—exploring code, making changes, running tests & linters.
3. Streams updates to your Linear activity timeline in real time.
4. Requests review when the work is ready.

Coding.Agent.+.Linear.Burned.mp4

✨ Key Benefits

• Automate repetitive work: Bug fixes, refactors, docs updates—delegate and move on.
• Reduce context switching: Stay in Linear; Copilot handles GitHub.
• Preserve governance: Every PR follows your existing review & approval rules.

🚀 Get Started

1. Install the GitHub Copilot coding agent for Linear app from the GitHub Marketplace.
   • Requires: GitHub org owner permissions + Linear workspace admin access.
2. Configure repo mappings and policies.
3. Assign a Linear issue to Copilot and watch the timeline update.

📘 Learn More

• Integration guide: https://docs.github.com/copilot/how-tos/use-copilot-agents/coding-agent/integrate-coding-agent-with-linear
• Copilot coding agent: https://docs.github.com/copilot/concepts/agents/coding-agent/about-coding-agent---

🎤 Microsoft Teams: GA

The GitHub app for Microsoft Teams is now generally available, offering the same delegate-from-chat experience for Teams users.

Learn more:

• Slack integration docs
• Teams integration docs

---

💬 Slack: Delegate PRs from Chat (Public Preview)

The GitHub app for Slack now works with Copilot coding agent. Mention @GitHub in any thread with a prompt—"Fix missing tooltips on navigation icons"—and Copilot gets to work in the background, then replies when the PR is ready for review.

Coding.Agent.+.Slack.mp4

Try it:

1. Ensure Copilot coding agent is enabled for your account (available on all paid Copilot plans; Business/Enterprise admins must enable the policy).
2. Install or upgrade the GitHub app in your Slack workspace (new permissions required for Copilot features).
3. Mention @GitHub in a Slack thread and follow progress inline.
4. Link your GitHub account if prompted.

Note

The new Copilot functionality is optional. If you skip the upgrade, the GitHub app continues to work for notifications, issue triage, and PR management.

---

🚀 Why Integrations Matter

• Meet teams where they already work: No forcing everyone into GitHub to delegate tasks.
• Async by design: Mention Copilot, keep moving—PRs arrive when ready.
• Preserve governance: Every PR follows your review & approval rules, regardless of origin.
• Reduce tool fatigue: Plan in Linear, chat in Slack/Teams, code in GitHub—seamlessly.

🎯Cross-Integration Use Cases

• Backlog grooming: Assign low-priority issues to Copilot during planning; reviews ready by next standup.
• Triage automation: Tag bugs in Linear with "Copilot-ready" labels; batch-assign weekly.
• Documentation sync: Create Linear issues for outdated docs; let Copilot update and open PRs.
• Sprint overflow: Assign stretch-goal issues to Copilot so the team stays focused on core work.

🔧 Workflow Tips

• Linear: Use issue templates with structured prompts (context, acceptance criteria) to guide Copilot.
• Teams/Slack: Create dedicated channels for Copilot delegation (#copilot-tasks); easier audit trail.
• Automation: Set up Linear automations to assign issues to Copilot when they enter a "Ready for Automation" state.
• Labeling: Tag PRs generated from integrations with labels for expedited review lanes.
• Monitoring: Review Copilot's timeline updates (Linear) or thread replies (Slack/Teams) to catch blockers early.

💬 Feedback

Share what's working—or what you'd like next ⏭️

What integrations do you want next? Jira? Notion? Asana? Let us know.

Work where you plan. Delegate where you chat. Build where it matters. 🚀

[melv-n]

Great, thanks for this!

Could you add a way to provide custom instructions? Right now the agent is always confused what repository to use, and it would be great for us to provide default instructions so the agent can find the correct repository without needing to ask for it.

[melv-n]

We're also seeing lots of issues with Copilot timing out and not understanding what repository to use, despite many attempts where we:

• Put it directly in the start prompt
• Put the repository directly in the issue description
• Replied directly to Copilot, tagging it and using the correct org/repoName format:

It will eventually say "GitHub Copilot stopped responding"

[Akash1134]

Thanks for sharing your valuable feedback @melv-n. We will pass it to the product team.

[jdestgermain]

Is it possible to configure the default branch that the Linear GitHub agent starts from?

[dmirmilshteyn]

Is there a way to configure the repository mapping? I have several repositories driven by a single Linear board. I configured the repository for an agent task the first time, but now there's no way to change it, and all other requests are targeting that initial repository. This prevents me from being able to start agent tasks for anything that isn't on that one repo, which is a real blocker from being able to properly use the integration.

This is what Cursor does, for reference: https://cursor.com/docs/integrations/linear#repository-selection

[seripap]

I am unsure on how to get this working, or even steps to set a repo here. the app and copilot is authorized across all repos but to no avail. the repo in this context already has access to copilot and is setup for it.

[hitherejoe]

This was previously working for me, but not the copilot agent will not respond in any issue that I assign it to. Any pointers as to what might be causing this? 🤔