meilisearch-rust
Rust wrapper for the Meilisearch API.
Runssource: GitHubhomepageRustMITcommit 14008e4aa077
Rust, MIT licensed. The project labels itself: crate, meilisearch, rust, sdk, search engine and wasm.
meilisearch-rust runs. An Argusic agent installed it in 2.5 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.
Installed Rust 1.99.1, the meilisearch-sdk v0.33.0 crate compiles, and all 194 unit tests pass against a local Meilisearch v1.55.0 server.
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
- 3 minutes
- Cold machine to finish
- 8 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- cargo test --lib exited 0, 194 passed, 0 failed
- Model tokens used
- 330,605
- Exact commit tested
- 14008e4aa077
- 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.
tokens used
330,605
All tests pass. The key findings:
1. **Rust wasn't installed** — installed via rustup (rustc 1.99.1)
2. **Meilisearch server required** — no Docker available, downloaded the binary directly from GitHu…
3. **IPv6 localhost issue** — initial server started on `0.0.0.0:7700` but the test binary resolved…
4. **API key mismatch** — the test macro's default key is `masterKey` (hardcoded in `option_env!("M…
5. **Stale auth state** — after earlier server runs with different keys, `data.ms` persisted auth; …
6. **Server persistence** — the PTY-based long-running session kept the server alive across separat…
**All 194 tests passed** against a real Meilisearch v1.55.0 server. No code changes or mocks were n…
2026-10-21T17:10:23.018706Z ERROR codex_core::session: failed to record rollout items: thread 01a15…
2026-10-21T17:10:23.018794Z ERROR codex_core::session: failed to record rollout items: thread 01a15…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.
- Installed in 2.5 minutes.
- Nothing broke on the way: zero errors between clone and running.
- 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
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
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 2.5 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)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/meilisearch-rust)Questions
- Does meilisearch-rust run?
- Yes. meilisearch-rust runs. Argusic installed and launched it on a clean machine in 3 minutes, hitting 0 errors on the way, and recorded the session.
- How did Argusic test meilisearch-rust?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 14008e4aa077. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test meilisearch-rust?
- 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 meilisearch-rust take to install?
- 2.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 meilisearch-rust need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing meilisearch-rust?
- Nothing did, in the recorded run: zero errors between clone and running.
- Where is the evidence for meilisearch-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.