Review code and coordinate parallel work
As an app grows, the useful question becomes what changed, why it changed and whether it works with the rest of the project. Vortex keeps files, Git, tests and linked conversations close enough to inspect the evidence before moving on.
Review one change from files to behavior
Begin with the changed-file list, inspect the relevant diff and run the check that covers the intended behavior. Manual commits let you record the changes you select. Automatic commit has stricter clean-checkout, passing-test and unchanged-snapshot conditions and stays opt-in.
Choose shared files or an isolated worktree
Separate chats can share a checkout, or use Project & worktree in the chat menu to choose an isolated working copy. The badges inside Files and Source Control browse projects and active branches without redirecting the chat. A check mark identifies the selected checkout, and panel sizes carry across switches within the workspace. Independent linked tasks can run in the same project checkout, with the coordinator reconciling any shared-file changes. Subchat cards and their history stay under the main conversation; Back at the top returns from an opened subchat. The coordinator resumes after results or attention arrive, and approvals remain with the user.
Repeat local work deliberately
A scheduled task can reuse an ordinary provider chat on a daily timezone-aware time or interval, and an optional check script can start the agent only when there is new work. The app must remain open and the device awake. Review failed or interrupted occurrences before trying again. Scheduling, a completed run and a local commit do not silently authorize deployment.
Follow the detailed guides
- Files, editor 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
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
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.
- Work on separate changes
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
Follow active subchats in a sidebar tree, answer highlighted questions and coordinate up to ten linked tasks with automatic result handoff and cleanup.
- Connect what your app needs
Pin, rename and reorder saved project connections through chat. Open databases and tools beside your work, with the right project and environment.
- Check the app before you publish
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.
- Run a recurring task
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.
- Let a long script finish in the background
Run an authorized project script, keep Vortex open and continue the same chat when the job finishes or fails.
- Inspect tasks and processes
Read local process activity, inspect output, stop a supported task and clear finished entries without deleting its work.
- Use another workspace as reference
Add read-only workspace context for comparison without granting permission to run commands or change the reference files.
- Try a mobile app in an emulator
Prepare Android or iOS simulator tools, choose a device and control a supported mobile app manually or with an agent.