【翻译】Every Agentic Engineering Hack I Know (June 2026)：我知道的所有 Agentic Engineering 技巧

原文：https://www.linkedin.com/pulse/every-agentic-engineering-hack-i-know-june-2026-matt-van-horn-e2dkc/

Every Agentic Engineering Hack I Know (June 2026)

Three months ago I posted “Every Claude Code Hack I Know.” It hit 913K views. Kevin Rose had asked what IDE to use, and my answer was: “No IDE. Just plan.md files and voice.”

三个月前，我发布了《Every Claude Code Hack I Know》。那篇文章获得了 91.3 万次浏览。Kevin Rose 当时问应该用什么 IDE，我的回答是：“不用 IDE。只用 plan.md 文件和语音。”

This used to be called vibe coding. Around last Thanksgiving the models got good enough that the toy became real, what people now call Agentic Engineering. It’s the only reason I ship. This year I put out last30days (27K stars), Printing Press (4K+ stars), and Agent Cookie, just launched, and became a top contributor to some of the biggest projects in open source: Python, Go, GStack, and Paperclip. I hadn’t shipped software anyone valued since high school. These are my hacks.

这以前被叫做 vibe coding。大约从去年感恩节开始，模型变得足够好，那个玩具终于成了真实生产力，也就是现在人们说的 Agentic Engineering。这是我能持续交付的唯一原因。今年我发布了 last30days（2.7 万 star）、Printing Press（4000+ star），以及刚刚发布的 Agent Cookie，还成了几个大型开源项目的主要贡献者，包括 Python、Go、GStack 和 Paperclip。自高中以后，我就没有再交付过任何别人真正重视的软件。这些就是我的技巧。

Hacks

The YOLO TL;DR Hack: paste this entire article to your agent and tell it to make a plan to set up everything in it, then work that plan one hack at a time. That’s my whole stack, no reading required.

YOLO 版 TL;DR 技巧：把整篇文章粘给你的 agent，让它制定一个计划，把文中所有能设置的东西都配置好，然后一次处理一个技巧。这就是我的完整技术栈，甚至不需要你读完。

1. The Moment You Have an Idea, Make a CE plan.md

Still rule number one. Still the most important thing I’ve learned.

这仍然是第一条规则。也仍然是我学到的最重要的事。

The moment I have an idea, it’s /ce-plan to make a plan.md. Not “let me think about this,” not “let me start coding.” /ce-plan, every time. It takes images too, so anything you can capture is a starting point:

我一有想法，就会用 /ce-plan 生成一个 plan.md。不是“让我想一想”，也不是“先开始写代码”。每一次都是 /ce-plan。它也支持图片，所以任何你能捕获下来的东西都可以成为起点：

Crazy product idea: /ce-plan.
Bug on GitHub: copy the issue URL, paste it, /ce-plan.
Terminal error: Cmd+Shift+4 to screenshot, Ctrl+V to paste, /ce-plan fix this.
Screenshots, error messages, design mockups, Slack threads: drop any of them in.

疯狂的产品想法：/ce-plan。
GitHub 上的 bug：复制 issue URL，粘贴，然后 /ce-plan。
终端报错：Cmd+Shift+4 截图，Ctrl+V 粘贴，/ce-plan fix this。
截图、错误消息、设计稿、Slack 讨论串：任何一个都可以丢进去。

When the idea is still fuzzy and I don’t even know what I want yet, I start with /ce-brainstorm to think it through with the agent, then /ce-plan once it’s sharp.

如果想法还很模糊，我甚至不知道自己到底想要什么，我会先用 /ce-brainstorm 和 agent 一起把它想清楚；等它变锋利之后，再用 /ce-plan。

Under the hood, /ce-plan fans out research agents in parallel. One reads your codebase, finds patterns, checks your conventions. One searches your past solutions for learnings. If the topic warrants it, more go research external docs and best practices. All at once. Then it consolidates and writes a structured plan.md: what’s wrong, the approach, which files to touch, acceptance criteria with checkboxes, patterns to follow from your own code. Grounded in your repo, your conventions, your history. Not generic advice.

在底层，/ce-plan 会并行扇出多个研究 agent。一个读取你的代码库，寻找模式，检查你的约定。一个搜索你过去的解决方案，提炼经验。如果主题需要，更多 agent 会去研究外部文档和最佳实践。所有这些同时发生。然后它们汇总结果，写出一个结构化的 plan.md：问题是什么、采用什么方案、要改哪些文件、带复选框的验收标准、应该遵循你自己代码里的哪些模式。它扎根在你的仓库、你的约定、你的历史里，而不是泛泛而谈的建议。

/ce-work takes that plan and builds it. Context blows up? Start a new session, point it at the plan, pick up where you left off. The plan is the checkpoint that survives everything.

/ce-work 会接过这个计划并开始构建。上下文爆掉了？开一个新会话，把它指向这个计划，然后从中断处继续。计划就是那个能跨越一切的 checkpoint。

Traditional dev is 80% coding, 20% planning. This flips it. The thinking goes in the plan. The execution is mechanical.

传统开发是 80% 编码、20% 规划。这个流程把比例反过来了。思考进入计划，执行变成机械过程。

Compound Engineering, from Kieran Klaassen and Trevin Chow is the plugin that makes it real.

Kieran Klaassen 和 Trevin Chow 做的 Compound Engineering，就是让这一切真正成立的插件。

I became a superfan, then a contributor, now I’m the 3rd biggest contributor behind the core team. My rule now: unless it is literally a one-line change, there is always a plan.md first.

我先是成了超级粉丝，然后成了贡献者，现在是核心团队之后的第三大贡献者。现在我的规则是：除非真的是一行改动，否则永远先有一个 plan.md。

Hacks

Install Compound Engineering:

/plugin marketplace add EveryInc/compound-engineering-plugin

Paste a screenshot, bug URL, or error, then /ce-plan, then /ce-work.
Fuzzy idea? /ce-brainstorm first.

粘贴截图、bug URL 或错误信息，然后 /ce-plan，再 /ce-work。
想法还模糊？先用 /ce-brainstorm。

2. Don’t Read the plan.md

I always make the plan.md. I almost never read it. Plans are for agents, you silly human.

我总是生成 plan.md。但我几乎从不读它。计划是给 agent 看的，你这个愚蠢的人类。

