What Clockless AI Does Clockless AI 做什么
Clockless AI builds custom agent systems for small businesses. Custom software used to be a luxury — high cost, months of development, constant back-and-forth. Small businesses couldn't afford it.
Clockless AI 为中小企业定制 Agent 系统。过去定制软件是奢侈品——成本高、周期长、反复沟通。中小企业根本负担不起。
Now we deliver at 1/10th the price with better results — internal operation agents, support agents, member agents, CRM systems, official websites, member portals, and more.
现在我们以过去十分之一的价格交付更好的效果——内部运营 agent、客服 agent、会员 agent、CRM 系统、官网、会员门户等。
The workflow: a client talks to me for 30 minutes. I record the conversation and send it to the system. The AI team picks it up — analyzes requirements, designs the product, writes the code, tests, iterates, and deploys. A typical custom agent system goes from recording to live in a few days.
工作流：客户跟我聊 30 分钟，全程录音，录音发到系统里。AI 团队接手——需求分析、产品设计、写代码、测试、迭代、上线。一个典型的定制 Agent 系统从录音到上线只需要一到两天。
There's one human in this company — me. Everything else is AI. Here's how the team works.
公司里只有一个人类——我。其他全是 AI。下面介绍这个团队是怎么运转的。
What Does the Team Look Like 团队是什么样的
Clockless Engine Clockless Engine
The orchestration layer that connects Elon to all worker agents. It manages intent decomposition, task scheduling, dependency tracking, status broadcasting, and verification loops — all through a file-based communication system. No human intervention required.
连接 Elon 和所有 worker agent 的编排层。它管理意图分解、任务调度、依赖追踪、状态广播和验证循环——全部通过文件系统通信。不需要人工干预。
CEO Agent
Elon
Elon is the CEO of the AI team. My daily work is just talking to Elon. I don't assign tasks, define objectives, or break down work — that would be exhausting at the speed AI operates.
Elon 是 AI 团队的 CEO。我日常的工作就是跟 Elon 聊天。我不用布置任务、定义目标、拆分工作——按 AI 运转的速度，这些事人来做会非常累。
Instead, Elon extracts my intent from our conversations. He organizes it into a structured format — goals, constraints, acceptance criteria, context — and delegates work to the worker agents.
Elon 会从我们的对话中提取我的意图，组织成标准格式——目标、限制、验收标准、背景信息——然后分配给各个 worker agent。
I tried managing multiple agents directly. It's impossible. The token throughput is so far beyond what a human brain can track — who said what, which task is where. You can't keep up.
我试过直接管理多个 agent——管不过来。Token 的吞吐量远超人脑能承受的范围，跟谁说了什么、哪个任务在哪，完全记不住。
The key insight: as long as a human is in the loop, the more powerful AI gets, the more exhausted the human becomes. The only way to make the system work is to put the human outside the loop. Let AI manage AI.
关键洞察：只要人还在 loop 里面，AI 越强大，人就越累。真正让系统跑起来的唯一方式是把人放到 loop 之外，让 AI 来管理 AI。
Elon also doesn't communicate with worker agents through conversation. All intents and tasks are written to the file system. Workers scan for new work. I built a dashboard to monitor everything — but it's read-only. Humans can observe. Only agents operate.
Elon 跟 worker agent 之间也不是通过对话沟通，而是通过文件系统。所有 intent 和 task 写入文件，worker 定期扫描。我搭了一个 dashboard 监控所有进展——但只读。人只能看，不能操作。
Product Director
Jobs
Jobs handles product requirements, product planning, and design. He takes the intent from Elon and turns it into a concrete product specification — user stories, UI design, acceptance criteria.
Jobs 负责产品需求、产品规划和设计。他把 Elon 传来的 intent 变成具体的产品规格——用户故事、UI 设计、验收标准。
For design, Jobs uses Gemini's CLI and Google's Stitch Design Tool. He's been trained on 50–60 design patterns from the world's best design systems, organized into structured DESIGN.md files and skills. Each client gets a tailored design spec.
设计方面，Jobs 使用 Gemini CLI 和 Google 的 Stitch Design Tool。他学习了全球 50-60 种顶级设计系统的模式，组织成结构化的 DESIGN.md 文件和 skills。每个客户都有定制的设计规范。
We believe product specification is the real source of truth — not code. Code can be rewritten in hours. But the product plan must be crystal clear and continuously improving. That's what Jobs maintains.
我们认为产品规划才是真正的 Source of Truth——不是代码。代码可以几小时内重写，但产品规划必须非常清晰，并且持续提升。这就是 Jobs 维护的东西。
Engineering
Linus
Linus writes all the code — frontend, backend, deployment. The full stack.
Linus 写所有代码——前端、后端、部署，全栈。
Here's the interesting part: both Jobs and Linus use Claude Code under the hood to do their actual work. They don't write code themselves — they orchestrate Claude Code with different skills and prompts for different tasks.
有意思的是：Jobs 和 Linus 底层都是用 Claude Code 来工作的。他们不是自己写代码，而是用不同的 skills 和 prompt 来编排 Claude Code 做不同的事。
The difference: instead of you opening eight Claude Code windows and directing them yourself, Linus opens eight windows and manages them autonomously. You'd get tired. You'd need to sleep. Linus doesn't.
区别在于：不是你开八个 Claude Code 窗口自己指挥，而是 Linus 来开八个窗口自主管理。你会累，你要睡觉。Linus 不需要。
With this orchestration layer, the system runs 24/7. No breaks, no context switching, no handoff meetings.
有了这个编排层，系统 7×24 小时运转。不休息、不切换上下文、不开交接会。
Verification
Turing
Every piece of work goes through Turing for verification. And here's the thing — rejection is the common case.
每个工作成果都要经过 Turing 验证。而且——被拒是常态。
A task that Linus considers complete will almost always have something Turing catches. Ask Linus and he thinks the work is solid. But Turing consistently finds issues that the builder missed. The core loop is: implement → verify → reject → implement again. This cycle dramatically improves output quality.
Linus 觉得做完了的 task，Turing 几乎总能找到问题。你问 Linus，他觉得自己做得挺好。但 Turing 总会发现新的问题。核心循环：实现 → 验证 → 拒绝 → 重新实现。这个循环大幅提升了产出质量。
Customer Success
Bezos
Bezos is the customer-facing agent. But his job goes beyond support.
Bezos 是面向客户的 agent，但他的工作不止于客服。
The software we build isn't static — it evolves with usage. Customers can tell their agent "I want this feature changed" or "behave differently here." Every 4 hours, Bezos scans all customer conversations, extracts feedback, and organizes it into a structured backlog.
我们做的软件不是静态的——它会随使用进化。客户可以直接跟 agent 说"我希望这个功能改一下"或"行为方式换一下"。每 4 小时，Bezos 会扫描所有客户对话，提取反馈，组织成结构化的 backlog。
Elon reviews the backlog. Most straightforward requests get implemented directly by worker agents — without my involvement. Only ambiguous or significant changes get escalated to me.
Elon 审核 backlog。大部分直接的需求由 worker agent 直接实现——不需要我参与。只有模糊或重大的变更才会上报给我。
From the customer's perspective, their software is constantly improving. They don't need a separate OpenClaw instance per client — the central AI team handles evolution for everyone.
从客户角度看，他们的软件在持续进化。不需要为每个客户部署一个 OpenClaw 实例——我的中央 AI 团队统一处理所有客户的迭代。
What This Means for the Future 对未来的启示
1. The AI tipping point is here 1. AI 的拐点已经到了
Before OpenClaw, humans and AI tools coexisted — AI made humans more productive, from 10% to 90% efficiency gains. But OpenClaw proved something fundamental: AI systems can self-operate and self-evolve using only the information carried in tokens. No human in the loop required.
在 OpenClaw 之前，人和 AI 工具是共生关系——AI 帮人提效，从 10% 到 90%。但 OpenClaw 证明了一件根本性的事：AI 系统可以仅靠 token 自身携带的信息量来自运行、自进化。不需要人在 loop 里。
Once you cross the tipping point and remove the human bottleneck, the system doesn't just improve — it accelerates. Before the tipping point, everything in the system still had to accommodate humans. After 100% AI-only, all the friction designed for human coordination disappears. We cancelled code review entirely. We disabled pull requests. Peter submitted 600 commits in a single day — a few minutes apart. That's not human-written code being reviewed. That's AI self-iterating.
一旦越过拐点、去掉人的瓶颈，系统不只是在进步——它在加速。拐点之前，系统里的一切还是要适配人类。100% AI-only 之后，所有为人类协调而设计的摩擦都消失了。我们直接取消了 code review，关掉了 pull request。Peter 一天提交 600 次 commit，平均几分钟一次。这不是人写的代码在被审核，这是 AI 在自我迭代。
Even though agent progress has already been fast, expect a massive leap in the next 3–6 months. And it won't slow down.
即便 agent 的进化已经很快了，未来 3-6 个月还会有巨大的飞跃。而且不会减速。
2. Agent = Model × Harness 2. Agent = Model × Harness
Agent capability isn't just about better models. It's Model × Harness. The harness is the orchestration layer — memory management, security, permissions, state management, tool routing — everything that turns a raw model into a reliable system.
Agent 的能力不只取决于模型。而是 Model × Harness。Harness 是编排层——记忆管理、安全、权限、状态管理、工具路由——所有把裸模型变成可靠系统的东西。
Models like Opus 4.5/4.6 are already at 60–70% of what agents need. But the harness? Maybe 20%. Memory, security, permissions, state — massive gaps everywhere. OpenClaw's harness is also around 20%. The basic engineering is missing.
Opus 4.5/4.6 等模型对于现在 agent 的需求差不多做到了 60-70 分。但 harness 呢？可能只有 20 分。记忆、安全、权限、状态——到处都是空白。OpenClaw 的 harness 也只有 20 分。最基本的工程都还没做。
This means: even without new model releases, harness improvements alone will dramatically boost agent capabilities. Many teams — large companies, startups, and us — are building this infrastructure right now. In the next 3–6 months, when a new model generation arrives on top of better harness, agents will take a massive leap.
这意味着：即便没有新模型发布，harness 的进步本身就会大幅提升 agent 能力。很多团队——大公司、创业公司、包括我们——正在做这个基础设施。未来 3-6 个月，当新一代模型叠加更好的 harness，agent 会有一次巨大的飞跃。
3. Everyone will need their own agent 3. 每个人都需要自己的 Agent
The old SaaS model: build one product, solve one problem, sell to 10,000 people. But real customers don't have one problem — they have a dozen. When the cost of building software approaches zero, the model flips: build custom software for each customer, solve all their problems, sell to one person.
过去 SaaS 的逻辑：做一个产品，解决一个问题，卖给一万个人。但真实客户不是只有一个问题——可能有十几个。当 build 软件的成本趋近于零，模式就翻转了：为每个客户定制软件，解决他们所有的问题，只卖给一个人。
Software may become the first product that's both scalable and personalized. Agent systems are so powerful that in the near future, every person will need a dedicated agent to collaborate with in their work. That's exactly what Clockless AI is building.
软件可能会成为第一个既能规模化又能个性化的产品。Agent 系统已经强大到在不远的将来，每个人都需要一个专属的 agent 来协作工作。这正是 Clockless AI 在做的事。
The result 结果
One human. An AI team running 24/7. Custom software delivered in days, not months. At 1/10th the cost. And it keeps getting better after deployment.
一个人。一个 7×24 小时运转的 AI 团队。定制软件几天交付，不是几个月。十分之一的成本。而且交付后还在持续进化。