VORTEXHQ
URL: https://vortexhq.dev
Summary: Vortex is a desktop workspace and agent harness for managing AI agents, projects, conversations and connected developer tools. Bring your own provider accounts, guide parallel work, inspect results and keep the context and permissions for each task together.

Platforms: macOS (Apple silicon and Intel with a Universal build), Windows, Linux x64 (AppImage and deb). Downloads depend on published package availability.

Current capabilities:
- Local CLI integrations for Codex, Claude Code, Google Antigravity, Grok Build, Kimi Code, Cursor and OpenCode using the user's provider account
- Multiple account profiles for all eight providers, with an explicit provider, account and model choice in chat
- Personal skills library, per-project skills selection and project instructions
- Projects, chats, attachments, runs, approvals and steering
- Chat layout: drag chats left, right, above or below each other with a drop preview, numbered areas and resizable dividers; expand one chat and restore the previous arrangement with drafts preserved
- One Browser panel beside the conversation: app pages and reference websites are ordinary editable, closable tabs, with an address/search field and a single Browser icon in the toolbar
- Saved resources open from Tools in the sidebar or search; Project settings → Connections manages workspace resource pins; supported tools can be docked or floating inside Vortex
- Separate Files and Source Control navigation, grouped file/diff tabs and a movable editor beside or above chat or above/below the tool panel; the terminal stays below the work area
- Linked project task delegation with automatic resume, nested subchat cards with Back navigation and completed-child cleanup after handoff and lighter models for routine assignments from the coordinator's provider and account
- Workspace activity: the left workspace icons show running agents, requests for input and unread results; select a workspace and open its conversation. Your chosen order stays stable as messages arrive.
- Agent access: Auto executes authorized ordinary reads and scoped changes directly; Supervised and Auto-edit ask before native tool changes; Auto-edit can accept local file edits through the provider. Plan is read-only. SQL, shell and FTP root-path guards still apply; device permissions and provider restrictions still apply.
- Workspace rail: manually ordered icons, custom workspace pictures, full-name tooltips and coloured activity; extra workspaces fit behind More above the + button
- App mentions: @architect, @ux, @design, @ui, @security and @qa guide the current agent; a leading project mention launches a separate chat in the selected project, including another workspace
- Local scheduled tasks: daily timezone-aware timing or intervals; Vortex must remain open and the machine awake
- Local preview, project startup, Git, worktrees and configurable autocommit
- Encrypted SQLite workspace storage within the desktop account profile
- SQL, SSH, FTP/FTPS/SFTP, API clusters, test mail and application Signals
- Encrypted workspace records and vault-backed resources, with server-readable ownership and relation metadata
- Local MCP server for supported developer tools and resource discovery
- Connected apps and external MCP server status, refresh and reconnect where supported by the provider

Creative AI and process visibility:
- OpenRouter connects directly with its own API key, account, catalog and usage information; OpenCode installation is not required.
- Direct OpenRouter text chat uses conversation and explicit attachments, without local coding-agent tools.
- Specialized image, video, speech, audio, transcription, embeddings, rerank and decisions models expose controls and input formats according to their capabilities.
- Versions retain each generation and its inputs. Selecting a version does not alter a draft; Use inputs prepares it, and Generate version submits a new request.
- Compatible models support independent First frame, Last frame, Images, Video and Audio inputs. Originals stay intact when preparing model-compatible image copies.
- Extend video requires an eligible completed job, model and the same provider account. An uncertain paid submission is not automatically repeated.
- Resource Manager shows local tasks and processes with available CPU/memory readings, detailed results and scoped stop actions. Clearing finished entries preserves chats, files and results.
- Local files, Git diffs and history remain readable offline. Remote checks and cloud operations still require connectivity.

Using Vortex:
- All Vortex features are free, including encryption, MCP, local schedules and linked tasks.
- Unlimited workspaces, projects, saved chats and saved connections.
- Technical cloud storage, retention, rate and abuse limits remain. AI accounts and usage belong to the user's chosen provider.