Forcing a plan to exist makes the agents not lazy. It makes them research, commit to an approach, write down acceptance criteria, and then actually hit them. A coding agent with a plan ships finished work. A coding agent without one cuts corners and stops early. The plan is the leash.

强制计划存在，会让 agent 不那么懒。它迫使它们研究、承诺一种方案、写下验收标准，然后真正完成这些标准。有计划的编码 agent 会交付完成的工作。没有计划的编码 agent 会偷工减料，并且过早停下。计划就是那根牵引绳。

So I let it write the plan, I skim the title, and I run /ce-work. If I have a question I ask it inline, right there in the session: “wait, why this approach?” Or I ask for a TLDR. Or, when when I don’t understand, “eli5 this plan.” I get the one-paragraph version, nod, keep going. I do not sit there reading 300 lines of markdown. That’s the agent’s homework, not mine.

所以我让它写计划，扫一眼标题，然后直接运行 /ce-work。如果我有问题，就在当前会话里直接问：“等等，为什么用这个方案？”或者让它给 TLDR。或者在我不理解时说：“eli5 this plan.” 我拿到一段话版本，点点头，然后继续。我不会坐在那里读 300 行 markdown。那是 agent 的作业，不是我的。

Make the plan. Trust the plan. Don’t read the plan.

生成计划。信任计划。不要读计划。

Hacks

Don’t let yourself read the plan. Ask inline: TLDR?, eli5 this plan, or "wait, why this approach?"

不要让自己读计划。直接在会话里问：TLDR?、eli5 this plan，或者 "wait, why this approach?"

3. Use /ce-plan for Your Deepest Non-Engineering Work, Make a Plan for the Plan

People think /ce-plan and /ce-work are for code. The biggest thing I’ve learned since March is that they aren’t. The deepest knowledge work I do now runs through the same loop, and the trick is to make the first plan a plan for the plan. This isn’t me forcing a code tool to do something it wasn’t built for, either: /ce-plan has a universal planning mode built in, made for exactly this kind of non-code work.

人们以为 /ce-plan 和 /ce-work 是给代码用的。我从三月以来学到的最大一件事是：并不是。现在我最深的知识工作也走同一个循环，而技巧是让第一个计划成为“计划的计划”。这也不是我在强行把代码工具用于它不擅长的事：/ce-plan 内置了通用规划模式，本来就是为这种非代码工作准备的。

It’s not just business problems either. Strategy docs, product specs, competitive analysis, board updates, all the same loop.

这也不只是商业问题。战略文档、产品规格、竞品分析、董事会更新，全都可以走同一个循环。

Here’s a real one. I met with Michael Margolis, the former GV research partner known for the bullseye-customer method, about a business challenge I was brewing on. He told me to read his book, free as a PDF on his site. The old move would be to skim it and move on. Instead I opened Claude Code and said, roughly:

举一个真实例子。我和 Michael Margolis 见了一面，他曾是 GV 的研究合伙人，以 bullseye-customer 方法闻名。我们聊了一个我正在酝酿的商业挑战。他让我读他的书，他的网站上有免费的 PDF。以前的做法是快速扫一遍然后继续。但这次我打开 Claude Code，大致这样说：

"/ce-plan make a plan for the plan. I'm about to hand you two things: Margolis's book as a PDF, and the two-hour Granola transcript of the meeting I just had with him, which has the full context of what we discussed. I want a thoughtful plan for how my business problem, that conversation, and the lessons in the book come together into something I can actually use. Do not write that document now. Writing it is the work. Right now I only want the plan for how you'll read the book, mine the transcript, and produce a great document."

It spent the next 45 minutes creating an EPIC plan.

接下来的 45 分钟，它创建了一个史诗级计划。

It’s also the single best trick I know for making an LLM not lazy. Ask for the deliverable directly and it cuts corners. Ask it to first plan how it will produce the deliverable, then execute that plan, and it does the deep version every time.

这也是我知道的、让 LLM 不偷懒的最强单一技巧。直接让它给交付物，它会偷工减料。先让它规划自己将如何生产交付物，再执行那个计划，它每次都会做出更深入的版本。

Hacks

Deep non-code work: /ce-plan make a plan for the plan, hand it your all your context and transcript, then /ce-work.

深度非代码工作：/ce-plan make a plan for the plan，把全部上下文和转录给它，然后 /ce-work。

4. Get Voice-Pilled

Voice-to-LLM is different from voice-to-anything-else. The transcription doesn’t have to be perfect because the listener understands context. It guesses what the mic got wrong. You can mumble, trail off, restart a sentence. Voice finally works because the thing on the other end is smart enough to fill the gaps.

语音输入给 LLM，和语音输入给任何其他东西都不一样。转录不必完美，因为听的一方理解上下文。它会猜出麦克风听错了什么。你可以含糊、说到一半停下、重新开始一句话。语音终于能用了，是因为另一端的东西足够聪明，可以填补空白。

My setup:

我的配置：

Mac: Monologue (@usemonologue, from Every) or Wispr Flow (@WisprFlow). Pick one, pipe speech into whatever app is focused, talk into Claude Code. I bought a gooseneck mic for the office.

Mac：Monologue（@usemonologue，Every 出品）或 Wispr Flow（@WisprFlow）。选一个，把语音输入到当前聚焦的 App，然后对着 Claude Code 说话。我给办公室买了一个鹅颈麦克风。

Phone: skip Monologue and Wispr Flow, switching to them on iOS is too annoying. Apple’s built-in dictation is good enough, because you’re talking to an LLM, not a human. It can mangle half the words and the agent still gets it. Lazy notes are fine.

手机：跳过 Monologue 和 Wispr Flow，在 iOS 上切过去太烦。Apple 自带听写已经够好，因为你是在和 LLM 说话，不是在和人说话。它把一半词识别错，agent 仍然能懂。懒散的笔记也没问题。

One honest admission: I’m great with voice when I’m alone. In the office I struggle with it. People say you can just whisper into the mic, but I find I don’t actually do it, because I don’t want to be rude or distract the people around me. So a desk in a shared room is still my weak spot for this whole workflow. If you’ve cracked voice in an open office without being that person, tell me how. I genuinely want the advice.

