Getting started
The recommended path is deliberately short: authorize the CLI once, then run one guided command in each repository. NEPOPSX detects the stack, tailors the entitled agent, and renders provider-ready files.
1. Install the CLI
Create or sign in to your NEPOPSX account first. Then install the CLI globally if you want the nepopsx command available in every repository. You can also use npx @nepopsx/cli without a global install.
2. Connect this machine
login starts device authorization. Approve the short-lived code in your browser and the CLI stores the machine credential locally. Use --no-browser on a remote shell to print the URL and code instead of opening a browser.
3. Set up a repository
Run up at the repository root. It confirms the workspace name, detects services, resolves the agent included with your plan, lets you pick which editors to render for (GitHub Copilot, Claude Code), and guides tailoring through Copilot or Claude. Your editor choice is saved to workspace.yaml, so re-runs never ask again. It is resumable and safe to run repeatedly.
4. Review what changed
Before later syncs, use preview mode to inspect a unified diff without writing files. In CI, add --exit-on-changes to fail when generated state has drifted.
Explicit / headless setup
Use individual commands when you need more control than up. Login with --no-browser on a remote shell, then use up --system for a non-interactive install (no LLM tailoring), followed by workspace enrich if you have a key available.
The current CLI does not expose an init or activate command. Older setup guides that reference them are stale — use nepopsx up instead.