Boundaries:
- No hosted Vortex agent, included AI-token pool or remote schedule execution.
- Cloud mail, Signals and server-processed service data are not universally end-to-end encrypted.
- Plain chats have no project settings. Creating a worktree requires confirmation.
- Standalone chats keep Browser on the right without project settings. App pages use their actual URL, not a reserved Preview tab.
- Chat layouts are saved locally per workspace and window, not cloud-synchronized. Closing a chat area does not delete its conversation.
- Files and Source Control show project and active, unmerged worktree badges inside each panel below its heading. Folder/fork icons, a selection check and palette-aware colours identify the checkout; inactive badges are muted.
- Browsing a repository does not change a chat’s starting folder. Chat menu → Project & worktree… selects the starting project and working copy for its next message while idle. Existing terminals keep their folders.
- Tool-panel widths, editor dimensions and terminal height carry across project/worktree switches within the same workspace and window on the device. Files, drafts and terminal sessions remain associated with their project.
- Fast mode starts off in new chats and is disabled for linked tasks. Complex assignments require a reason to retain the coordinator's stronger model; provider usage still applies.
- Work steps do not automatically create sub-agents or expand permissions. Project mentions carry the new prompt and explicitly selected attachments/context, not the source conversation’s history or provider session.
- Independent linked tasks can run in parallel in the same checkout; the coordinator must reconcile shared-file changes. The current local scheduler allows two active linked tasks alongside the parent, while each chat processes its own messages serially.
- Chat browser navigation accepts safe HTTP(S) addresses; pages have no Node access or Vortex app bridge. Named browser profiles retain website logins locally per Vortex account. Agent Browser Use controls access to ordinary websites; configured local app preview remains available with it off.

Common searches this product answers:
- Postman alternative: https://vortexhq.dev/postman-alternative
- Insomnia alternative: https://vortexhq.dev/insomnia-alternative
- Termius alternative: https://vortexhq.dev/termius-alternative
- PuTTY alternative: https://vortexhq.dev/putty-alternative
- Mailtrap alternative: https://vortexhq.dev/mailtrap-alternative
- SQLAce alternative: https://vortexhq.dev/sqlace-alternative
- Sequel Ace alternative: https://vortexhq.dev/sequel-ace-alternative
- TablePlus alternative: https://vortexhq.dev/tableplus-alternative
- phpMyAdmin alternative: https://vortexhq.dev/phpmyadmin-alternative
- FileZilla alternative: https://vortexhq.dev/filezilla-alternative
- Cyberduck alternative: https://vortexhq.dev/cyberduck-alternative

Primary pages:
- Homepage: https://vortexhq.dev/
- Documentation: https://vortexhq.dev/docs
- Roadmap: https://vortexhq.dev/roadmap
- Contact & feedback: https://vortexhq.dev/contact
- Full machine-readable profile: https://vortexhq.dev/llms-full.txt