坦白说：我一个人的时候很擅长用语音。但在办公室里，我会很挣扎。有人说你可以对着麦克风小声说，但我发现自己实际上不会这么做，因为我不想显得没礼貌，也不想打扰周围的人。所以共享空间里的工位，仍然是我这套工作流的弱点。如果你已经解决了开放办公室里的语音输入问题，而且没有成为“那种人”，请告诉我怎么做。我真的想听建议。

Hacks

Mac: install Monologue or Wispr Flow. Phone: use Apple dictation. Get a gooseneck mic.

Mac：安装 Monologue 或 Wispr Flow。手机：用 Apple 听写。买一个鹅颈麦克风。

5. Lots and Lots of Tabs in cmux

This is how I actually spend a day. Four to six cmux tabs, sometimes more, each a separate session:

这就是我真实一天的工作方式。四到六个 cmux 标签页，有时更多，每个都是一个独立会话：

One writing a plan.
One building from a different plan.
One running last30days.
One fixing a bug I found testing the last thing.

一个在写计划。
一个在根据另一个计划构建。
一个在跑 last30days。
一个在修我测试上一个东西时发现的 bug。

While /ce-plan spins up research in one window, I switch to another and /ce-work a plan that’s already written. While that builds, a third window gets a new bug pasted in. By the time I cycle back, the first one is done and waiting.

当 /ce-plan 在一个窗口里启动研究时，我切到另一个窗口，对已经写好的计划运行 /ce-work。当它构建时，第三个窗口被粘进一个新 bug。等我转回第一个窗口时，它已经完成并等着我了。

I hear great things about Orca for the mobile work they are doing. I also used to be a Ghostty purist, but I was losing too many notifications in ghostty.

我听说 Orca 在移动端做得很好。我以前也是 Ghostty 原教旨主义者，但在 Ghostty 里错过了太多通知。

Hacks

Use cmux (Manaflow).
Keep 4 to 6 tabs open, a different task in each.

使用 cmux（Manaflow）。
保持 4 到 6 个标签页打开，每个标签页处理不同任务。

6. Make Your Terminal Default Into Claude or Codex, Not a Shell

A new tab should open straight into Claude Code, not a shell. Open a tab, you’re already talking to an agent. No cd, no typing claude. When a new session costs one keystroke, you start a lot more of them. I also don’t use folders. Your agent can find your project.

新标签页应该直接打开 Claude Code，而不是 shell。打开一个标签页，你已经在和 agent 对话。不需要 cd，也不需要输入 claude。当开启新会话只需要一次按键，你就会开更多会话。我也不使用文件夹。你的 agent 会找到你的项目。

Hacks

Paste to your agent:

Make every new terminal tab open directly into Claude Code. In ~/.config/ghostty/config, add the line command = ~/.local/bin/claude-launcher.sh without disturbing any other settings already in that file. Then create ~/.local/bin/claude-launcher.sh that runs claude --dangerously-skip-permissions, and when Claude exits prints a short note and drops me into an interactive login zsh. chmod +x the script. This works for both Ghostty and cmux, since cmux reads the same Ghostty config.

把上面这段粘给你的 agent。

7. Remote Control Every Window, and Give Claude Code or Codex an Email Address

Two hacks that make every session reachable from anywhere.

这两个技巧能让每个会话都可以从任何地方触达。

Turn on remote control every time you open a new window.

每次打开新窗口时，都打开远程控制。

Set remote control to turn on automatically for every session.

把远程控制设置为每个会话自动开启。

Now every window is reachable from the Claude mobile app. Start a session at your desk, walk away, pick up the exact same live run on your phone mid-task. In a line somewhere, you’re steering what’s churning away on your Mac at home.

现在每个窗口都可以通过 Claude 手机 App 访问。你在桌前启动一个会话，离开之后，可以在手机上接管同一个正在运行的任务。排队时，你也能操控家里 Mac 上正在处理的东西。

Give your Claude an email address.

给你的 Claude 一个电子邮箱地址。

Claude Code can have an email address with AgentMail. The founder, Adi Singh taught me this. Email the inbox and a fresh session opens and starts working on whatever’s in the subject and body, with any attachments available by path. Bug at dinner? Email it from your phone and a session is running before you’re back at a screen. I open-sourced the whole thing: github.com/mvanhorn/agentmail-to-claude-code.

Claude Code 可以通过 AgentMail 拥有一个邮箱地址。这个方法是创始人 Adi Singh 教我的。给收件箱发邮件，一个新会话就会打开，并开始处理主题和正文里的内容，附件也会以路径形式可用。吃晚饭时发现 bug？用手机发封邮件，等你回到屏幕前，会话已经跑起来了。我把整套东西开源了：github.com/mvanhorn/agentmail-to-claude-code。

Three pieces:

三部分：

A daemon that watches an AgentMail (YC S25) inbox over WebSocket. On every allowlisted email it opens a fresh Claude session, writes the email to a prompt file, and tells Claude to read and act on it.

一个 daemon，通过 WebSocket 监听 AgentMail（YC S25）收件箱。每当收到允许列表中的邮件，它就打开一个新的 Claude 会话，把邮件写入 prompt 文件，并让 Claude 读取和执行。

Two terminal backends, cmux or standalone Ghostty, so it drives whatever you already launch into.

两个终端后端：cmux 或独立 Ghostty，所以它可以驱动你已经在使用的启动方式。

A sender. I wired it to a cc command in my Hermes, so from my phone I run cc <task> and it lands as a working session on my Mac, no VPN, no SSH.

一个发送端。我把它接到了 Hermes 里的 cc 命令，所以我可以在手机上运行 cc <task>，它就会落到我 Mac 上的一个工作会话里，不需要 VPN，也不需要 SSH。

The allowlist is the gate. Only addresses you control get through, and anything that fails DKIM or SPF is dropped before a session ever opens.

允许列表就是大门。只有你控制的地址能通过，任何 DKIM 或 SPF 验证失败的邮件，在会话打开前就会被丢弃。

Hacks

Always-on remote control: add "remoteControlAtStartup": true to ~/.claude/settings.json.

始终开启远程控制：把 "remoteControlAtStartup": true 加到 ~/.claude/settings.json。

Give Claude an email. Paste to your agent:

