Documentation
progrok documents one operating model: activate your xAI OAuth session once, then use that session through a local OpenAI-compatible proxy and direct Grok tool commands. The docs are organized around that bridge, not around API keys.
Read this first
If you are evaluating progrok, start with the OAuth bridge page. It explains why Hermes Agent, OpenClaw, Grok Build-style workflows, and progrok all care about the same OAuth session pattern.
Core path
| Step | Page | What it answers |
|---|---|---|
| 1 | OAuth bridge | What progrok is, why OAuth matters, and what “tool activation” means. |
| 2 | Quick Start | How to install, login, run the proxy, and call Grok from a client. |
| 3 | Login | Browser login, device-code login, stored credential path, and validation. |
| 4 | Proxy | How placeholder keys become OAuth-backed upstream requests. |
| 5 | Tools overview | Which proxy tools and direct CLI commands are activated by the session. |