infinite-canvas
面向 AI 创作的开源无限画布工作台，集成 AI 生图、参考图编辑、视频生成、Agent 智能助手、画布编排、对话创作、提示词库与素材管理等能力，支持可视化创作流程与多 Agent 协同工作。兼容 OpenAI 接口生态，支持 chatgpt2api、grok2api、flow2api、newapi 等渠道接入。
Runssource: GitHubhomepageTypeScriptMITcommit dab19adc0847
TypeScript, MIT licensed.
infinite-canvas runs. An Argusic agent installed it in 4 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Dependencies installed, dev server serves HTTP 200 with valid SPA HTML, and all 129 tests pass (3 in web/, 126 in canvas-agent/)
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.
- @ant-design/[email protected] requires antd@^5.11.2 but antd@^6.4.2 is specified in project1 minute
- Node.js 18.19.1 too old for Vite 7 (requires >=20.19)1 minute
- bun not found (required by test script)1 minute
- vite build OOM after 8736 modules on 2GB RAM container1 minute
- Install time
- 4 minutes
- Cold machine to finish
- 32 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- npx vite returned 200 on localhost:3000; bun test in web/ returned 3/3 pass; bun test in canvas-agent/ returned 126/126 pass; bun build ./src/main.tsx in web/ succeeded
- Model tokens used
- 74,941
- Exact commit tested
- dab19adc0847
- 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.
- `canvas-agent/` (tsc build): compiles cleanly **Known gap** – `npm run build` (Vite) runs out of memory after transforming 8736 modules on this 2… tokens used 74,941 All tasks complete. Here's the summary: **Install succeeded** – dependencies installed with `--legacy-peer-deps` to resolve the antd v5/v6 … **Dev server launched** – `npx vite --host 0.0.0.0 --port 3000` starts in ~220ms and serves HTTP 20… **Tests verified:** - `web/` (bun test): 3/3 pass - `canvas-agent/` (bun test): 126/126 pass across 8 test files - `canvas-agent/` (tsc build): compiles cleanly **Known gap** – `npm run build` (Vite) runs out of memory after transforming 8736 modules on this 2…
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 4 minutes, faster than the median of the 18 comparable projects Argusic has measured.
- 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
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 19 TypeScript projects Argusic has installed and timed, infinite-canvas was the 8th fastest to reach a running state, and 16 of 19 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 4 minutes after the clone.
Run history
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/infinite-canvas)Questions
- Does infinite-canvas run?
- Yes. infinite-canvas runs. Argusic installed and launched it on a clean machine in 4 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test infinite-canvas?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit dab19adc0847. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test infinite-canvas?
- The run that produced this verdict cost $0.07: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does infinite-canvas take to install?
- 4 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 infinite-canvas need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing infinite-canvas?
- 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 infinite-canvas compare with the alternatives?
- Of the 19 TypeScript projects Argusic has installed and timed, infinite-canvas was the 8th fastest to reach a running state, and 16 of 19 reached one at all.
- Where is the evidence for infinite-canvas?
- 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.