rakazo
Open-source Grok Bot alternative. Choose your own model and sandbox.
Runssource: GitHubhomepageTypeScriptApache-2.0commit ed2cfb5cafa2
TypeScript, Apache-2.0 licensed. The project labels itself: ai agents, chatgpt, docker, electron, expo, grok, llm and self hosted.
rakazo runs. An Argusic agent installed it in 9 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.
Node 22.23.2 + pnpm 9.15.0 installed; all 1853 npm packages resolved and linked; Prisma client generated; full TypeScript/Vite/Electron/Astro build completes cleanly; all 282 unit-test files pass (2605 tests); Electron 43.4.0 launches on the virtual display and stays up.
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 100 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.
- Install time
- 9 minutes
- Cold machine to finish
- 9 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- pnpm test: 282 test files passed, 2605 tests passed, 0 failed (exit 0); pnpm build: 5 turbo tasks succeeded; electron . --no-sandbox: process stayed alive for 10s timeout on DISPLAY=:99 (Xvfb), exit code 124 (SIGTERM from timeout)
- Model tokens used
- 73,758
- Exact commit tested
- ed2cfb5cafa2
- 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
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
/usr/bin/bash: line 1: vitest: command not found
exec
/usr/bin/bash -lc 'export NVM_DIR="$HOME/.nvm"; . "$NVM_DIR/nvm.sh"; cd /work/repo && npx vitest ru…
succeeded in 42931ms:
Test Files 282 passed | 19 skipped (301)
Tests 2605 passed | 110 skipped (2715)
Start at 01:23:41
Duration 42.57s (transform 4.67s, setup 1.32s, import 74.58s, tests 19.09s, environment 20ms)
All data collected. Here's the final report:
tokens used
73,758
All data collected. Here's the final report: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
- Reached a running state on a clean machine, with the session recorded.
- Nothing broke on the way: zero errors between clone and running.
- Ran without a GPU, so it does not need one to start.
- Licensed Apache-2.0, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Took 9 minutes to install, slower than the median of the 11 comparable projects Argusic has measured.
Of the 12 ai-agents projects Argusic has installed and timed, rakazo was the 8th fastest to reach a running state, and 8 of 12 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 9 minutes after the clone.
- Following its own README: the documented path worked with nothing to fix.
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
Topics (from GitHub)
ai-agentschatgptdockerelectronexpogrokllmself-hostedtypescript
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/rakazo)Questions
- Does rakazo run?
- Yes. rakazo runs. Argusic installed and launched it on a clean machine in 9 minutes, hitting 0 errors on the way, and recorded the session.
- How did Argusic test rakazo?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit ed2cfb5cafa2. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test rakazo?
- The run that produced this verdict cost $0.04: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does rakazo take to install?
- 9 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 rakazo need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing rakazo?
- Nothing did, in the recorded run: zero errors between clone and running.
- How does rakazo compare with the alternatives?
- Of the 12 ai-agents projects Argusic has installed and timed, rakazo was the 8th fastest to reach a running state, and 8 of 12 reached one at all.
- Where is the evidence for rakazo?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.