meilisearch-ui
😎 Open-source, pretty, simple and fast ⚡ Meilisearch admin dashboard UI for managing your meilisearch instances 🕹
Runs with mockssource: GitHubhomepageTypeScriptApache-2.0commit ed8a2da42e12
TypeScript, Apache-2.0 licensed. The project labels itself: admin, admin dashboard, admin panel, console, dashboard, hacktoberfest, meilisearch and meilisearch dashboard.
meilisearch-ui runs, with stand-ins for the services it depends on. An Argusic agent installed it in 45 minutes and hit 8 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The repo installs with pnpm, passes pnpm lint and pnpm build:safe, and the built SPA runs with the dev server, preview server, and in a headless browser, rendering instance/index/documents/tasks/keys screens from a mocked Meilisearch API with zero browser errors.
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 86 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.
- tsc: ECharts pie used legacy itemStyle.normal (removed in ECharts v5 types)12 minutes
- Mock Meilisearch: CORS preflight rejected x-meilisearch-client header8 minutes
- Mock Meilisearch: /indexes/{uid}/search returned 404; Documents tab showed 0 hits8 minutes
- Playwright requires Node >=20 but container has Node 18.19.15 minutes
- tsc: Total.tsx passed count:string to i18next (expects number)4 minutes
- Biome lint: node: protocol missing in scripts/post-build.js (3 errors)3 minutes
- Install time
- 45 minutes
- Cold machine to finish
- 23 minutes
- Errors hit and fixed
- 8 hit, 8 fixed with no human help
- How the result was proved
- headless Chromium loaded http://localhost:24900/ - nav 200, redirected to /ins/0 dashboard showing Status Available, Instance DB Size 1.02 kB, Meilisearch Version 1.9.0, index movies Count: 3; Documents tab rendered 3 JSON documents (total 3 hits); Tasks and Keys pages loaded with no 4xx; console/page errors []
- Model tokens used
- 1,159,615
- Exact commit tested
- ed8a2da42e12
- 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.
src/components/block/task/Total.tsx | 2 +- .../_layout/index/$indexUID/_layout/index.tsx | 22 ++++++++++------------ 3 files changed, 14 insertions(+), 16 deletions(-) final build:safe rc=0 Updated: assets/@nextui-org-DQvTQTk3.js Post-build replacement complete. Updated 4 files. Checked 121 files in 60ms. No fixes applied. Found 33 warnings. Final verification complete: `pnpm build:safe` rc=0, `pnpm lint` 0 errors, and the app works end to… tokens used 1,159,615 Final verification complete: `pnpm build:safe` rc=0, `pnpm lint` 0 errors, and the app works end to…
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
- Recovered from all 8 errors without a human stepping in, which says the failures are documented well enough to solve.
- 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
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Took 45 minutes to install, slower than the median of the 9 comparable projects Argusic has measured.
Of the 10 admin projects Argusic has installed and timed, meilisearch-ui was the 9th fastest to reach a running state, and 8 of 10 reached one at all.
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 | 2/3 | Runs with mocks | 92.00 | 0.27 | |
| Argusic Runner | 1/3 | Unverified | 80.00 | 0.27 |
Topics (from GitHub)
adminadmin-dashboardadmin-panelconsoledashboardhacktoberfestmeilisearchmeilisearch-dashboardreactreactjssearchsearch-enginesearchviewtypescriptuivercelvitejs
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/meilisearch-ui)Questions
- Does meilisearch-ui run?
- meilisearch-ui runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 45 minutes, hitting 8 errors on the way, and recorded the session.
- How did Argusic test meilisearch-ui?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit ed8a2da42e12. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test meilisearch-ui?
- The run that produced this verdict cost $0.27: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does meilisearch-ui take to install?
- 45 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-ui need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing meilisearch-ui?
- 8 things broke in the recorded run, and 8 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does meilisearch-ui compare with the alternatives?
- Of the 10 admin projects Argusic has installed and timed, meilisearch-ui was the 9th fastest to reach a running state, and 8 of 10 reached one at all.
- Where is the evidence for meilisearch-ui?
- 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.