grok-reg-tool
可自部署的 Grok 注册机 Web 控制台,支持 Docker、DrissionPage 自动化、邮件后端配置和本地账号号池管理。
Runs with mockssource: GitHubTypeScriptMITcommit d609705f536d
TypeScript, MIT licensed. The project labels itself: account pool, automation, docker, docker compose, drissionpage, grok, grok registration and self hosted.
grok-reg-tool runs, with stand-ins for the services it depends on. An Argusic agent installed it in 15 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The web console builds, serves its UI, and answers all API endpoints with the schema-correct mock mail backend; the Python register flow launches Chromium and extracts verification codes but stops because x.ai's sign-up page reports email sign-up is unavailable, so no account or SSO was produced.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 92 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Registration round aborted with 'page was refreshed' when the OTP page reloaded between fill and click6 minutes
- /usr/bin/chromium and /usr/bin/chromium-browser absent, so DrissionPage had no browser to launch5 minutes
- python3 -m pip install --user -r register/requirements.txt blocked by PEP 668 (externally-managed-environment)3 minutes
- Local server defaults pythonPath to /usr/local/bin/python3, which does not exist here2 minutes
- Install time
- 15 minutes
- Cold machine to finish
- 16 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- npm install, npm run typecheck, npm run server:build exited 0 on a clean tree; npm run server:start then curl GET / returned 200, POST /api/auth/login returned 200, /api/system/health 2/2 ok, /api/system/version 0.1.2; Chromium login rendered the dashboard; python3 register/runner.py --count 1 against a mock /admin/new_address API launched Chromium, created a mailbox, extracted code AB1-CD2 and filled x.ai's sign-up form
- Model tokens used
- 464,922
- Exact commit tested
- d609705f536d
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
- `npm run server:start` on a fresh data dir: `GET /` returned 200, unauthenticated `/api/settings`… - Auth (change password, 401 on the WebSocket without a cookie, 200 with one), settings read/write,… - UI in a real Chromium on the Xvfb display: login rendered the dashboard with 2/2 health and v0.1.… - Python side: dependencies installed in a venv; `python3 register/runner.py --count 1` launched Ch… **Where it stops** - x.ai's sign-up page itself says "Email sign-up isn't available right now. Sign up another way.", … **Errors found and fixed** - System `pip install` was blocked by PEP 668 → use a venv, and the README now says so. - No Chromium in the container → installed Playwright's Chromium into the user cache; the script no… - A page reload during OTP entry aborted the whole round → fill/click now retry after re-acquiring … - A `.env.example` pointing at `/usr/local/bin/python3` isn't used by the local server. Runtime artifacts (`out/`, `node_modules/`, `register/logs/`, `config.json`) are left in place; onl…
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Installed in 15 minutes.
- Recovered from all 4 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.17 |
Topics (from GitHub)
account-poolautomationdockerdocker-composedrissionpagegrokgrok-registrationself-hostedwebuixai
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/grok-reg-tool)Questions
- Does grok-reg-tool run?
- grok-reg-tool runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 15 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test grok-reg-tool?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit d609705f536d. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test grok-reg-tool?
- The run that produced this verdict cost $0.17: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does grok-reg-tool take to install?
- 15 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does grok-reg-tool need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing grok-reg-tool?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for grok-reg-tool?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.