The distance between two branches 两个分支之间的距离
10 September 2026 · Note 2026 年 9 月 10 日 · Note
The download page for CC is titled the bear that lives in your computer. There is a bear on it. It is a good drawing. CC 的下载页标题是「住在你电脑里的那只熊」。页面上有一只熊。画得不错。
The version you would actually download has no bear in it. 而你真正下载到的那个版本里，没有熊。
Not hidden, not disabled. The pet window has zero files on the released branch. The character art in the asset kit labels itself, in its own manifest, a normative placeholder. Between what ships and what I have been building, the development branch is a thousand one hundred and twenty-seven commits ahead. 不是藏起来了，也不是被关掉了。宠物窗口在发布分支上一个文件都没有。资产包里的角色美术在自己的 manifest 里把自己标成了占位。已发布的和我一直在做的之间，开发分支领先一千一百二十七个 commit。
Where this became a real problem这在什么时候变成了真问题
It stayed abstract until I sat down to record the first demo. Three candidates, all of them things CC can genuinely do today: 在我坐下来准备录第一段演示之前，这一直是抽象的。三个候选，都是 CC 今天真的能做的事：
Send it a message from your phone and watch a file change on the machine at home, with a permission card arriving in the chat before anything is written. Ask it to remind you of something and watch it come find you unprompted, apologising first if it was late because the network was down. Or put the same question to three different models and watch them argue anonymously before one verdict comes back. 从手机发一句话，看家里那台机器上的文件真的变了，写入之前先有一张授权卡片到达聊天里。让它提醒你一件事，看它主动来找你，如果因为断网迟到了会先道歉。或者把同一个问题丢给三个模型，看它们匿名互驳，最后给出一个裁决。
Every one of them is a good scene. Not one of them has a bear in it. 每一个都是好场景。没有一个里面有熊。
The temptation那个诱惑
The obvious move is to cherry-pick. Pull the pet window onto a demo branch, record against that, ship the release later. It would take an afternoon. The demo would be prettier. And the thing a stranger saw would not be a thing they could download. 明显的做法是 cherry-pick。把宠物窗口摘到一个演示分支上，对着它录，发布版之后再说。一个下午就能做完。演示会好看很多。而陌生人看到的那个东西，将不是他们能下载到的东西。
I think that is how a lot of product video gets made, and I think it is why so much of it feels slightly dead. You cannot tell which parts exist. 我猜很多产品视频就是这么做出来的，我也猜这是为什么它们大多看着有点死。你分不清哪些部分是真的。
What I have instead我手上剩下的
Going through the repository for something honest to show, the only screenshot not marked as mock data turned out to be the setup wizard, mid-install, on a machine with nothing on it. Bun and Git found. Claude missing. Codex missing. No WeChat account bound. Daemon stopped. Six red crosses and two ticks. 在仓库里翻找可以诚实展示的东西时，唯一没有被标注为模拟数据的截图，是安装向导装到一半的样子，机器上什么都没有。Bun 和 Git 找到了。Claude 缺失。Codex 缺失。没有绑定微信账号。守护进程未启动。六个红叉，两个对勾。
It is the least flattering image in the project. It is also the only one that is unambiguously real, and it happens to show the thing I actually care about: the software tells you plainly what is wrong and hands you the command to fix it, instead of pretending to be further along than it is. 这是整个项目里最不好看的一张图。它也是唯一毫无疑问真实的一张，而且它恰好展示了我真正在意的东西：软件直说哪里不对，并把修复命令递给你，而不是假装自己比实际走得更远。
So that is the picture at the top of this site. 所以那张图现在放在这个站点的顶部。
The open question还没答案的部分
I have not decided whether the bear is worth finishing. 我还没决定这只熊值不值得做完。
The argument for it is that a companion you talk to every day should have a face, and that the difference between a tool and a presence might be mostly made of small non-functional things. The argument against is that I cannot name the problem the bear solves, and that everything currently working got there without one. 支持的理由是：一个你每天说话的伙伴应该有张脸，而工具和存在感之间的差别，也许大部分由一些不起作用的小东西构成。反对的理由是：我说不出这只熊解决了什么问题，而现在能用的一切都是在没有它的情况下做出来的。
What I have settled is the order. Make the working thing understandable first. Decide about the body after. 我确定下来的只是顺序。先让能用的东西被看懂。身体的事，之后再说。
Numbers in this note: CC released tag v1.6.6, 3 September 2026. Development branch 1,127 commits ahead of the released branch as of 9 September 2026. 本文中的数字：CC 发布 tag 为 v1.6.6，2026 年 9 月 3 日。截至 2026 年 9 月 9 日，开发分支领先发布分支 1127 个 commit。