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 work on the same branch, but they still share a checkout. Use an isolated worktree when independent branches and files matter. Linked project tasks can delegate a bounded assignment and resume the coordinator after results or attention arrive; their 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. 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
- Look at what changed
When the preview looks right, open the files and changes to understand how the agent got there. You can use Vortex through conversation and still review a particular change before keeping it.
- Save a version with Git
A Git commit saves a named version of your project locally. It gives you a concrete point to review later as the app changes.
- 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
Use separate conversations for changes that need their own context. They can share a branch, or you can give one an isolated worktree so the file edits stay separate.
- Coordinate work across projects
A larger idea may involve work in more than one project. Linked tasks let a coordinator assign a bounded piece to another project chat while keeping its progress and result visible.
- Connect what your app needs
An app may need a database, a mail receiver or an API. Connect those resources once, then let the project reuse them without copying passwords into each conversation.
- 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.