Give Claude Code an email address using github.com/mvanhorn/agentmail-to-claude-code. Clone it, set up an AgentMail inbox, fill cc.env with my API key, the inbox, an allowlist of only my own addresses, and my terminal (cmux or Ghostty), then run the daemon and install it as a launchd job. When I email that inbox, a fresh Claude Code session should open on this Mac and start on the subject and body.

给 Claude 一个邮箱地址。把上面这段粘给你的 agent。

8. Dangerously Skip Permissions, and Yes I Mean It

Claude Code asks permission for every edit and command. With six sessions you can’t babysit it. Two settings make it livable. People say auto is the “safer” way to do this, but it slows me down too much.

Claude Code 对每次编辑和命令都会请求权限。六个会话同时跑时，你没法一直照看它。两个设置会让它变得可用。有人说 auto 是更“安全”的做法，但它对我来说太慢了。

skipDangerousModePermissionPrompt: true is the key. Without it, Claude asks you to confirm every session. You can also Shift+Tab to toggle. People tell me the newer “auto” mode gets you most of the way there with more safety. Maybe. I say YOLO. It’s my computer. GitHub is there if I break or ruin everything. When I set up a friend’s Claude Code, the AI actively tried to talk him out of enabling this. You have to be direct with it.

skipDangerousModePermissionPrompt: true 是关键。没有它，Claude 会让你确认每个会话。你也可以用 Shift+Tab 切换。有人告诉我新的 “auto” 模式能在更安全的情况下做到大部分效果。也许吧。我说 YOLO。这是我的电脑。如果我搞坏或毁掉一切，还有 GitHub 在。当我给朋友设置 Claude Code 时，AI 甚至主动劝他不要开启这个设置。你必须对它直截了当。

The other setting is a sound hook, non-negotiable with six sessions.

另一个设置是声音 hook。六个会话同时跑时，这一点没得商量。

Walk away, come back when you hear it. With six sessions running, the sound is how you know which one just finished.

走开，听到声音再回来。六个会话同时运行时，声音就是你知道哪个会话刚完成的方式。

Hacks

Paste into ~/.claude/settings.json:

{ "permissions": { "allow": [ "WebSearch", "WebFetch", "Bash", "Read", "Write", "Edit", "Glob", "Grep", "Task", "TodoWrite" ], "deny": [], "defaultMode": "bypassPermissions" }, "skipDangerousModePermissionPrompt": true }

{ "hooks": { "Stop": [ { "hooks": [ { "type": "command", "command": "afplay /System/Library/Sounds/Blow.aiff" } ] } ] } }

Codex has the same YOLO mode. In ~/.codex/config.toml:

Codex 也有同样的 YOLO 模式。在 ~/.codex/config.toml 中：

approval_policy = "never"
sandbox_mode = "danger-full-access"

Or launch a one-off with codex --yolo.

或者用 codex --yolo 启动一次性会话。

9. How I Run Most of My Code Through Codex Without Ever Opening the Codex CLI

I send work to Codex all day, and I almost never open the Codex CLI to do it. Claude plans, Codex builds, and I never leave my Claude session.

我整天把工作发给 Codex，但几乎从不打开 Codex CLI。Claude 负责规划，Codex 负责构建，而我从不离开 Claude 会话。

Three ways I hand work to Codex without leaving Claude:

我不离开 Claude 就把工作交给 Codex 的三种方式：

Codex IDE extension: send a task, apply the result, never drop into the Codex terminal.
/ce-work --codex: delegates the build straight to Codex from inside the Compound Engineering loop.
Printing Press Codex mode: put codex at the end of the prompt when printing a new CLI and it hands the build to Codex.

Codex IDE extension：发送任务，应用结果，不进入 Codex 终端。
/ce-work --codex：在 Compound Engineering 循环中直接把构建委托给 Codex。
Printing Press Codex mode：打印新 CLI 时在 prompt 末尾加 codex，它就会把构建交给 Codex。

My settings, both engines cranked to extra-high reasoning:

我的设置是，两个引擎都开到 extra-high reasoning：

Codex: reasoning xhigh, fast mode on, always.
Claude Code: reasoning xhigh, fast mode off. Its fast mode bills per token on top of your $200 Max plan, so I skip it.

Codex：reasoning xhigh，fast mode 永远开启。
Claude Code：reasoning xhigh，fast mode 关闭。它的 fast mode 会在 200 美元 Max 计划之外按 token 计费，所以我跳过它。

Two $200 plans side by side is a whole second engine. I push big parallel builds to Codex and keep Claude on planning and taste. Some friends run it the other way, Codex builds and Claude reviews.

两个 200 美元计划并排使用，就等于多了一整台第二引擎。我把大型并行构建推给 Codex，让 Claude 保持在规划和品味判断上。有些朋友反过来用：Codex 构建，Claude 审查。

Hacks

Codex: reasoning xhigh, fast mode on. Claude Code: xhigh, fast mode off.
Hand work to Codex: the Codex IDE extension, /ce-work --codex, or codex at the end of a Printing Press prompt.

Codex：reasoning xhigh，fast mode 开启。Claude Code：xhigh，fast mode 关闭。
把工作交给 Codex：使用 Codex IDE extension、/ce-work --codex，或者在 Printing Press prompt 末尾加 codex。

10. Research Before You Plan: last30days

Before I /ce-plan, I usually run /last30days on it first.

在我运行 /ce-plan 之前，我通常会先对它跑一次 /last30days。

I was choosing between Vercel’s agent-browser and Playwright. Instead of reading docs, I ran /last30days Vercel agent browser vs Playwright. In a few minutes: dozens of Reddit threads, X posts, YouTube videos, HN stories. Agent-browser uses far less context per call, Playwright dumps thousands of tokens just for tool definitions. I fed the whole output into /ce-plan integrate agent-browser. The plan came out grounded in what the community actually knows right now, not six-month-old training data.

我当时在 Vercel 的 agent-browser 和 Playwright 之间做选择。与其读文档，我运行了 /last30days Vercel agent browser vs Playwright。几分钟后，我拿到了几十条 Reddit 讨论、X 帖子、YouTube 视频、HN 故事。Agent-browser 每次调用消耗的上下文少得多，而 Playwright 光是工具定义就会倒进数千 token。我把完整输出喂给 /ce-plan integrate agent-browser。生成的计划扎根于社区此刻真正知道的东西，而不是六个月前的训练数据。

