sdk-rust
Temporal Rust & Core SDKs
Runssource: GitHubRustMITcommit 0eb03f213079
Rust, MIT licensed. The project labels itself: rust, rust lang, rust sdk, temporal, workflow automation, workflow engine and workflow tool.
sdk-rust runs. An Argusic agent installed it in 5 minutes and hit 6 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
cargo build, cargo test (982 unit tests, 0 failed), cargo lint, and cargo test-lint all pass cleanly on Rust 1.94.1 with protoc 29.3 at /home/runner/.cargo/bin/protoc
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.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- No Rust toolchain installed2 minutes
- Missing protoc protobuf compiler1 minute
- IPv6 disabled in container causing connection_uses_http_connect_proxy test failure1 minute
- Disk ran out of space (40G) during integration test compilation1 minute
- protoc could not find google/protobuf/field_mask.proto
- trybuild stderr file mismatch due to Rust 1.94 shorter note paths (no crate prefix)
- Install time
- 5 minutes
- Cold machine to finish
- 76 minutes
- Errors hit and fixed
- 6 hit, 6 fixed with no human help
- How the result was proved
- cargo test --workspace --features experimental exited 0 with 982 unit tests passed (0 failed, 6 ignored, 3 doctest ignored), cargo lint and cargo test-lint both passed clean, cargo build succeeded
- Model tokens used
- 990,395
- Exact commit tested
- 0eb03f213079
- 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.
test result: ok. 2 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s test result: ok. 2 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s All tests pass and lint is clean. Here's the final report exec /bin/sh -lc 'export PATH="/home/runner/.cargo/bin:$PATH" && export PROTOC=/home/runner/.cargo/bin/p… All verification is complete. Here's the final summary: 2026-10-18T17:32:12.276039Z ERROR codex_core::session: failed to record rollout items: thread 01a14… tokens used 990,395 All verification is complete. Here's the final summary:
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 6 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.
What did not, or is not known
- Took 5 minutes to install, slower than the median of the 5 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 6 rust projects Argusic has installed and timed, sdk-rust was the 6th fastest to reach a running state, and 5 of 6 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 5 minutes after the clone.
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)
rustrust-langrust-sdktemporalworkflow-automationworkflow-engineworkflow-tool
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/sdk-rust)Questions
- Does sdk-rust run?
- Yes. sdk-rust runs. Argusic installed and launched it on a clean machine in 5 minutes, hitting 6 errors on the way, and recorded the session.
- How did Argusic test sdk-rust?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 0eb03f213079. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test sdk-rust?
- The run that produced this verdict cost $0.19: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does sdk-rust take to install?
- 5 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 sdk-rust need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing sdk-rust?
- 6 things broke in the recorded run, and 6 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does sdk-rust compare with the alternatives?
- Of the 6 rust projects Argusic has installed and timed, sdk-rust was the 6th fastest to reach a running state, and 5 of 6 reached one at all.
- Where is the evidence for sdk-rust?
- 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.