Using Vortex and understanding its limits

3 minute read · Account usage

Vortex is free to use. Workspaces, projects, saved conversations and saved connections have no product count limits. Preview, Git, developer tools, local schedules, encryption and MCP are included. You choose and connect your own coding-agent account.

• Organize work in a way that fits the project
• Use tools and saved connections
• Understand your coding-agent account
• Keep cloud storage useful
• Choose the right next step

Organize work in a way that fits the project#

Create a workspace for related project folders and a conversation for each useful thread of work. You can keep a small first app in one chat or coordinate changes across several projects. Starting another chat does not copy a checkout. Archiving a conversation keeps its history; permanent deletion is a separate action.

Use a worktree when one task needs an isolated branch and files. Review how its changes should return to the main project before finishing it. A local schedule reuses its own ordinary conversation so you can inspect previous results and approvals. See workspaces, worktrees and schedules.

Use tools and saved connections#

Save SQL, SSH, FTP/SFTP, API, SMTP and Signal resources as needed. Reuse the intended connection in another project instead of pasting its credentials into a prompt. Opening multiple sessions does not require creating multiple saved profiles.

The correct account, Vault unlock and resource permissions are still required. A saved connection gives Vortex the means to reach a service; it does not authorize every database write, remote command or outbound request. Review the target and operation before a consequential change. These access rules apply equally to manual work and agent-assisted work.

Understand your coding-agent account#

Your connected provider controls its own account eligibility, models, subscriptions and usage. Vortex does not supply an AI account or included AI tokens. A provider quota error means you should inspect that provider's reported window and reset time, not delete Vortex chats.

Use the usage display where the provider reports trustworthy information. Unknown or unreported limits do not mean unlimited usage. A model's context window is also different from an account's time-based allowance. Models and provider usage explains those distinctions.

Keep cloud storage useful#

Optional cloud history, attachments, captured mail and Signals use storage with technical ceilings and rate protection. They are not an unlimited archive. Retention considers eligible inactive content within its own account and category, while active work stays protected. Saved project folders and credentials are not removed to free message storage.

When a limit or sync error appears, read the actual category and message. Keep local pending changes safe, check connection and Vault state and resolve a conflict before retrying. Repeated retries do not repair a full content category or a competing run on another device. See storage and deletion and sync.

Choose the right next step#

Start with your first app if you are exploring. For a saved resource you cannot access, follow account access and troubleshooting. Include the action and exact visible error in a support report; never send a password, private key, session token or full recovery link.