Plan files on disk
Keep the approach in .vortex/plans/ where you can read and change it before execution.
Closed beta · macOS 12+
A macOS coding agent that ships the job.
You describe the work. Vortex plans, edits, verifies, and ships inside your workspace. The editor, terminal, diffs, and browser are how you watch and steer — not where you are expected to write the solution.
Apple Silicon recommended; Intel supported. Windows and Linux are not part of this beta.
The agent loop
Every job follows the same loop.
Understand the workspace, plan the approach, implement the change, then verify it — with the work visible at each step.
- 01Understand
- 02Plan
- 03Implement
- 04Verify
In the workspace
The request, the plan, the diff, the check.
A compact illustration of the checkpoints Vortex keeps close: the request, the plan, the pending diff, and the verification result.
Job
Improve keyboard focus states across the public pages.
Plan
- 01Map shared controls
- 02Refine focus tokens
- 03Check reduced motion
Review
− outline: muted
+ outline: cyan
+ offset: 3px
Verify
Checks passed
Illustrative sequence, not a live product capture.
How it works
Four modes. Same workspace.
Describe an outcome. Vortex gathers context, follows the mode you choose, and keeps checkpoints in view as work moves from intent to a verified result.
The editor, terminal, diffs, and bundled browser stay available as surfaces for watching and steering the job.
-
01
Ask
Get oriented
Ask focused questions about the workspace and get answers grounded in the files you choose.
-
02
Plan
Shape the approach
Create an editable plan file before implementation starts, then revise the intent in your workspace.
-
03
Agent
Delegate the work
Let the agent edit across files, run terminal commands, and keep the whole job in one continuous loop.
-
04
Debug
Investigate failures
Turn a failing check or unexpected behavior into the next task, with the relevant evidence in view.
Stay in control
The agent moves. You decide what lands.
Plan files and Review mode are checkpoints. The agent does not silently overwrite your workspace.
Pending patches
Review mode gives each agent edit a visible diff. Approve or reject changes instead of accepting a hidden overwrite.
Surfaces for steering
Use the editor, terminal, diffs, and bundled browser to watch the job and redirect it when the evidence changes.
What 100% agentic means
Job-first
Start with an outcome, not a suggestion in the current file.
Local-first
Retrieve workspace context on your machine before you send anything to a provider.
Checkpointed
Review plans and patches while the work is still easy to change.
Headless too
Run vortex run and vortex review when the terminal is the right surface.
Models
Use your keys, or a model on this Mac.
Vortex provides the agent loop and workspace control. Bring your own provider API keys or run an optional local model.
Bring your own key
OpenAI, Anthropic, OpenRouter, and compatible endpoints. Provider costs remain yours.
Keep inference nearby
Optional GGUF models run on your machine through the local model path.
Choose what the agent sees
On-device retrieval and explicit attachments keep context anchored to the workspace you are steering.
Get Vortex
Join the waitlist for the macOS beta.
Access is invite-only while we test the macOS closed beta.
When your invite arrives: Open the DMG, drag Vortex to Applications, and launch it. Stay on the beta update channel during the closed beta.
Closed beta
Request an invite.
We'll email you when a place opens.
Already invited? Sign in to your accountFAQ
Common questions.
The short version of what Vortex does, where your data goes, and how the closed beta works.
Closed beta
Join the waitlist.
You describe the work. Vortex plans, edits, verifies, and ships inside your workspace. The editor, terminal, diffs, and browser are how you watch and steer — not where you are expected to write the solution.