Editor-based assistants
Vortex vs GitHub Copilot
GitHub Copilot assists you inside your editor and GitHub. Vortex takes a whole job — plan, edits, commands, verification — on macOS.
GitHub Copilot is an assistant that lives inside your editor and your GitHub workflow: inline suggestions as you type, a chat panel, and review assistance on pull requests. It is available broadly across editors and platforms.
Vortex is a macOS app for a different shape of work. You assign a whole job; the loop is understand → plan → implement → verify inside your workspace. It retrieves context on-device, writes an editable plan file, edits across files, runs commands, and verifies.
Both are legitimate choices. This page is about which one fits which job.
The short version
| GitHub Copilot | Vortex | |
|---|---|---|
| Primary interface | Your editor, plus GitHub | A job assigned to the agent, with the desktop app as a steering surface |
| Unit of work | A completion, an inline edit, or a chat turn | A whole task: context, plan, edits, commands, verification |
| Plan on disk | No plan file | Plan mode writes an editable .vortex/plans/<name>.plan.md |
| What lands on disk | Edits apply as you accept them | Review mode stages edits as pending patches until you approve each one |
| Context handling | Editor- and GitHub-managed retrieval | On-device retrieval (lexical, symbol, path, outline, references); nothing uploaded to build an index |
| Model choice | Managed by the vendor | BYO OpenAI, Anthropic, OpenRouter, or any compatible endpoint; optional local GGUF models |
| Platform | Broad editor and OS coverage | macOS 12+; closed beta. Windows and Linux are out of scope for this beta |
| Price model | Vendor-managed; see GitHub for current terms | Free during the closed beta; you pay your model provider directly |
Where GitHub Copilot is the better fit
- You want inline completion as the main speed-up, inside the editor you already use.
- You work across editors and platforms, including Windows and Linux.
- You want deep GitHub integration: pull requests, review assistance, and the GitHub surface you already live in.
- You are buying for a team or enterprise and want a vendor-managed plan with admin controls.
- You want a broadly available assistant today rather than a beta on one operating system.
- Your tasks are mostly local to one file or one function, where a suggestion is enough.
Vortex is macOS-only during the closed beta, and inline completion is not where it competes. If your main speed-up is suggestions while you type, Copilot is the more direct answer.
Where Vortex is the better fit
- Whole-job delegation. The unit is a task — "make the failing test pass and keep the public API stable" — not a suggestion.
- The plan is a file. Plan mode writes
.vortex/plans/<name>.plan.md, so the approach is reviewable, editable, and diffable before any edit happens. - A checkpoint before changes land. Review mode keeps agent edits as pending patches in the Changes panel; you approve or reject each one. The agent does not silently overwrite your workspace.
- Context you can inspect. Retrieval runs on your Mac — lexical, symbol, path, outline, and reference search — and nothing is uploaded to build an index.
- Model choice. Bring your own key for OpenAI, Anthropic, OpenRouter, or any OpenAI-compatible endpoint, and optionally run a local GGUF model on the Mac.
- The job can finish headless too. The same workspace runs in the terminal with
vortex runandvortex review, which is useful in CI or over SSH.
What a Vortex job looks like
A job starts with context and a plan, not a completion. In the desktop app the loop is visible in the transcript, the diffs, and the Changes panel; the same loop runs without a window:
vortex run --prompt "make the failing test pass and keep the public API stable" --workspace .
vortex review --json --base main --fail-on errorDetached runs write their status and traces under ~/.vortex/detached/<id>/, so a long job can keep going while you do something else.
Using them together
Copilot and Vortex do not conflict on disk, and most people would not replace one with the other. Keep Copilot for inline completion while you type; hand Vortex the jobs that span files, commands, and verification. Vortex reads the same repository and honours AGENTS.md and Cursor-compatible .vortexrules, so your existing project instructions keep working.
Where the two overlap
Both will answer a question about a file, and both will make a small edit if you ask. The overlap is real, and for a one-line change either is fine. The split shows up when the task is too large to hold in one suggestion: several files, a command to run, and something to check at the end.
A quick way to choose
- If the work is "finish this line as I type", stay in your editor with Copilot.
- If the work is "make this change across the project and prove it works", hand it to Vortex.
- If you need Windows or Linux today, Vortex's beta does not cover it.
- If you want third-party or local models rather than a vendor-managed one, Vortex is built around that.
Migrating a Copilot setup
Nothing needs to be ported. Vortex reads the same repository and honours the project instructions already on disk. Keep Copilot installed for quick inline edits if you like; the two tools do not conflict.
What Vortex does not claim
Vortex is in a closed beta. Verification gates are advisory today: you can require an exit code or an output phrase for a check, but the agent does not hard-block a task on a failing gate. search_memory is lexical, not semantic — there is no embedding corpus or vector search. And the beta is macOS 12+ only; Windows and Linux are out of scope for now. If any of those matter more than plan-file and patch review, wait for a later beta.
Try it
Vortex is invite-only on macOS 12+. Join the waitlist, or compare it with Cursor and read what the agent loop does before you decide.