VORTEXHQ
URL: https://sandbox.smtp.vortexhq.dev
Summary: Vortex is a vibe-coding desktop app: describe an idea to your connected coding agent, build a working website or app, try it in Preview and improve it. Git, databases, APIs, terminals and test mail are available as your project grows.

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 and Kimi Code using the user's provider account
- Multiple account profiles for Codex and Claude Code, with a provider icon and model picker in chat; other providers use their current login
- 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: the project's Preview tab sits next to website tabs, with an address/search field and a single Browser icon in the toolbar
- Saved tools and connections launcher, with supported tools 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, a compact active-chat summary and lighter models for routine assignments from the coordinator's provider and account
- 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

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 or a project 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.
- Chat browser navigation accepts safe HTTP(S) addresses; pages have no Node access or Vortex app bridge. Browser login sessions are ephemeral.

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

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

Practical guides (published public articles only):
- Signals overview: https://sandbox.smtp.vortexhq.dev/docs/signals-overview — Receive application errors and operational signals in a focused Nexus feed.
- Build your first app: https://sandbox.smtp.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.
- Sign in and recover your account: https://sandbox.smtp.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://sandbox.smtp.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://sandbox.smtp.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.
- Import, export and sharing: https://sandbox.smtp.vortexhq.dev/docs/api-import-export-and-sharing — Bring in existing requests, share clusters through Nexus and review proposed changes.
- Build an app that saves data: https://sandbox.smtp.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://sandbox.smtp.vortexhq.dev/docs/project-runtime-and-preview — Start your local app, open Browser and select its Preview tab beside website tabs. Try the requested flow, then save and read back data to check it works.
- Connect what your app needs: https://sandbox.smtp.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://sandbox.smtp.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 Codex: https://sandbox.smtp.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.
- Connect Claude Code: https://sandbox.smtp.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://sandbox.smtp.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://sandbox.smtp.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://sandbox.smtp.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://sandbox.smtp.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://sandbox.smtp.vortexhq.dev/docs/agent-permissions-and-approvals — Choose how much independence an agent should have for this conversation. For a first project, supervised work gives you a chance to review unfamiliar steps as they arise.
- Add an instruction while work continues: https://sandbox.smtp.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://sandbox.smtp.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://sandbox.smtp.vortexhq.dev/docs/linked-project-tasks — Delegate bounded work with lighter models for routine tasks from the same provider. Follow active linked chats together and review their results before continuing.
- Files, editor and change review: https://sandbox.smtp.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://sandbox.smtp.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://sandbox.smtp.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://sandbox.smtp.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://sandbox.smtp.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.
- Speak a message: https://sandbox.smtp.vortexhq.dev/docs/dictation-and-spoken-replies — Speak the next change when it is easier than typing. Ordinary dictation puts recognized text in the draft so you can review it before sending.
- Run a recurring task: https://sandbox.smtp.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://sandbox.smtp.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://sandbox.smtp.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://sandbox.smtp.vortexhq.dev/docs/database-schema-and-diagrams — Column fields, raw defaults, indexes, foreign-key actions, collation, identity reset and diagrams, with engine-specific limits.
- Database import and export: https://sandbox.smtp.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://sandbox.smtp.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://sandbox.smtp.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://sandbox.smtp.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://sandbox.smtp.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://sandbox.smtp.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://sandbox.smtp.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://sandbox.smtp.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?
- Capture an email from your app: https://sandbox.smtp.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://sandbox.smtp.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://sandbox.smtp.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://sandbox.smtp.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://sandbox.smtp.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://sandbox.smtp.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://sandbox.smtp.vortexhq.dev/docs/mcp-share-vortex-tools — Let a supported local external agent use saved developer resources through Vortex. Credentials are resolved by Vortex rather than pasted into the agent’s resource list.
- Continue on another computer: https://sandbox.smtp.vortexhq.dev/docs/cloud-sync-and-device-folders — Continue a project conversation on another computer without confusing synced history with a copied checkout. The local project folder and running processes still belong to their device.
- Understand what is kept: https://sandbox.smtp.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://sandbox.smtp.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://sandbox.smtp.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://sandbox.smtp.vortexhq.dev/docs/settings-and-keyboard-shortcuts — Vortex Search categories, saved connections, workspaces and chats, customizable keyboard shortcuts, clipboard controls and every settings section.
- Install and update Vortex: https://sandbox.smtp.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.
- Get help with a problem: https://sandbox.smtp.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.