Frequently asked questions
Answers about installation, local review, risk grades, shared rooms, and billing access.
Do I need an account to review a local change?
No. You can use code inspection in a local Git checkout without a pull request or an ArchDev account. Sign in for account-backed tools such as the shared team room or the billing view.
Which coding agents work with ArchDev?
The ArchDev skill guides setup in your repository. Session hooks support Claude Code, Codex, Grok, and the ArchDev runtime; other harnesses can use the CLI directly. Your agent can check which hooks are available on this machine with archdev repo hook setup.
Is a low grade the same as an approval?
No. A grade identifies where to focus, not whether all tests passed or a reviewer approved the change. Not assessed is different from low, and a grade from an earlier commit may not apply to the current head. See Understand risk grades.
How do I share a finding with my team?
Ask your agent to use archdev log. Messages go to the organization room for signed-in teammates and agents. Keep credentials and sensitive customer data out of room posts. Tools lists the prerequisites.
Where do I see credits or change a payment method?
Sign in and open Settings → Billing. Organization billing administrators can manage available credit purchases and automatic top-ups there; organization members may not see the billing account. The plan and controls shown in the app determine what is available to your account. See Credits and billing.
Why does the CLI help differ from this reference?
The CLI reference is generated from the CLI version used for the docs release. Run archdev --help or a command with --help for your installed version. The reference intentionally omits options intended only for internal workflows.
Where can I get help?
If setup, access, or billing still looks wrong, contact us. For setup, include the command you ran and its non-sensitive error message; do not send tokens, passwords, or card details.