Does GitHub Copilot run agents?

Copilot has an agent mode in the editor and a cloud agent that works in the background and opens a pull request you review. GitHub's docs also describe cloud and local sandboxes and scheduled automations. It all runs as a GitHub-hosted service.

Can I self-host GitHub Copilot?

No. Copilot is a hosted subscription service, and its models and infrastructure are GitHub's. OpenHands self-hosts on a machine you choose, and Kortix self-hosts the whole system in your VPC or on-prem network, with self-host free.

Can I bring my own model to GitHub Copilot?

The Copilot pages describe choosing from a catalog of leading models and an automatic model selection, not bringing your own keys. OpenHands brings your own model, and Kortix takes any model provider with your own keys.

Where does an editor assistant stop and a company system start?

A coding assistant works inside a developer's loop: code, suggestions, review, ship. A company system runs work that has no diff, such as replies and reports, keeps the agents and memory in one repo, and lands agent work through a change request a person reviews. Copilot and OpenHands cover the first shape; Kortix covers both.

OpenHands vs GitHub Copilot: an open source harness compared with a hosted assistant

OpenHands and GitHub Copilot are both real ways to bring AI to code; OpenHands is open source and self-hosted, Copilot is closed and hosted by GitHub. Kortix, the open-source AI Operating System, is the pick when agent work has to span a whole company.

Try Kortix

Kortix, OpenHands and GitHub Copilot, side by side

Kortix is the pick when agent work has to span a company; both rivals cover the developer's loop. Rival facts come from each project's own repository, docs and product pages, checked October 2026.

Differences only

CriteriaKortixOpenHandssource

What it is: A company-wide agent system you run from one git repo; A self-hosted developer control center for coding agents
Open source: Yes, read it, fork it, audit it; Yes
Where it runs: Kortix Cloud, your VPC, or on-prem; self-host is free; Locally, in Docker, on a VM, or your infrastructure
Who holds the code and context: You do: your repo, your keys, your infrastructure; You do; self-hosted, and the agent runs on your machine
Model choice: Any model provider with your own keys; Use with any LLM
Where it works: Web, Slack, Teams, CLI and every connected app; A browser control center or the terminal CLI
Work outside code: Company work: reports, replies, actions across 3,000+ apps; Coding automations, Slack reports and issue triage
Who reviews the agent's work: A person, through a change request; merge is default-deny; Engineers review code; the agent has host filesystem access

CriteriaKortixGitHub Copilotsource

What it is: A company-wide agent system you run from one git repo; A hosted AI coding assistant across your editor, CLI and GitHub
Open source: Yes, read it, fork it, audit it; No; a hosted GitHub service
Where it runs: Kortix Cloud, your VPC, or on-prem; self-host is free; GitHub's cloud and your editor; a subscription service
Who holds the code and context: You do: your repo, your keys, your infrastructure; GitHub: your code context is sent to its model
Model choice: Any model provider with your own keys; Model catalog and automatic selection inside Copilot
Where it works: Web, Slack, Teams, CLI and every connected app; Your IDE, the CLI, GitHub and chat apps
Work outside code: Company work: reports, replies, actions across 3,000+ apps; Developer workflow only: code, reviews, docs and automations
Who reviews the agent's work: A person, through a change request; merge is default-deny; You review suggestions and pull requests in GitHub

Work that runs without a developer at the keyboard

kortix.yaml

# kortix.yamltriggers:  - slug: daily-digest    type: cron    cron: '0 0 9 * * 1-5'    prompt: Summarize yesterday's support tickets and open a change request with the digest.

Source: https://github.com/kortix-ai/suna

From the Kortix README: a trigger starts a session on a cron schedule, so agent work runs across the company with nobody watching.

What each tool is for

GitHub Copilot is a hosted AI coding assistant. Its own product page calls it an AI coding agent and shows it working in your editor, on the command line, and across GitHub, with inline suggestions, chat, and an agent mode that proposes edits. GitHub sells Copilot on subscription plans that run from a free tier to business and enterprise tiers, and the service and its models stay on GitHub's side. OpenHands is a self-hosted developer control center for coding agents and automations. It runs on a machine you choose and can drive its own agent or another one you already use, such as OpenCode.

An assistant inside your editor against a harness that runs agent work

Copilot lives where a developer types. It completes code, answers questions in the editor, and in agent mode proposes edits and can run an assigned task in the background, with a cloud agent that opens a pull request you review. The unit of work is a developer's task inside an editor session or a background job on GitHub. OpenHands runs agent work as conversations and automations on its own agent server, behind a browser control center that can front several backends at once. That unit of work is a coding conversation or an automation, and it ends in a change to a repository.

Where the code, the models and the keys live

GitHub Copilot sends code context to GitHub's model to produce a suggestion. Its own page explains that the lines around your cursor, your open files and repository paths are sent to the model to work out what comes next, so the code context leaves your machine and the service is GitHub's. OpenHands runs on your laptop, in Docker, on a virtual machine or inside your company infrastructure, and you bring your own model, so the host and the key stay yours. Kortix goes the same way on a larger scale: run it on Kortix Cloud, in your VPC, or on your own on-prem network, with any model provider and your own keys. The self-hosting guide covers that choice in detail.

Where a hosted assistant's model of work stops

A hosted coding assistant is built around the developer's loop: write code, read suggestions, review a pull request, ship. Copilot's billing, models and integrations all point at that loop, and its sandboxes exist so it can touch code, tools and files safely. Work that has no diff and no editor, such as a support reply or a finance summary, never enters it. OpenHands reaches a little further with automations that publish a report to Slack or break a GitHub issue into tasks, and its connectors stop at developer services. Neither tool holds a company's agents, memory and connector rules in one place that a manager outside engineering can review. OpenHands for teams works through what that gap means as a team grows.

The practical rule for choosing

Choose by the shape of the work and the place the code has to stay. Keep Copilot when your team wants suggestions inside the editor and a hosted service that GitHub maintains. Keep OpenHands when you want to self-host a control center for coding agents and automations. Kortix is the pick when agent work spans departments, when the outcome has to be reviewable outside engineering, or when the code and its context have to sit on infrastructure you control. OpenHands vs Kortix covers the move, and Is OpenHands open source? answers the question teams ask first, as does the Kortix blog's Kortix vs OpenHands.

OpenHands vs GitHub Copilot, answered

Does GitHub Copilot run agents?: Copilot has an agent mode in the editor and a cloud agent that works in the background and opens a pull request you review. GitHub's docs also describe cloud and local sandboxes and scheduled automations. It all runs as a GitHub-hosted service.
Can I self-host GitHub Copilot?: No. Copilot is a hosted subscription service, and its models and infrastructure are GitHub's. OpenHands self-hosts on a machine you choose, and Kortix self-hosts the whole system in your VPC or on-prem network, with self-host free.
Can I bring my own model to GitHub Copilot?: The Copilot pages describe choosing from a catalog of leading models and an automatic model selection, not bringing your own keys. OpenHands brings your own model, and Kortix takes any model provider with your own keys.
Where does an editor assistant stop and a company system start?: A coding assistant works inside a developer's loop: code, suggestions, review, ship. A company system runs work that has no diff, such as replies and reports, keeps the agents and memory in one repo, and lands agent work through a change request a person reviews. Copilot and OpenHands cover the first shape; Kortix covers both.

Keep the assistant, add the system it cannot be

Move one department's work first and keep git as the record on both.

Try Kortix OpenHands for teams