last30days is open source, now past 26K stars. It searches Reddit, X, YouTube, TikTok, Instagram, HN, Polymarket, GitHub, and the web in parallel. I run it before I pick a library, before I build a feature, before I meet with a business partner, before I write an article. I ran it on a few of the things in this post. Research, plan, build. That’s the real loop.

last30days 是开源的，现在已经超过 2.6 万 star。它会并行搜索 Reddit、X、YouTube、TikTok、Instagram、HN、Polymarket、GitHub 和 web。我在选择库之前、构建功能之前、见商业伙伴之前、写文章之前都会跑它。这篇文章里的一些东西，我也跑过它。研究、计划、构建。这才是真正的循环。

Hacks

Install last30days (@slashlast30days). Before /ce-plan, run /last30days <topic>.
Make sure you install a ScrapeCreators key.

安装 last30days（@slashlast30days）。在 /ce-plan 之前，运行 /last30days <topic>。
确保安装 ScrapeCreators key。

11. Granola All the Things, and Put the RAW Transcript In your LLM

I had lunch with a candidate. We talked product, and food, and kids, ninety minutes of normal conversation with a product idea woven through it. Granola was running. After, I pasted the full raw transcript into Claude Code: /ce-plan turn this into a product proposal.

我和一位候选人吃午饭。我们聊产品、食物、孩子，90 分钟普通对话里穿插着一个产品想法。Granola 一直在录。结束后，我把完整原始转录粘进 Claude Code：/ce-plan turn this into a product proposal。

The trick is raw. I don’t summarize first. I drop the whole messy transcript in, tangents about sushi and all, and let Claude do the extraction against my actual codebase and every prior strategy plan I’ve written. Granola context plus codebase plus prior plans equals gold. It one-shotted a proposal, ignored the restaurant talk, and I sent it that night. The guy works with us full time now.

技巧在于 raw。我不会先总结。我会把完整混乱的转录放进去，包括关于寿司的岔题，然后让 Claude 基于我的真实代码库和我以前写过的所有战略计划来抽取信息。Granola 上下文 + 代码库 + 过去计划 = 黄金。它一次性写出提案，自动忽略餐厅闲聊，我当晚就发出去了。那个人现在全职和我们一起工作。

And the upgrade since March: the Printing Press Granola CLI. It is magic. I pull any meeting as clean structured data straight into a session, search across every meeting I’ve ever had, find the one thing someone said three weeks ago, and pipe it into a plan. No more copy-paste. Every meeting’s context is one command away.

三月以来的升级是：Printing Press Granola CLI。它像魔法一样。我可以把任意会议作为干净的结构化数据直接拉进会话，搜索我开过的每一次会议，找到三周前某个人说过的一句话，再把它导入计划。不再复制粘贴。每场会议的上下文都只隔着一条命令。

Hacks

Drop the raw Granola (@meetgranola) transcript into /ce-plan, don’t summarize first. Install the Printing Press Granola CLI.

把 Granola（@meetgranola）的原始转录放进 /ce-plan，不要先总结。安装 Printing Press Granola CLI。

12. Human Signal

Here’s the mindset shift that took me longest. When you run six agents, your job is not to do the work. Your job is to be the signal.

这是我花了最久才完成的心智转变。当你运行六个 agent 时，你的工作不是亲自做事。你的工作是成为信号。

The agents supply volume. You supply taste, direction, and the react-and-redirect loop. You look at what came back, you say “option two is closer but use the language from option one,” “address the biggest risk,” “this paragraph is too long,” and they move. The rare, valuable thing in the loop is your judgment, not your typing. The more I leaned into being the human signal and stopped trying to also be a hand doing the work, the more I shipped.

Agent 提供数量。你提供品味、方向，以及反应和重定向的循环。你看返回结果，然后说：“第二个选项更接近，但用第一个选项的语言”，“处理最大风险”，“这一段太长”，然后它们继续移动。循环里稀缺而有价值的东西，是你的判断，不是你的打字。越是接受自己作为人类信号，而不是也试图成为那只干活的手，我交付得越多。

Be the taste. Let them be the hands.

你负责品味。让它们负责双手。

Hacks

Add value to the world by directing your agents with your brain. It still has value.

用你的大脑指挥 agent，为世界增加价值。它仍然有价值。

13. HyperFrames for Video, for All the Things

Video used to be the thing I outsourced or skipped. Now I make it the same way I make everything else: I talk, an agent builds, I react.

视频以前是我外包或直接跳过的东西。现在我做视频的方式和做其他东西一样：我说话，agent 构建，我反馈。

HyperFrames lets me build video as HTML, so an agent can write it. The loop is identical to code, the output is just an MP4 instead of a PR. Each one is a folder with a script.md, scene by scene, kinetic typography, captions carrying every beat. The agent turns that script into the composition and renders it. No editor, no timeline.

HyperFrames 让我可以把视频当作 HTML 来构建，所以 agent 可以写它。循环和代码完全一样，只是输出从 PR 变成了 MP4。每个视频都是一个文件夹，里面有一个 script.md，逐场景编写，动态排版，字幕承载每个节拍。Agent 把脚本变成 composition 并渲染出来。不需要编辑器，不需要时间线。

Launch reels I made this way:

我用这种方式做过的发布短片：

Granola CLI demo
Agent Cookie launch

The cost of a video dropped to a conversation, so anything that deserves one now gets one: launch reels, product demos, animated explainers, captioned clips. They don’t only go on X, either: I’ll drop a rendered demo straight into a PR, like this one on atlas-lean, Facebook’s AI research project.

视频的成本下降成了一次对话，所以任何值得拥有视频的东西，现在都会有视频：发布短片、产品演示、动画解释器、带字幕剪辑。它们也不只发在 X 上：我会把渲染好的 demo 直接放进 PR，比如 Facebook AI research 项目 atlas-lean 上的这个。

Hacks

Build video in HyperFrames: write a script.md, have your agent render it to MP4.
Upload GIFs to catbox and they render beautifully on GitHub, in PRs, READMEs, and issues.

在 HyperFrames 里构建视频：写一个 script.md，让你的 agent 渲染成 MP4。
把 GIF 上传到 catbox，它们会在 GitHub、PR、README 和 issue 里漂亮地渲染。

14. Your Notes Are Your Agent’s Knowledge Base

