MxPage
开源 AI 电商图片工作台:商品主图与详情页、批量图片翻译、小红书图文、LangGraph Agent。支持 Windows / macOS 和本地部署,使用自己的模型 API。Open-source e-commerce image generator, translation & agent workspace.
Runssource: GitHubhomepageTypeScriptMITcommit 7adb826dbd8b
TypeScript, MIT licensed. The project labels itself: ai agents, batch processing, deterministic workflow, e commerce, electron, image editing, image generation and image translation.
MxPage runs. An Argusic agent installed it in 43 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
npm install and Next.js build succeed, dev server returns HTTP 200, and all 168 tests pass with zero failures.
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.
- node:sqlite not in Node 18; custom migration script and tests require it6 minutes
- sharp could not load on Node 18 (requires >=20.9.0)5 minutes
- @modelcontextprotocol/client missing transitive dependency3 minutes
- npm run prisma:deploy uses custom script requiring node:sqlite but runs under system Node 183 minutes
- Install time
- 43 minutes
- Cold machine to finish
- 28 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- npm test: 168 passed, 0 failed; curl http://localhost:3000/ returned HTTP 200; npm run build compiled successfully
- Model tokens used
- 233,162
- Exact commit tested
- 7adb826dbd8b
- 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.
2. **`sharp` requires Node >=20.9.0** — the system Node 18 could not load the sharp native addon. F…
3. **`@modelcontextprotocol/client` missing** — the `@openai/agents-core` package depended on it bu…
4. **Custom migration script uses `node:sqlite` (Node 22+)** — the project's `npm run prisma:deploy…
**Test results:** `npm test` with Node 22 + `--experimental-sqlite` → 168 tests passed, 0 failed.
**Build results:** `npm run build` → compiled successfully (standalone output in `.next/`).
**Server verification:** `npm run dev` started Next.js, and `curl -s -o /dev/null -w "HTTP %{http_c…
exec
/bin/sh -lc "echo '{\"install_succeeded\": true, \"launch_succeeded\": true, \"install_minutes\": 4…
succeeded in 0ms:
{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 43, "errors": [{"msg": "no…
tokens used
233,162Replay 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 4 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 43 minutes to install, slower than the median of the 123 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 124 ai-agents projects Argusic has installed and timed, MxPage was the 116th fastest to reach a running state, and 96 of 124 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
Topics (from GitHub)
ai-agentsbatch-processingdeterministic-workflowe-commerceelectronimage-editingimage-generationimage-translationlanggraphmacosmodel-context-protocolnextjsopenai-compatibleproduct-detail-pageproduct-imagesproduct-photographyself-hostedtypescriptwindowsxiaohongshu
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/mxpage)Questions
- Does MxPage run?
- Yes. MxPage runs. Argusic installed and launched it on a clean machine in 43 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test MxPage?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 7adb826dbd8b. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test MxPage?
- The run that produced this verdict cost $0.18: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does MxPage take to install?
- 43 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 MxPage need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing MxPage?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does MxPage compare with the alternatives?
- Of the 124 ai-agents projects Argusic has installed and timed, MxPage was the 116th fastest to reach a running state, and 96 of 124 reached one at all.
- Where is the evidence for MxPage?
- 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.