Practical guides (published public articles only):
- Build your first app: https://vortexhq.dev/docs/getting-started-vortex — Start with a small idea you can describe in a few sentences. In this guide, you will ask a coding agent to create a simple article website, open it inside Vortex and make one change. You can follow the steps without writing code.
- Signals overview: https://vortexhq.dev/docs/signals-overview — Receive application errors and operational signals in a focused Nexus feed.
- Sign in and recover your account: https://vortexhq.dev/docs/account-sign-in-and-recovery — Your Vortex account owns your cloud resources. It is separate from the coding-agent account you connect to build an app.
- Unlock your saved work: https://vortexhq.dev/docs/vault-setup-unlock-and-recovery — Unlock the Vault to use protected saved resources and encrypted workspace sync. Its password and recovery material are separate from the ordinary login session.
- Give your app a home: https://vortexhq.dev/docs/workspaces-and-projects — Organize project folders in workspaces. Switch project and worktree badges, recognize the selected checkout and keep panel sizes while browsing.
- Build an app that saves data: https://vortexhq.dev/docs/create-laravel-react-project — Turn Small Stories into an app whose articles are stored and read back. This walkthrough adds persistence to the first-app guide, using Vortex’s supported Laravel + React starter.
- Run your app and try it: https://vortexhq.dev/docs/project-runtime-and-preview — Choose the project in Play or Preview, start its local app and verify the actual page, including saved data and background services.
- Browser tabs, profiles and agent access: https://vortexhq.dev/docs/browser-profiles-and-agent-access — Browse beside chat, save website logins in device-local profiles, import cookies and control agent access to website tabs.
- Try a mobile app in an emulator: https://vortexhq.dev/docs/mobile-emulator — Prepare Android or iOS simulator tools, choose a device and control a supported mobile app manually or with an agent.
- Connect what your app needs: https://vortexhq.dev/docs/project-environments-and-resources — Pin, rename and reorder saved project connections through chat. Open databases and tools beside your work, with the right project and environment.
- Chats, drafts and layouts: https://vortexhq.dev/docs/conversations-and-drafts — Choose project context, arrange chats by dragging, resize areas, expand and restore layouts, and understand every main composer control.
- Connect Cursor: https://vortexhq.dev/docs/connect-cursor — Install Cursor, connect a provider account and use it for a project conversation with approvals and review.
- Connect OpenCode: https://vortexhq.dev/docs/connect-opencode — Connect a local OpenCode coding agent to its API provider and distinguish it from direct OpenRouter generation.
- Connect OpenRouter directly: https://vortexhq.dev/docs/connect-openrouter — Connect your own OpenRouter account for direct text chat and specialized image, video and audio models.
- Generate images, video and audio: https://vortexhq.dev/docs/generate-images-video-and-audio — Choose a model, prepare independent frames and references, generate a result and inspect or download it.
- Versions, references and video extensions: https://vortexhq.dev/docs/generation-versions-and-references — Revisit saved generations, reuse their inputs and extend eligible videos with deliberate new submissions.
- Find or recover a conversation: https://vortexhq.dev/docs/find-and-recover-chats — Find a saved conversation across workspaces or preview and restore available local backup and provider history.
- Connect Codex: https://vortexhq.dev/docs/connect-codex — Connect a Codex account profile and choose it for a conversation. Keep multiple provider profiles distinct from your Vortex sign-in.
- Use GPT through an SSH server: https://vortexhq.dev/docs/gpt-through-ssh — For enabled accounts, connect a Linux server, complete the supported provider sign-in and choose the GPT through SSH account in chat.
- Connect Claude Code: https://vortexhq.dev/docs/connect-claude-code — Connect a Claude Code account profile and choose it for a conversation. Keep multiple provider profiles distinct from your Vortex sign-in.
- Connect Google Antigravity: https://vortexhq.dev/docs/connect-google-antigravity — Connect Google Antigravity, then choose it for a conversation. The provider's current login is separate from your Vortex sign-in.
- Connect Grok Build: https://vortexhq.dev/docs/connect-grok-build — Connect Grok Build, then choose it for a conversation. The provider's current login is separate from your Vortex sign-in.
- Connect Kimi Code: https://vortexhq.dev/docs/connect-kimi-code — Connect Kimi Code, then choose it for a conversation. The provider's current login is separate from your Vortex sign-in.
- Choose a model and read its usage: https://vortexhq.dev/docs/models-and-provider-usage — Choose the provider account and model for each conversation. Fast mode starts off in new chats; read provider usage separately from conversation context.
- Choose what your agent can do: https://vortexhq.dev/docs/agent-permissions-and-approvals — Auto runs authorized ordinary reads and scoped changes directly through native tools. Learn how provider file edits, tool confirmations and read-only Plan mode differ.
- Add an instruction while work continues: https://vortexhq.dev/docs/steer-and-queue-messages — You can add a detail while your agent is working. Keep the new instruction specific enough that the agent can tell whether it changes the current task or comes next.
- Work on separate changes: https://vortexhq.dev/docs/parallel-chats-and-worktrees — Choose the main folder or an isolated Git worktree for each chat. Keep browsing separate from chat context, review changes and merge when ready.
- Coordinate work across projects: https://vortexhq.dev/docs/linked-project-tasks — Follow active subchats in a sidebar tree, answer highlighted questions and coordinate up to ten linked tasks with automatic result handoff and cleanup.
- Workspace activity and project mentions: https://vortexhq.dev/docs/work-dashboard-and-app-mentions — Follow active agents and unread results by workspace, open the relevant chat, and start a separate project conversation with a leading mention.
- Use another workspace as reference: https://vortexhq.dev/docs/workspace-reference-context — Add read-only workspace context for comparison without granting permission to run commands or change the reference files.
- Files, editor and change review: https://vortexhq.dev/docs/files-and-change-review — Choose project and worktree badges, review grouped file and diff tabs, preserve unsaved edits and reuse panel sizes across the workspace.
- Save a version with Git: https://vortexhq.dev/docs/git-and-manual-commits — Choose the exact project or worktree, review its changed files, stage a focused change and save a local Git commit before deciding what to publish.
- Let a checked change be committed: https://vortexhq.dev/docs/automatic-commit — Automatic commit is an explicit opt-in for a checked agent change. Use it when the project has meaningful tests and you want a successful task recorded as a local Git commit.
- Check the app before you publish: https://vortexhq.dev/docs/checks-and-publishing — Try the behavior you wanted before deciding the app is ready. “The process started” and “the page loaded” are useful checks, but neither proves that a person can complete the intended task.
- Show the agent what you mean: https://vortexhq.dev/docs/attachments-and-images — A screenshot or sketch can explain a design change better than a paragraph. Attach it to the draft or conversation, then say which part the agent should use.
- Dictate a message or talk with Voice: https://vortexhq.dev/docs/voice-dictation-and-conversations — Use local or cloud dictation, choose a conversation voice, configure start and stop phrases, and manage microphone access in Settings → Voice.
- Let a long script finish in the background: https://vortexhq.dev/docs/background-scripts-and-results — Run an authorized project script, keep Vortex open and continue the same chat when the job finishes or fails.
- Run a recurring task: https://vortexhq.dev/docs/local-scheduled-tasks — Give a recurring task a regular place in your day. Scheduled work uses your connected coding agent and a normal project chat on this computer.
- Open your app's database: https://vortexhq.dev/docs/database-first-connection — Open the data behind the app you are building. If Small Stories saves articles, Database lets you see those stored titles rather than relying only on the page.
- Read and change saved data: https://vortexhq.dev/docs/database-queries-and-data — Use a table view for a quick inspection, or SQL when you need a more specific question. Both operate on the database connection you selected.
- Database structure and relationships: https://vortexhq.dev/docs/database-schema-and-diagrams — Column fields, raw defaults, indexes, foreign-key actions, collation, identity reset and diagrams, with engine-specific limits.
- Inspect tasks and processes: https://vortexhq.dev/docs/resource-manager — Read local process activity, inspect output, stop a supported task and clear finished entries without deleting its work.
- Database import and export: https://vortexhq.dev/docs/database-import-and-export — SQL, CSV and JSON exports: structure, content, DROP statements, BLOBs, batching, concurrency, compression and import checks.
- Connect to a server: https://vortexhq.dev/docs/ssh-hosts-and-keys — Open a terminal on a server you control when your project needs remote work. A local project shell and an SSH session run on different machines; keep that distinction visible.
- Reach a server-side service: https://vortexhq.dev/docs/ssh-tunnels-and-project-tools — A tunnel lets a local tool reach a service through an SSH server. Use it when the database should not be directly exposed to your computer’s network.
- Move files to and from a server: https://vortexhq.dev/docs/ftp-sftp-connections-and-transfers — Use the file-transfer workspace to browse a server and move selected files. Choose the protocol the server actually supports: FTP, FTPS or SFTP.
- Edit a remote file: https://vortexhq.dev/docs/remote-file-editing-and-permissions — For a small server-file change, open the file, edit it locally through the supported workflow and let the tracked upload return the saved change.
- API requests and collections: https://vortexhq.dev/docs/api-first-request-and-collections — Understand method, URL, parameters, headers, body, auth, cookies, send, cancel and save with a working sample request.
- API environments and authentication: https://vortexhq.dev/docs/api-environments-and-authentication — Configure variables, inherited auth, bearer/basic credentials and every OAuth field, including token refresh and workspace sharing.
- Check an API response: https://vortexhq.dev/docs/api-scripts-tests-and-responses — Use the response to answer a concrete question: did the service return the right data, and does it behave correctly when the input changes?
- Reuse API collections: https://vortexhq.dev/docs/api-import-export-and-sharing — Reuse requests you already have, then check their targets and credentials before running them. Importing a collection is not permission to send every request in it.
- Capture an email from your app: https://vortexhq.dev/docs/mail-local-smtp-setup — Catch an email from your development app before you send real messages. Vortex Mail is a test-email receiver, not a replacement for a personal IMAP inbox.
- Capture test mail through cloud SMTP: https://vortexhq.dev/docs/mail-cloud-smtp — Cloud SMTP capture is useful when the test app cannot reach your computer’s local receiver. Create a credential for that app, then find its captured messages in Vortex.
- See what a test email looks like: https://vortexhq.dev/docs/mail-inspection-and-checks — Check the actual email your app produced: its wording, layout, text alternative and attachments. Select the message and confirm whether it came from local or cloud capture.
- Bring an app event into Vortex: https://vortexhq.dev/docs/signals-create-and-integrate — Bring an application event into Vortex so you and your agent can inspect what happened. Start with a deliberate test event before depending on the feed for real errors.
- Find the event that needs attention: https://vortexhq.dev/docs/signals-events-sharing-and-notifications — Use the feed to find the event that explains a broken app flow. Unread attention and total stored history are different counts.
- Add tools to a conversation: https://vortexhq.dev/docs/mcp-tools-for-chats — Use built-in project and connection tools in Vortex chats, or add an external MCP server. Discover tools, check status and verify the result.
- Let an agent use Vortex tools: https://vortexhq.dev/docs/mcp-share-vortex-tools — Let a supported local external agent use saved developer resources through Vortex. Scoped operations follow the external confirmation setting, with additional SQL, shell and FTP root-path guards.
- Continue desktop conversations from your phone: https://vortexhq.dev/docs/remote-phone-connection — Pair Vortex Mobile by QR code, answer desktop agents from your phone and remove a device’s access when needed.
- Continue on another computer: https://vortexhq.dev/docs/cloud-sync-and-device-folders — Continue synchronized history with a local checkout and provider account on each computer, without overwriting another device’s choices.
- Understand what is kept: https://vortexhq.dev/docs/storage-retention-and-deletion — Your app’s files, Vortex conversation history and captured cloud content have different lifetimes. Choose the operation that matches what you want to remove.
- Using Vortex and understanding its limits: https://vortexhq.dev/docs/free-pro-and-resource-counting — Use every Vortex feature with unlimited workspaces, projects, saved chats and connections. Understand the separate boundaries of cloud storage and your coding-agent account.
- Account access and troubleshooting: https://vortexhq.dev/docs/billing-payments-and-downgrade — Find the right next step for sign-in, Vault unlock, project folders, provider usage and saved-resource access without deleting your work.
- Settings and keyboard shortcuts: https://vortexhq.dev/docs/settings-and-keyboard-shortcuts — Find AI providers, Voice, Browser, Remote, Computer use, permissions, personal skills, notifications and keyboard shortcuts.
- Install and update Vortex: https://vortexhq.dev/docs/updates-and-downloads — Install Vortex on macOS with Apple silicon or Intel, Windows, or Linux x64. Choose an available Universal DMG, Windows installer, AppImage or deb, and keep your saved work when updating.
- Computer use and system permissions: https://vortexhq.dev/docs/computer-use-and-system-permissions — Choose app access and saved permissions, check operating-system requirements and verify agent actions on your computer.
- Get help with a problem: https://vortexhq.dev/docs/support-and-bug-reports — A useful report tells us what you tried, what happened and what should have happened. Start with one reproducible problem so the result is easy to check.