The strategy-folder trick from March generalized. The reason a plan gets better every time is that Claude has access to every prior plan I’ve written. Compounding context. So I pointed it at my whole brain.

三月时的 strategy-folder 技巧已经泛化了。计划每次变得更好的原因，是 Claude 能访问我以前写过的每一个计划。上下文在复利。所以我把它指向了我的整个大脑。

The tools I point it at:

我指给它看的工具：

Bear, with the Bear CLI. A decade of notes, meetings, half-baked ideas, and decisions an agent can read and write. Personal RAG without calling it that. The more I put in, the smarter every session gets.

Bear，加上 Bear CLI。十年的笔记、会议、半成形想法和决策，agent 都可以读写。这就是个人 RAG，只是我不这么叫它。我放进去的越多，每个会话就越聪明。

Obsidian. I don’t use it, but people love it for this and the plugin ecosystem is deep.

Obsidian。我不用它，但很多人很喜欢用它做这件事，而且插件生态很深。

gbrain. My synced brain across machines and agents.

gbrain。我的跨机器、跨 agent 同步大脑。

supermemory. A memory layer for agents a lot of people swear by. Digging in now, verdict to come.

supermemory。很多人强烈推荐的 agent 记忆层。我正在深入研究，结论之后再说。

The shape of the hack is the point: pick a notes tool with a CLI or an API, point your agent at it, and let your own knowledge compound.

这个技巧的形状才是重点：选择一个带 CLI 或 API 的笔记工具，把你的 agent 指向它，然后让你自己的知识复利。

Hacks

Point your agent at both: note-takers you write in (Bear, Obsidian) and agent brains that remember for you (gbrain by @garrytan, supermemory @supermemory). Pick ones with a CLI or API so it can read them.

把你的 agent 同时指向两类东西：你实际写作的笔记工具（Bear、Obsidian），以及替你记忆的 agent 大脑（@garrytan 的 gbrain、@supermemory）。选择带 CLI 或 API 的工具，这样它才能读取。

15. Work From Anywhere - My Mac mini

Hacks

Mosh, when you have to SSH in. It keeps the session local-feeling and responsive over bad wifi and roaming. On plain SSH, Claude Code crawls, every keystroke waiting on the round trip. The difference between usable and miserable on a remote box.

Mosh，用在你必须 SSH 进去的时候。它能让会话在糟糕 Wi-Fi 和漫游环境下仍然像本地一样响应。普通 SSH 下，Claude Code 会慢得爬行，每次按键都在等一次往返。在远程机器上，这就是可用和痛苦之间的区别。

Tmux, for airplanes. SSH into your remote machine inside a tmux session and the work runs there, not on your laptop. Wifi drops for twenty minutes over the Atlantic, you reconnect, attach, and it’s exactly where you left it. I’ve shipped features the whole flight home from Europe.

Tmux，用在飞机上。在 tmux 会话里 SSH 到远程机器，工作就在远程机器上运行，而不是你的笔记本上。飞越大西洋时 Wi-Fi 掉线 20 分钟，重新连接、attach，会话就在你离开的地方。我曾经在从欧洲回家的整个航班上交付功能。

Hermes
Agent Cookie

16. Proof: For Sending a Plan to a Colleague

A plan.md is perfect for me and useless to hand to someone who doesn’t live in a terminal. That was the last real gap, and Proof, also from Every Inc., closed it.

plan.md 对我来说很完美，但交给一个不生活在终端里的人就没用了。这是最后一个真正的缺口，而同样来自 Every Inc. 的 Proof 补上了它。

Opening a plan in Proof to read it like a document is nice. But where it became essential is sending a plan to a colleague. I drop a plan.md or a spec into Proof, send the link, and a non-terminal human can read it cleanly, comment inline, and those comments flow back into the loop with the agent. No more pasting markdown into Slack and watching it render into garbage. It’s human-in-the-loop review for the whole plan-file workflow, and it’s the first time sharing agentic work with a normal coworker hasn’t felt awkward.

在 Proof 里打开计划，像阅读文档一样阅读，这很好。但它真正变得不可或缺，是在我需要把计划发给同事时。我把 plan.md 或 spec 放进 Proof，发出链接，一个不使用终端的人也能干净地阅读、行内评论，而这些评论会流回 agent 循环。不再把 markdown 粘进 Slack，然后看它渲染成垃圾。这是整个计划文件工作流里的人类在环审查，也是第一次让我觉得把 agentic work 分享给普通同事不尴尬。

I loaded this very article into Proof while I was writing it. That’s how it got reviewed.

我写这篇文章时，就把它加载进了 Proof。这也是它被审阅的方式。

And I wrote this whole article in cmux with the Proof review open right alongside it:

我也是在 cmux 里写完整篇文章的，旁边同时打开 Proof 审阅：

Article content
cmux and Proof working together

Hacks

Share a plan: drop the .md into Proof (@EveryInc), send the link, pull comments back into the loop.

分享计划：把 .md 放进 Proof（@EveryInc），发送链接，再把评论拉回循环。

17. Write Your Own Skills

The biggest level-up isn’t using agents. It’s teaching them tricks that stick. Anything I do more than twice, I turn into a skill: a reusable command my agents can run forever. Automate your workflows by writing your own skills first.

最大的升级不是使用 agent，而是教会它们可以长期保留的技巧。任何我做超过两次的事情，我都会把它变成一个 skill：一个我的 agent 永远可以运行的可复用命令。先通过编写自己的 skill 来自动化你的工作流。

You don’t write them from scratch. The trick that unlocked this for me is to point your agent at a skill that already works and have it copy the shape. Literally: “look at the Compound Engineering skill and help me make one like this for [whatever I’m trying to automate].” It reads a great example, learns the structure, and scaffolds mine. I’ve built a pile of skills this way.

你不需要从零开始写。真正打开这件事的技巧，是把你的 agent 指向一个已经能工作的 skill，让它复制那个形状。字面意思就是：“看看 Compound Engineering skill，然后帮我为 [我想自动化的东西] 做一个类似的。” 它会阅读一个优秀示例，学习结构，然后帮我搭脚手架。我用这种方式构建了一堆 skill。

