Cursor Canvas — product feedback
Subject: Canvas: workspace-native files, editor reliability, and hierarchical navigation
主题： Canvas：工作区内原生文件、编辑稳定性、目录化导航
Please forgive the bilingual layout: I’m not confident I can express my feedback clearly in English alone, so I’m including the Chinese original beside each line for accuracy.
请见谅我使用双语对照：我担心仅靠英文无法把我的意见说清楚，因此逐行附上中文原稿以便准确表达。
Cursor Canvas is genuinely valuable.
Cursor Canvas 整体非常有价值。
In addition to Cursor’s built-in workflows, I use it to keep two kinds of documentation in my project separate:
除了在 Cursor 自身工作流里使用，我还在项目里用它区分两类文档：
Agent-oriented docs — many files produced by tools like Superpowers and Compound Engineering (plans, persisted working notes, etc.).
面向 Agent 的文档 — Superpowers、Compound Engineering 等工具产出的大量文件（计划、落盘的工作记录等）。
They work well as filesystem-grounded context for the model—almost like file-based RAG—but for humans they are often long, dense, and hard to skim for the main ideas.
对模型很友好，近似「基于文件系统的 RAG」；但对人类读者往往冗长、信息密、难快速抓住要点。
Human-oriented docs — concise, maintainer-facing documentation.
面向人类维护者的文档 — 更精炼、可为团队服务的说明材料。
Canvas is an excellent fit here thanks to its layout, typography, and overall visual clarity.
Canvas 在版式、排版与视觉层次上很适合承担这一层。
The biggest gap today is that canvas sources are not treated as normal workspace files, so they don’t naturally ride along with Git, cloud backup, or team sharing.
目前最大的问题是：画布源文件没有按普通工作区文件来对待，因此难以自然享受 Git / 云同步备份 / 团队共享。
My current workaround is to delete the canvases folder under ~/.cursor/projects/.../, keep canvases/ in the repo, and symlink the Cursor-managed path to that directory.
我现在的权宜之计是删掉 ~/.cursor/projects/.../ 下的 canvases 目录，在仓库里保留 canvases/，再把 Cursor 管理路径软链接到该目录。
It sort of works, but it is fragile and has to be redone on every machine.
能用，但很脆，每台新机器都要重做一遍。
Request: first-class support for authoring and organizing canvas files inside the workspace (same as any other source file), without relying on per-machine symlinks.
诉求： 支持在工作区内直接创建、编辑与组织 canvas 文件（与别的源码一致），避免依赖本机软链接。
I also see frequent agent edit failures on these files (changes appear rejected or rolled back).
另外，Agent 编辑这些文件时我经常遇到失败（改动像是被拒绝或回滚）。
I suspect that may be related to paths outside the workspace and stricter tooling or guardrails around out-of-tree edits.
我猜想与路径在工作区外、从而触发更严格的工具/护栏有关。
Keeping canvases in-repo should help both sync and stability.
若画布默认为仓库内文件，应能同时改善同步与稳定性。
Additional request: in the Canvas UI, support a directory / tree view (not only a flat list) so larger sets of canvases remain manageable.
附加诉求： Canvas 界面在文件增多时，希望支持目录树 / 分层结构，而不是仅平铺列表。
Thank you for considering these improvements.
感谢考虑以上改进方向。