Build websites and apps with coding agents, in one workspace.
Start with what you want to make. Keep shaping it as you go.
Free to use on macOS, Windows and Linux. Connect your own coding-agent account.
YOUR AGENT. YOUR ACCOUNT. YOUR CHOICE.
Keep multiple account profiles for Codex and Claude Code. Use the provider icon and model picker in chat to choose the agent for your task. Your provider’s subscription and usage limits stay with that provider.
VIBE CODING, FROM IDEA TO PREVIEW
You don’t need to have the whole app figured out. Start with one useful thing, see it working, then decide what comes next. Vortex keeps the conversation, the project and the result together.
A booking page for your studio. A dashboard for your business. That small tool you keep wishing someone would make. Explain who it’s for and what they should be able to do.
“Build a simple app to track my freelance projects, with a deadline and a status for each one.”
Choose your connected coding agent. Let it create the project and guide the setup, or bring a folder you already have. Follow its progress, answer questions and steer the work as the idea gets clearer.
Make your first appOpen Browser and choose your project’s Preview tab beside the conversation. Click through the app, try the form and ask for the next change. “Make that simpler” is a perfectly good place to start. Inspect the files and checks when you want more detail.
Meet the previewMORE THAN ONE PROJECT IN MOTION
Keep building while other tasks move forward. Workspace icons show running agents, requests for input and unread results, so you can see where your attention is needed.
Follow the workspace icons on the left. Each shows its running agents, requests for input and unread results. Select a workspace, then open the conversation you need. Your workspace order stays the same as messages arrive.
Ask your agent to split useful work into parallel tasks. Subchats appear in expandable cards under the main chat while needed. Fully completed children are cleaned up after their result is handed back and the parent has settled. Open a card for the details and use Back at the top to return. Agents can share a project while coordinating their changes.
Type @ to choose a work step such as @design or @qa for your current agent. Start a message with a project mention such as @foodcard to launch a new chat there, even in another workspace, and follow it from the destination workspace.
Explore workspace activity & @ mentions ↗A SMALL START CAN GO A LONG WAY
Start with one useful page or a single everyday task. Tell your agent who it’s for, try the first version and build on what you learn.
Your portfolio, a page for a local business or a home for your next launch. Get the story and layout right, then refine the details in the preview.
A project tracker, a shared checklist or a simple inventory. Start with adding and saving an item, then build the screens that make it useful.
Open an existing project. Fix a frustrating flow, add a feature or explore a redesign, with the conversation and source changes side by side.
APPROACHABLE UP FRONT. CAPABLE UNDERNEATH.
Let your agent handle the unfamiliar parts while you focus on the result. When you want to understand a change, check real data or take control yourself, the tools are already in your workspace.
Explore the tools in the workspace demo ↑
01
Start with one chat. Drag another beside it or above or below it, and see the arrangement before you drop. Resize the areas, expand a chat to focus, then restore your layout. Keep only chats in view, or open Files, Source Control, Browser and a terminal as you need them. Your app’s Preview and reference websites share one Browser panel. Give the editor, tools and terminal room to breathe; panel sizes follow you between projects in the same workspace.
Arrange chats & keep browsing ↗02
Work on parallel tasks in the same project or choose an isolated Git worktree for a chat. Browse another project without redirecting that chat’s work. Review the isolated change before merging it back. Linked tasks use a lighter model from your provider for routine work and the stronger model for justified complex work. Fast mode stays off for linked tasks and starts off in new chats. Follow delegated work in the main chat’s subchat cards, open a card to inspect its result and use Back to return. Workspace badges help you find running work and unread results across projects.
Parallel & linked work ↗03
Inspect MySQL, MariaDB, PostgreSQL or SQLite. Browse rows, write SQL, explore a schema and import or export the data you need. Save API requests with environments and authorization, then use scripts and tests to check both a successful response and an error. In Auto, ask your agent to read data or update selected records without approving every step. Compare what the database holds with what your app shows.
Make a repeatable API check ↗04
Catch development email through local or cloud SMTP and inspect its HTML, text and attachments. Connect Signals to your app, filter events and follow an error into its context. Send the relevant result back to your agent so the next fix starts with evidence.
Check your app’s test mail ↗05
Choose a project or branch badge inside Files or Source Control. Folder and fork icons distinguish the working copies; a check mark and stronger colour show what’s selected. Browse large projects, search files and review the changes that matter. Open files and Git diffs as grouped editor tabs. Keep the editor beside or above your chat, or above or below Files and Source Control. Resize the panels and expand or restore them from the header while keeping unsaved edits. Review diffs, stage changes and make a manual commit. Connect GitHub or GitLab and use Git Flow when it fits your project. The terminal stays below your work, close to local servers and background processes.
Review files and changes ↗06
Open saved resources from Tools in the sidebar or search. Use the direct Project settings button and its Connections section to choose resources for the workspace. Keep supported tools docked or floating inside Vortex, beside your chat or editor. Open a local shell or saved SSH host, tunnel to a private database and transfer files with FTP, FTPS or SFTP. Keep credentials in the encrypted Vault.
Manage project connections ↗07
Build a personal skills library, then select the skills each project needs. Save project instructions for its conventions and checks. Reuse what helps the task while keeping the project’s scope and your permissions clear.
Choose skills and project instructions ↗08
Check connected apps and MCP server status for your provider. Refresh the status or reconnect where supported, then try the tool you need. Connect external tools to chats or share Vortex’s tools with a local agent, with the selected resource and permission scope kept explicit.
Manage connected apps and MCP ↗MORE ROOM TO MAKE
Vortex is free. Bring your own coding-agent account and use the whole workspace, from your first conversation to the details of a working app.
Create the workspaces, projects and saved conversations you need. Open another chat, try a worktree or link tasks across projects. There are no paid tiers or product count caps.
Preview, Git, databases, APIs, terminals, test Mail, Signals, local schedules, encryption and MCP are all available. Save and reuse connections without a subscription gate.
Your coding agent uses your own provider account and its usage limits. Vortex does not include AI tokens or hosted agent runs. Optional cloud storage has technical limits to keep the service reliable.
Understand cloud storage ↗THE PERSON BEHIND VORTEX
I’m Yuliyan Doev, a software developer with 15 years of experience building websites, applications and business systems.
My work spans the full development stack: backend services, frontend interfaces, databases and the Linux environments that keep applications running. Over the years, I’ve worked with PHP, Go and Node.js, built interfaces with React, Angular and Vue, and used MySQL, PostgreSQL, NoSQL databases and Docker across different projects.
My experience includes public-facing platforms, custom CRM and ERP systems, websites and applications built around specific business needs. I’ve worked both independently and as part of development teams, contributing to the different pieces that turn an idea into usable software.
Vortex brings those areas of development together. A conversation with a coding agent is one part of the work. There are also files to review, databases to inspect, APIs to test, servers to connect to and changes to manage in Git. I’m building a workspace where those activities stay connected, with the tools available when you need them.
I want Vortex to be useful whether you’re an experienced developer working on an existing system or someone taking the first steps towards building an application. You can start with an idea, work through it with your chosen agent, try the result and keep improving it.
Vortex is free to use. You bring your own coding-agent account, with that provider’s terms and usage limits. My focus now is on making the workspace useful, listening to the people using it and developing it around the work they actually need to do.
A FEW THINGS YOU MIGHT BE WONDERING
Want the walkthrough?
Start with the guides ↗
Start by describing the app you want, then build it through conversation with your connected coding agent. Try each change in the preview and ask for the next improvement. Vortex keeps the code, tools and checks within reach, so you can learn as you go or take control of the details.
You can start by describing what you want to make. Your connected coding agent writes code and helps with setup; you guide it, try the app and ask for changes. Building something reliable still takes testing and decisions. The guides start with a small first app and introduce the details as you need them.
Connect your own Codex, Claude Code, Google Antigravity, Grok Build or Kimi Code account. Vortex brings the workflow together; it does not include provider subscriptions or AI tokens. Available models and usage limits depend on your chosen provider.
Your project files and running app stay on your computer. Agents use the access you grant them, and prompts sent to a provider follow that provider’s service. Optional encrypted workspace sync helps you continue across devices; it does not upload your whole Git checkout or move a running process to the cloud.
Yes. Open its folder or clone its repository, select an agent and give it a bounded task. Vortex helps inspect the project, prepare its runtime and start its preview. You can review file changes and Git diffs as you go.
In Auto, an agent can carry out work you have asked it to do, such as reading data, editing files or updating selected records, without asking before every tool call. Supervised and Auto-edit ask before Vortex tool changes. Auto-edit can accept local file edits through your provider; Plan is read-only. Vortex blocks mass-destructive commands such as deleting a whole database. Device permissions and provider restrictions still apply. Publishing or sending real messages needs to be part of your request.
Use the connected tools in an ordinary workflow: inspect a database and run SQL, send and check API requests, inspect test Mail, follow Signals, connect to a server over SSH or transfer files with FTP, FTPS or SFTP. Reuse saved resources where useful and keep the task scoped to the project and resource you intend.
Yes. Use a plain chat to explore an idea. Plain chats have no project settings. Attach or open a project when you need its files, instructions and selected skills. Creating an isolated Git worktree requires confirmation.
Yes. Drag a chat from the sidebar to the left, right, top or bottom of another chat. A preview shows where it will go. Resize the dividers, split areas again or expand one chat and restore the previous layout. Numbers before chat titles match the sidebar. Your arrangement is saved locally for that workspace and window.
Use the workspace icons on the left to see running agents, requests for input and unread results. Select a workspace, then open the conversation you need. Workspace icons keep the order you choose as messages arrive. Delegated subchats stay under their main conversation, with Back at the top when you open one.
Type @ to see work steps and projects. Choose @architect, @ux, @design, @ui, @security or @qa to guide the current agent. A work step does not automatically create another agent. Start a message with a project mention to launch a new chat in that project, including another workspace. Only the new request and explicitly chosen context go with it.
Yes. One Browser panel brings your project’s Preview tab and website tabs together beside the conversation, with an address/search field. Open it from the Browser icon in the toolbar. Standalone chats have website tabs without a project Preview tab. Web navigation accepts safe HTTP(S) addresses, and Browser login sessions are ephemeral.
Yes. All Vortex features are free, with unlimited workspaces, projects, saved chats and connections. Connect your own coding-agent account; that provider controls its subscriptions and usage. Cloud storage and abuse protections still have technical limits.
Local scheduled tasks can reuse a chat with your chosen coding agent, at a daily time and timezone or on an interval. Vortex must be open and your computer awake. Approvals remain in the chat. There are no hosted runners, and failed or interrupted work needs review.
You decide when work is ready. Use the preview, inspect changes and run the checks your project needs. Git push, publishing and deployment are separate actions; an agent finishing a turn is not proof that your app is ready for real users.
THE NEXT PART IS YOURS
Give that idea a place to become something.
Download Vortex, connect an agent and start small.
Apple silicon & Intel
Universal builds support both Macs.
Install on your Windows PC.
Ubuntu / Debian x64 · Install with .deb.
AppImage is available as a portable alternative.