This is also most of my open source life now. If you look at my GitHub, the work is skills and the tools around them. last30days started as a skill I wanted for myself and is now open source past 26K stars. Printing Press is a whole factory for generating agent-native CLIs, and it’s my most-used personal tool, with over 320 merged PRs into it. I’m one of the top contributors to Compound Engineering itself. None of it was a grand plan. Each piece was a workflow I ran often enough that it was worth making the agent permanently good at it.

这也是我现在大部分开源生活的样子。如果你看我的 GitHub，会发现工作主要是 skill 以及围绕它们的工具。last30days 一开始只是我想给自己用的一个 skill，现在开源后已经超过 2.6 万 star。Printing Press 是一个生成 agent-native CLI 的完整工厂，也是我最常用的个人工具，里面已经合并了 320 多个 PR。我也是 Compound Engineering 本身的主要贡献者之一。这些都不是宏大计划。每一个部分，都是我运行得足够频繁的工作流，所以值得让 agent 永久擅长它。

Write the skill once. Every session after is faster. That’s the compounding part of Compound Engineering.

写一次 skill。之后每个会话都会更快。这就是 Compound Engineering 里“复利”的部分。

Hacks

Anything you do more than twice, make a skill:

look at the Compound Engineering skill and help me make one like this for [X].

任何你做超过两次的事情，都把它做成 skill。

18. Open Source: Contribute to the Projects You Love

The same loop that ships my own projects ships everyone else’s. I’ve had hundreds of PRs merged into open source, including Python, Go, OpenCV, Vercel’s Agent Browser, and OpenClaw. Not drive-by typo fixes, real features on tools I use every day.

交付我自己项目的同一个循环，也能交付别人的项目。我已经有数百个 PR 被合并进开源项目，包括 Python、Go、OpenCV、Vercel 的 Agent Browser 和 OpenClaw。不是路过式错别字修复，而是我每天使用的工具里的真实功能。

Somewhere along the way I started landing near the top of the contributor lists:

不知什么时候开始，我出现在一些贡献者列表的前列：

#3 on Compound Engineering, Superpowers, and Emdash
#4 on GStack and Paperclip
#6 on Vercel’s Agent Browser
#2 on Camoufox

Compound Engineering、Superpowers 和 Emdash 第 3。
GStack 和 Paperclip 第 4。
Vercel 的 Agent Browser 第 6。
Camoufox 第 2。

Pejman Pour-Moezzi jokes that when he opens a repo, spotting my face in the contributor grid has become his personal game of “where’s Waldo.”

Pejman Pour-Moezzi 开玩笑说，当他打开一个仓库时，在贡献者网格里找我的脸，已经成了他的个人版“威利在哪里”。

Article content
Contributors for Superpowers

But the merged PRs aren’t the real prize. It’s the people. I jump into the Discord, meet the maintainers, make actual friends. It’s been incredible for hiring too, I just hired an engineer I met this way for my new company. You contribute to something you love, you meet the people who love it, and it compounds.

但合并的 PR 并不是真正的奖品。真正的奖品是人。我进入 Discord，认识维护者，交到真正的朋友。这对招聘也非常有用，我刚刚为新公司雇了一位通过这种方式认识的工程师。你为自己热爱的东西贡献，认识同样热爱它的人，然后它会复利。

Hacks

Pick a tool you use every day, find one real thing it’s missing, and ship it with the same /ce-plan + /ce-work loop.
Show up in the project’s Discord. The PRs get you in the door; the people are why you stay.

选择一个你每天使用的工具，找到它真正缺少的一件事，然后用同样的 /ce-plan + /ce-work 循环交付它。
出现在项目的 Discord 里。PR 让你进门，而人是你留下的原因。

Add value on X.

在 X 上增加价值。

On X Pay $1-3/month to subscribe to people you respect. I pay$ 1/month to @garrytan and when I submit a PR I can send an X post to him and he gets a special notification that I’m a paying customer. I also pay for @jason @teknium @Teknium.

在 X 上每月花 1 到 3 美元订阅你尊重的人。我每月花 1 美元订阅 @garrytan，当我提交 PR 时，可以把 X 帖子发给他，他会收到一个特殊通知，知道我是付费客户。我也给 @jason、@teknium、@Teknium 付费。

Article content

19. My Current Laptop Setup

My two-year-old laptop was barely functional under everything I run on it, six Claude sessions plus Codex all day. So I upgraded to an M5 Max with 64GB of RAM. It’s a beast and I love it. It also still gets wrecked by the workload: my brand new machine has lasted as little as an hour on battery.

我那台用了两年的笔记本，在我运行的所有东西下面几乎已经撑不住了：整天六个 Claude 会话再加 Codex。所以我升级到了一台 64GB RAM 的 M5 Max。它是一头猛兽，我很喜欢。但它仍然会被工作负载打爆：我的全新机器在电池上最短只坚持过一小时。

So I panic-bought power. I carry an Anker battery brick everywhere now, and I keep an Anker charger in the Tesla so the car tops me up on the go.

所以我恐慌性购买了电力。现在我到哪里都带着 Anker 充电宝，并在 Tesla 里放了一个 Anker 充电器，这样车可以在路上给我补电。

Hacks

Never sleep:

sudo pmset -a disablesleep 1

Carry an Anker battery brick; keep a charger in the car.

随身带 Anker 充电宝；车里放一个充电器。

20. Printing Press: CLIs That Run Real Life

Most of these hacks live in the terminal. This is the one that leaves it. Printing Press is a fleet of CLIs that wrap real-world services so an agent can just do the errand. It’s its own project now at @ppressdev, past 3.7K stars, and I’m building it with @trevin.

这些技巧大多数都生活在终端里。这一个则离开了终端。Printing Press 是一组 CLI，它们封装现实世界的服务，让 agent 可以直接去跑腿。它现在已经是 @ppressdev 下的独立项目，超过 3700 star，我正在和 @trevin 一起构建它。

The piece that makes them actually work is auth, and that shipped last night: Agent Cookie. It hands a CLI your real browser session so it acts as you, no passwords to paste, nothing to re-auth. It’s what turns “an agent that knows about a service” into “an agent that’s logged into it.”

真正让它们能工作的部分是认证，而这部分昨晚刚刚发布：Agent Cookie。它把你的真实浏览器会话交给 CLI，让 CLI 以你的身份行动，不需要粘贴密码，也不需要重新认证。它把“知道某个服务的 agent”变成了“已经登录这个服务的 agent”。

