Qoder CLI Guide
Qoder’s terminal agent for project exploration, coding, review and persistent instructions.
Last verified: · How we verifySuitable workflows
Qoder users who prefer a terminal workflow without launching the IDE.
Limitations and billing
Native installation is now preferred over legacy npm; Windows ARM64 is not supported in the checked guide.
Capabilities we verified
This is an evidence-based shortlist, not an exhaustive feature inventory. Omitted capabilities have not been checked for this record.
Pricing & usage
See official pricing
Qoder plan and Credits usage. The cost of metered usage or an external agent can be separate from the subscription.
Check official pricing ↗Models & access
Model access and Credits depend on your Qoder account and selected mode.
Official model information ↗Install and start the CLI
macOS, Linux or Windows x64; the native installer avoids the legacy Node.js dependency.
Installation command · macOS / Linux
curl -fsSL https://qoder.com/install | bashOpen your project folder in a terminal, then run:
qoderAccount and authentication
Launch qoder and follow the first-run sign-in flow; /status shows account and connectivity details.
Project configuration and tools
Use /init for AGENTS.md, /review for local changes and /usage to inspect Credits.
First task to try
Map the project, implement a small tested change, then review it before committing.
Official configuration reference ↗Related CLI tools
All AI CLI tools →
Project evaluation checklist
- Open a small, familiar project and confirm that your essential language tooling works.
- Give the agent one bounded change with an observable acceptance criterion.
- Review the diff, run the project’s checks and compare the result with your current workflow.
- Inspect usage after the task. Estimate a month of similar work, including any separate model or agent bill.