rocketride-server

RocketRide is an open source AI meta-harness with the only enterprise-grade runtime built on C++. Build, test and publish durable agents that scale in production.

Runssource: GitHubPythonMITcommit 37b5dd25af12

Python, MIT licensed. The project labels itself: agent framework, agent harness, agent orchestration, agentic ai, ai agents, ai observability, cpp and document processing.

rocketride-server runs. An Argusic agent installed it in 18 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

The prebuilt RocketRide engine (v3.6.0.38) runs as a WebSocket server on port 5565, the Python client SDK (v1.6.0) installs and connects to it successfully, and the SDK's test suite executes real pipeline operations (launch/terminate/stream data/service discovery) against the engine.

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 75 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
75 / 100
cost of the verifying run
$0.28 (measured)
recorded runs
2
last tested
stars
20,008
forks
0
open issues
0
watchers
0
created
-
last push
-

Subject data from GitHub, linked at the top of this page. 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.

Time lost to each failure while testing rocketride-server, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • server:build failed because system packages (zip, unzip, ninja-build, libc++1, etc.) require root5 minutes
  • LLVM/clang 18 tarball URL discovery via GitHub API hit rate limit — manually downloaded to ~/toolchains/llvm-183 minutes
  • Engine finds local source paths and fails when run from inside the repo checkout3 minutes
  • pnpm install required but pnpm not in PATH — installed via npm with --prefix1 minute
  • Engine's bundled depends.py needed uv binary in exec_dir/bin/uv1 minute
Install time
18 minutes
Cold machine to finish
22 minutes
Errors hit and fixed
5 hit, 5 fixed with no human help
How the result was proved
Started engine from /tmp/rr-test (./engine ./ai/eaas.py --host=127.0.0.1), verified HTTP 200 on GET /, then ran 778 pytest cases against the live WebSocket server: 763 passed, 2 failed, 7 skipped, 6 errors, 539 subtests passed
Model tokens used
280,995
Exact commit tested
37b5dd25af12
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.

- Engine started and answered HTTP 200 on `GET /` ✓
- Python test suite ran against the live engine: **763 passed, 2 failed, 7 skipped, 6 errors** acro…
The 2 failures are minor engine-version gaps (prebuilt engine is v3.6.0.38, SDK is v1.6.0 — slightl…
tokens used
280,995
Let me compile the final results. Here's what we accomplished:
- Installed Node/Python dependencies, built TypeScript client SDK ✓
- Installed Python SDK via pip ✓
- Manually downloaded prebuilt C++ engine from GitHub releases ✓
- Engine started and answered HTTP 200 on `GET /` ✓
- Python test suite ran against the live engine: **763 passed, 2 failed, 7 skipped, 6 errors** acro…
The 2 failures are minor engine-version gaps (prebuilt engine is v3.6.0.38, SDK is v1.6.0 — slightl…

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.
  • Recovered from all 5 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Ran without a GPU, so it does not need one to start.
  • Licensed MIT, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

What did not, or is not known

  • Took 18 minutes to install, slower than the median of the 63 comparable projects Argusic has measured.

Of the 64 agent-framework projects Argusic has installed and timed, rocketride-server was the 57th fastest to reach a running state, and 51 of 64 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.

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 byattemptoutcomescorecost USDwhen
Argusic Runner2/3Did not run50.000.08
Argusic Runner1/3Runs100.000.28

Topics (from GitHub)

agent-frameworkagent-harnessagent-orchestrationagentic-aiai-agentsai-observabilitycppdocument-processingllmllmopsmcpmcp-servermeta-harnessmodel-context-protocolopen-sourceragself-hostedvisual-programmingvscode-extensionworkflow-engine

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/rocketride-server.svg)](https://argusic.com/subject/rocketride-server)

Questions

Does rocketride-server run?
Yes. rocketride-server runs. Argusic installed and launched it on a clean machine in 18 minutes, hitting 5 errors on the way, and recorded the session.
How did Argusic test rocketride-server?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 37b5dd25af12. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test rocketride-server?
The run that produced this verdict cost $0.28: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does rocketride-server take to install?
18 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 rocketride-server need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing rocketride-server?
5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does rocketride-server compare with the alternatives?
Of the 64 agent-framework projects Argusic has installed and timed, rocketride-server was the 57th fastest to reach a running state, and 51 of 64 reached one at all.
Where is the evidence for rocketride-server?
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.

Discussion