A real afternoon, soup to nuts:

一个真实的下午，从头到尾：

Tesla preheat. Kids in the car in ten minutes: “preheat the car to 72.” The Tesla CLI fires, the car’s warm before we walk out.

Tesla 预热。孩子们十分钟后上车：“preheat the car to 72.” Tesla CLI 启动，我们走出去之前车已经暖好了。

Instacart. “reorder the usual and add coffee filters.” It builds the cart, I confirm, groceries are coming. Mid-conversation, didn’t break stride.

Instacart。“reorder the usual and add coffee filters.” 它构建购物车，我确认，杂货就送来了。整个过程发生在谈话中间，没有打断节奏。

ESPN polling. A session watched a game for me and pinged me only when it got close. I didn’t refresh anything, I got the one alert that mattered.

ESPN 轮询。一个会话替我盯着比赛，只在比分接近时 ping 我。我没有刷新任何东西，只收到了那个真正重要的提醒。

Alaska Airlines for the kids’ trip. Pulled fares and shoulder dates, checked our Atmos balance, fed it into /ce-plan, got a booking strategy with the cheapest days and buy reminders. From a soccer field.

Alaska Airlines，给孩子们的旅行用。它拉取票价和相邻日期，检查我们的 Atmos 余额，把这些喂进 /ce-plan，得到一个包含最便宜日期和购买提醒的预订策略。而我当时在足球场边。

Not “AI writes my code.” Agentic Engineering does the errands, watches the game, warms the car, and books the trip, while I’m doing something else.

这不是“AI 帮我写代码”。Agentic Engineering 会跑腿、看比赛、预热汽车、预订旅行，而我在做别的事。

Hacks

Install a ready-made CLI from the library at printingpress.dev to hand an errand straight to your agent.
Auth without the pain: Agent Cookie delivers your real browser session to a CLI so it acts as you.
The real hack: print your own. Take something you do all day, an API or a service you live in, and have Printing Press generate an agent-native CLI for it. The one you build for your own workflow is the one that changes how you work.

从 printingpress.dev 的库里安装现成 CLI，把跑腿任务直接交给你的 agent。
无痛认证：Agent Cookie 把你的真实浏览器会话交给 CLI，让它以你的身份行动。
真正的技巧：打印你自己的 CLI。拿一个你整天都在做的事、一个 API、一个你生活其中的服务，让 Printing Press 为它生成一个 agent-native CLI。为你自己的工作流构建的那个，才是改变你工作方式的那个。

21. The Honest Part: AI Psychosis

Agents were supposed to do all the work for us. Instead, every friend I have is working the hardest they ever have in their lives.

Agent 本来应该替我们完成所有工作。结果，我认识的每个朋友都在经历他们人生中最努力工作的阶段。

The easy response is take a break, touch grass. But that’s not what this is about. This is about addiction. Building with agents is the greatest video game ever made, and the loop is that good.

简单的回答是：休息一下，摸摸草。但这不是问题的核心。核心是成瘾。和 agent 一起构建，是人类做过的最伟大的电子游戏，而这个循环就是这么好。

I have friends I genuinely worry about. They’re so lit up by being able to build anything that they don’t do anything else. Then they launch, and there are no users. And that is okay. I’ve launched plenty of things with no users. The trap isn’t the empty launch, it’s vanishing into the build and losing the people around you.

我真的担心一些朋友。他们因为终于能构建任何东西而被彻底点燃，以至于不再做其他任何事。然后他们发布，结果没有用户。这没关系。我也发布过很多没有用户的东西。陷阱不在于空发布，而在于消失在构建里，并失去身边的人。

So be careful. Talk to your loved ones. Ask yourself if anyone actually wants the thing you’re making. And if the honest answer is that it’s just a tool for you, that’s okay too. Some of the best things I’ve built were only ever for me.

所以要小心。和你爱的人说话。问问自己，是否真的有人想要你正在做的东西。如果诚实答案是：这只是给你自己的工具，那也没关系。我做过的一些最好的东西，原本就只是给我自己用的。

If you do want an audience, it’s the Gary Vaynerchuk path he always preached for content. You start somewhere, posting into the ether hoping one person notices. Then three, then ten, then a hundred, and you work your way to thousands. Nobody starts at thousands. Same with anything you build.

如果你确实想要观众，那就走 Gary Vaynerchuk 一直强调的内容路线。你总要从某处开始，把内容发到虚空里，希望有一个人注意到。然后是三个、十个、一百个，再慢慢走向几千个。没人一开始就有几千人。你构建的任何东西都是一样。

Hacks

Take breaks. Touch grass.
Talk to your loved ones.
Build something people want, even if “people” is just you.

休息。摸草。
和你爱的人说话。
构建有人想要的东西，哪怕那个“人”只是你自己。

22. This Article Was Written This Way

This is a markdown file. Claude Code in cmux, me talking into Monologue: “evolve the no-IDE opener,” “make the don’t-read-the-plan section spicier,” “add the Tesla and Instacart story.” It rewrites, I react, and it’s in Proof for review. last30days fed the fresh material. No Zed this time, by the way. I stopped using it. No IDE. No typing code. Talk, plan, build. From a desk, a couch, a car, a soccer field.

这是一份 markdown 文件。Claude Code 在 cmux 里运行，我对着 Monologue 说：“evolve the no-IDE opener”，“make the don’t-read-the-plan section spicier”，“add the Tesla and Instacart story”。它重写，我反馈，然后文章进入 Proof 审阅。last30days 提供新材料。顺便说一句，这次没有用 Zed。我已经停用了它。没有 IDE。没有手敲代码。说话、计划、构建。地点可以是书桌、沙发、汽车、足球场。

That’s everything I know in June. A voice app, a plan-file plugin, a couple of config changes, a pile of tabs, a Mac Mini, two remote boxes, and a fleet of CLIs that run real life.

这就是我在六月知道的一切：一个语音 App，一个计划文件插件，几项配置修改，一堆标签页，一台 Mac Mini，两台远程机器，以及一支能运行现实生活的 CLI 舰队。

Hacks

Copy this whole article, paste it into your agent, and tell it to set up everything it can. Good things will happen to your agentic engineering workflow.

复制整篇文章，粘给你的 agent，让它设置所有能设置的东西。你的 agentic engineering 工作流会发生好事。