basketikun/infinite-canvas: README-based editorial guide
A guide grounded in the README, repository metadata, and license for installing and checking basketikun/infinite-canvas.
Project scope
basketikun/infinite-canvas describes itself in the README as "面向 AI 创作的开源无限画布工作台,集成 AI 生图、参考图编辑、视频生成、Agent 智能助手、画布编排、对话创作、提示词库与素材管理等能力,支持可视化创作流程与多 Agent 协同工作。兼容 OpenAI 接口生态,支持 chatgpt2api、grok2api、flow2api、newapi 等渠道接入。". This article keeps to facts that can be checked in the repository. Stars, forks, and promotional badges are signals of attention, not proof of quality. Under "README", the README says: 无限画布是一款面向图片创作的开源工作台。它把画布编排、AI 图片生成、参考图编辑、对话助手、提示词库和素材沉淀放在同一个界面里,适合用来探索视觉方案并连续迭代图片结果。. That establishes the project's stated boundary, not a production test.
Suitable use cases
The README's "核心功能" section gives a useful starting point for deciding whether the project fits: 本地 Agent:通过本机 Canvas Agent 连接 Codex / Claude Code,让 Agent 通过 MCP 操作当前画布;. If that problem is not yours, popularity is a poor reason to adopt it. Project names, commands, and component names are kept as written so a reader can return to the primary source without guessing at terminology. Another checkable README item is: AI 创作:浏览器前台直连你配置的 OpenAI 兼容接口,支持文生图、图生图、参考图编辑、文本问答、音频和视频生成。. It can shape a first test, but it does not replace testing in the intended environment.
How it works
The operating model is spread across sections such as "Docker 运行". The source evidence includes: 首次打开后进入右上角配置,填入自己的 OpenAI 兼容 Base URL 和 API Key。. This article does not turn missing architecture, performance, or security details into claims. A real deployment still needs a look at the repository layout, configuration files, and release history.
Installation and first run
Start installation from the README's documented entry point. A command that can be checked in the source is: git clone git@github.com:basketikun/infinite-canvas.git cd infinite-canvas cd web bun install bun run dev When the README contains no runnable command, this article does not invent one. Open its "核心功能" section and confirm system dependencies, default ports, and first-run initialization before using a public server.