Go
A practical first workflow for using NextOS on a project.
This page is the shortest path from install to a useful agent run.
1. Open a project
Use a repository with a clean or understandable working tree.
cd ~/code/my-appnextosThe same runtime is used by the desktop app, web UI, TUI, and CLI. Starting from a project directory lets NextOS discover files, git state, rules, and local config.
2. Initialize context
Ask NextOS to create project instructions:
/initReview the generated AGENTS.md, edit it like any other team document, and commit it. Good instructions reduce repeated prompting.
3. Ask for a plan first
For changes with risk, start with planning:
Inspect the auth flow and propose the smallest change to add password reset.Once the plan is good, ask it to implement. The runtime will show tool calls, file edits, subagent tasks, and permission prompts.
4. Review permissions
When NextOS asks for approval, read the target, command, or tool name. Use allow-once for unfamiliar operations and allow-always only for trusted recurring actions.
5. Finish like normal engineering work
Ask NextOS to run tests, summarize changed files, explain risks, and prepare a commit message. You stay in control of git history.