# 策展 · X (Twitter) 🔥🔥

> 📖 本站完整內容索引（documentation index）：[llms.txt](/llms.txt)

> 作者：Boris Cherny (@bcherny) · 平台：X (Twitter) · 日期：2026-06-09

> 原始來源：https://x.com/bcherny/status/2064034799711588805

## 中文摘要

Claude Code 發布週年演進為自主 Agent 生態。

**核心轉變與自動化**
Boris Cherny 指出，Claude Code 的開發模式已發生根本性變化，重點如下：
- **自動模式（Auto Mode）取代計劃模式**：隨著模型能力提升，已不再需要手動規劃步驟，自動模式能更高效地處理任務，並透過內建的安全性分類器確保執行過程的可靠性。
- **例程（Routines）與循環（Loops）**：透過設定例程，Agent 可自動監聽 GitHub Issue、錯誤報告並主動提出修復方案，甚至在開發者介入前就完成 PR 提交與驗證。
- **上下文極簡主義**：不再過度依賴提示工程，而是提供必要的工具與方法，讓模型自主提取上下文，避免微管理導致的效率下降。

**工程組織的典範轉移**
Boris Cherny 強調，Claude Code 的導入改變了 Anthropic 的工作流程，使 AI 成為企業運作的核心：
- **角色融合**：工程師、設計師、PM 與財務團隊皆能透過 Claude Code 直接參與程式開發與資料分析，打破了傳統職能分工。
- **端到端所有權**：開發者不再受限於繁瑣的程式碼審查與 CI 維護，能更專注於產品構思與使用者互動。
- **行動化開發**：透過遠端控制技術，Boris Cherny 現在能直接在行動裝置上監控並啟動 Agent 執行任務，實現了隨時隨地的開發體驗。

<video src="https://pub-75d4fe1e4e80421b9ecb1245a7ae0d1a.r2.dev/curated/1781010676218-j3jj4ook.mp4" poster="https://pub-75d4fe1e4e80421b9ecb1245a7ae0d1a.r2.dev/curated/1781010702678-htLaC2j8hqdefaultjpg.jpg" controls playsinline preload="metadata" style="max-width:100%;height:auto;display:block;margin:1rem 0"></video>
> Reflecting on a year of Claude Code

**對未來的展望**
影片中提到，Agent 的未來將朝向更長運行時間與更高自主性發展。Boris Cherny 認為，過去幾年累積的傳統工程經驗在 AI 時代需要重新學習，團隊應保持好奇心，透過與使用者共同構建，探索 Agent 在不同場景下的新應用形式。

## 媒體內容

**Reflecting on a year of Claude Code**

**逐字稿**

- `00:00` 當我們剛發布 Claude Code 時，那就像是一個小影片，我記得我把它貼到 Slack 上，（When we first released Claude Code, it was like a little video, and I remember posting it to Slack,）
- `00:04` 當時大概只有兩個人給了反應，大家看起來都很興奮。（and there was like two people that gave like the reaction, and like people were like excited.）
- `00:09` 對，我覺得這真的很酷，特別是對於我那些非常簡單的工程任務來說。（Yeah, I thought it was really cool, especially for my very easy engineering tasks.）
- `00:13` 它處理得相當不錯。（It was quite good at it.）
- `00:14` 這真是一個很好的說法，意思就是它其實沒那麼好。（That's like a really nice way to say that it wasn't really good.）
- `00:30` 真不敢相信我們發布 Claude Code 才過了一年。（I can't believe it's only been a year since we first launched Claude Code.）
- `00:34` 很難回想起那時候是什麼樣子了。（It's hard to remember what that was like.）
- `00:37` 跟我們現在做的事情相比，真的差很多。（It's so different than what we're doing today.）
- `00:40` 現在我手上有成群的 Agent 在處理各種事務。（Now I just have armies of agents that are doing stuff.）
- `00:44` 我會對一個 Agent 下指令，或者我有一個 Agent 會去指揮其他 Agent，而那些 Agent 又會再去指揮更多的 Agent，（I'm prompting one agent, or I have an agent that's prompting agents that's prompting agents,）
- `00:48` 就像是一個由數千個 Agent 組成的樹狀結構。（and it's like a tree of thousands of agents.）
- `00:50` 但我認為在處理這些事情時，最重要的觀念就是，每當 Claude 出錯時，（But I think it's just like the most important idea when working on this stuff is like every single time Claude Code makes a mistake,）
- `00:57` 我不會直接告訴 Claude 要怎麼做才對。（I don't tell Claude Code to do it differently.）
- `00:58` 我會讓它寫進 CLAUDE.md，或者建立一個 skill 之類的東西來處理。（I tell it to write it to the QuadMD, or to like make a skill or something to do it differently.）
- `01:04` 如果你能做到這一點，Claude 就可以一直運作下去。（And if you can do this, then Claude Code can just like run forever.）
- `01:07` 還有另一點我們意識到的是，驗證真的非常重要。（And I think the other thing that we kind of realized is the verification is really important.）
- `01:11` 我們之前沒意識到這一點。（Like we didn't realize that.）
- `01:12` 我常從我們接觸的開發者和企業那裡聽到這個問題。（I hear this come up a lot with developers and enterprises that we meet with.）
- `01:17` 你有什麼建議能讓 Claude Code 在驗證方面表現得更好嗎？（What are your tips for making a really good, making Claude Code really good at verification?）
- `01:21` 我感覺這件事大家都誤解了，（I sort of feel like this is this thing that just like everyone misunderstands,）
- `01:24` 因為每當我們談到驗證時，大家想到的都是單元測試，（because whenever we talk about verification, people are thinking like unit tests,）
- `01:28` 或是像 lint 或型別檢查之類的。（or they're thinking like lint or like type check.）
- `01:31` 這些東西顯然很容易自動化。（These are the things that are obviously really easy to automate.）
- `01:34` 而且這些東西早就已經自動化了。（And these are the things that were already automated.）
- `01:36` 但實際上，當我們談到 Agent 的驗證時，情況略有不同。（But actually, when we talk about verification for agents, it's something slightly different.）
- `01:40` 這更像是：Agent 能不能執行那個東西？（It's like, can the agent run the thing?）
- `01:42` 這需要花點心思去弄清楚到底該怎麼做，（It takes a little bit of mental work to figure out how exactly do you do this,）
- `01:45` 因為這通常不是直接了當的。（because it's often not straightforward.）
- `01:47` 我認為這就是挑戰之一。（And I think that's like, that's one of the challenges.）
- `01:49` 我記得在 Opus 4 時，Claude 會自我測試。（I remember with Opus 4, Cloud tested itself.）
- `01:54` 我們只是把它連接到 Opus 4。（And we just like hooked it up to Opus 4.）
- `01:58` 我當時說：「Claude，建立一個功能，然後在 Bash 裡測試你自己。」（And I was like, Cloud, build a feature and then test yourself in like Bash.）
- `02:02` 它打開了一個小型的 Claude CLI，並測試了它自己的功能。（And it opened a little Cloud CLI and tested its own feature.）
- `02:07` 我當時心想：哇，這太瘋狂了。（And I was just like, whoa, it's crazy.）
- `02:10` 現在我們已經習以為常了。（Like now we're so used to it.）
- `02:12` 現在我們有這些迴圈在跑，例如針對 iOS 模擬器、（Like now, you know, now we have these loops going for, you know, like the iOS simulator）
- `02:15` Android 模擬器，還有桌面電腦。（and the Android simulator and like computers for desktop.）
- `02:18` 這已經不稀奇了。（Like it's not surprising.）
- `02:20` 但在當時，那真的很瘋狂。（But back then, that was crazy.）
- `02:22` 你們現在是怎麼做的？（How are like, how are you doing it?）
- `02:24` 我最近主要是在開發桌面應用程式。（So I've been mainly hacking on the desktop app these days.）
- `02:27` 團隊中的一位工程師新增了一個桌面開發 skill，（And one of the engineers on the team actually added this desktop development skill）
- `02:31` 教導 Claude 如何執行本機桌面應用程式。（that teaches Cloud how to run the local desktop app.）
- `02:34` 我一直讓它使用這個功能。（And I've been having it use it.）
- `02:36` 它有時還是會遇到問題，或是與測試環境（staging environment）產生衝突。（And it still runs into issues or like bugs with the staging environment sometimes.）
- `02:42` 所以在這種情況下，我會讓它讀取 Slack 並理解：（And so what I have it do is in those cases, I have it read Slack and understand,）
- `02:46` 「嘿，現在測試環境當機了嗎？」（hey, is staging down right now?）
- `02:48` 或者「有沒有其他人已經遇到這個問題了？」（Or is there, has someone else already hit this?）
- `02:51` 然後當它除錯完整個問題後，我會告訴它更新那個桌面開發 skill。（And then when it debugs the whole issue, I tell it to update the desktop development skill.）
- `02:56` 這個 skill 的作用是讓 Claude 啟動一個本機桌面應用程式，（What this skill does is Cloud actually spins up a local desktop app）
- `03:00` 並使用電腦操作功能在上面點擊。（and it uses computer use to click around on it.）
- `03:02` 所以當我新增一個新的使用者體驗（UX）時，它會點擊並呼叫該功能。（And so when I add a new UX, it clicks around to invoke the new UX.）
- `03:07` 它也會測試邊緣案例。（It also tests edge cases.）
- `03:09` 當有問題時，它會修復並重新檢查。（And when there's an issue, it fixes it and rechecks.）
- `03:12` 老實說，這是我們團隊最讓我喜歡的一點，每個人都會寫程式。（This is like, honestly, one of my favorite things about this team is everyone codes.）
- `03:17` 我從未待過一個連產品經理（PM）都會寫程式的團隊。（I have never been on a team where my PM would code.）
- `03:23` 這真的很瘋狂。（And it's like crazy.）
- `03:24` 而且你的程式碼寫得很好。（And your code is really good.）
- `03:26` 你太客氣了。（You're too nice.）
- `03:28` 但我也覺得這變得越來越容易了，因為基本上，（But I also just feel like it's also just becoming easier because it's like,）
- `03:32` Claude 會負責寫程式碼。（essentially, Cloud writes the code.）
- `03:34` 所以更重要的是：你有什麼想法？（And so what matters a little more is like, what's the idea that you have?）
- `03:38` 我覺得如果你是一個擁有產品脈絡和商業脈絡的人，（And I feel like if you're a person that has like the product context and the business context,）
- `03:42` 並且在思考設計和使用者需求，你自然會想出更好的點子。（and you're thinking about the design and the user, you're just going to come up with better ideas.）
- `03:46` 所有的角色似乎都在融合。（It's kind of like all the roles are merging.）
- `03:48` 我記得剛開始看到我們的設計師 Megan 提交 PR 時，我簡直嚇壞了。（I remember seeing Megan, our designer's PRs, and I was just horrified at the beginning.）
- `03:52` 我心想：「天哪，為什麼 Megan 會提交 PR？」（I was like, oh, my God, why is Megan putting up PRs?）
- `03:54` 然後她說：「對啊，我只是在修復那個按鈕。」（And then she was like, yeah, yeah, I'm just like, I'm fixing the button.）
- `03:57` 我說：「好吧，那程式碼看起來不錯。」（And I was like, okay, all right, well, the code looks good.）
- `04:00` 所以也許這樣沒問題。（So maybe it's fine.）
- `04:02` 我覺得現在這已經完全正常了。（And I feel like now it's just like, it's totally normal.）
- `04:04` 沒錯。（Yeah.）
- `04:04` 我們在所有接觸的企業中都看到了這種現象。（We see this across all the enterprises we talk with.）
- `04:07` 工程師會先採用 Claude Code。（Like, it's the engineers adopt Claude Code first.）
- `04:10` 然後周邊的角色看到後會覺得：「哇，這東西太強大了。」（And then the edge adjacent roles look over their shoulder and they're like, whoa, this thing is very powerful.）
- `04:16` 讓我試試看。（Let me try it out.）
- `04:17` 我們發現這真的很瘋狂。（And we found, it's crazy.）
- `04:19` 我們的設計師變得更有效率，可以直接在應用程式中製作原型並進行修改，而不需要請工程師幫忙。（We found that like our designers are more productive, making prototypes and making changes directly in the app instead of paying an engineer.）
- `04:26` PM 也在應用程式中進行修改。（PMs are making changes in the app.）
- `04:29` 我們的財務團隊也在使用 Claude Code。（Like our finance team runs in Claude Code.）
- `04:32` 他們在那裡進行預測。（They do their projections there.）
- `04:34` 資料科學團隊也是。（Data science.）
- `04:35` 如果你跟我們的資料科學家聊聊，真的很酷。（Like if you talk with our data scientists, it's so cool.）
- `04:38` 每個人螢幕上都開著 Claude Code。（It's just like everyone just has Cloud codes up on their screens.）
- `04:42` 我覺得它對不同角色來說都非常實用。（I feel like it's remarkably versatile for different roles.）
- `04:46` 你覺得現在有哪些使用案例正在挑戰極限？（What do you feel like nowadays are like the use cases that are pushing the limit?）
- `04:51` 我最興奮的一個是「例行程序（routines）」。（One that I'm super excited about is routines.）
- `04:54` 我們團隊有一位工程師在我們所有的產品中推出了語音模式。（There's one engineer on our team who launched voice mode across all of our products.）
- `04:59` 他設定了一個例行程序，會監聽每一個進來的工單、每一個 GitHub Issue，以及每一個關於語音模式的錯誤報告。（And he has this routine set up that just listens for every ticket that comes, every GitHub issue, every bug report about voice mode.）
- `05:08` 他的 Claude 會自動接收這些訊息，主動提出修復方案，並將 PR 發送給他。（And his cloud just picks it up, proactively puts up a fix, and then pings the PR to him.）
- `05:14` 當他成功為語音模式做到這一點後，他想：「好吧，我們收到很多其他沒被回應的意見回饋。」（And when he got that working for voice mode, he thought, okay, we're getting a lot of other feedback that isn't being responded to.）
- `05:21` 所以他也設定了一個例行程序來監聽這些回饋。（So he also set up a routine to listen for that.）
- `05:24` 我發布了一個小功能，裡面有一個我沒注意到的邊緣案例。（So I shipped this small feature, and there was like an edge case in it that I didn't see.）
- `05:29` 有人回報了這個錯誤，我原本打算那天晚上來處理。（And so someone filed a bug for it, and I was going to get to the bug that night.）
- `05:34` 當我的 Claude 正在工作時，它說：「等等，另一個 Claude 已經修復這個問題了。」（And as my Claude Code was working, it said, wait a second, another Claude Code has already fixed this.）
- `05:39` 我心想：「這怎麼可能？」（And I was like, how is this possible?）
- `05:40` 我之前從未跟他討論過這個功能。（Like, I've never talked to him about this feature before.）
- `05:42` 所以我聯繫了他，問他：「你是怎麼這麼快修復它的？」（And so I pinged him, and I was like, how did you fix this so quickly?）
- `05:45` 他說他有另一個例行程序，會自動搜尋五小時內未被回應的錯誤報告並提出修復方案。（And he says he has another routine that just looks for bug reports that haven't been responded to in five hours and puts up a fix.）
- `05:52` 他會直接合併那些容易驗證的項目。（And he merges the ones that are easy to verify.）
- `05:55` Claude 現在一直這樣告訴我。（Claude Code tells me this, like, all the time now.）
- `05:57` 說別人已經修復了？（That someone else has already fixed it?）
- `05:59` 總是有另一個人的 Claude 在處理這些事。（There's always, like, another person's Claude Code that's working on it.）
- `06:01` 沒錯，這就是改變之一。（It's like, yeah, that's been one of the changes.）
- `06:04` 我覺得不久前，我們還在摸索如何使用例行程序。（I feel like we're, a while ago, we were trying to figure out, like, how to use routines.）
- `06:08` 我覺得 Agent SDK 是我們能以程式化方式使用 Claude Code 的第一個想法。（And I feel like just, like, the agent SDK was this first idea that we could use Claude Code code programmatically.）
- `06:15` 但剛開始時，我們並不清楚該如何使用它，以及用它來做什麼。（But I feel like at the beginning, it just wasn't obvious how do we use it, what do we use it for.）
- `06:20` 我認為例行程序是第一個真正顯而易見的應用。（And I think routines are the first really obvious application.）
- `06:24` 而且它幾乎包辦了所有的程式碼審查。（And I don't know, like, it just does, like, all the code review.）
- `06:27` 它會監管每一個 PR。（It babysits, like, every PR.）
- `06:30` 你還記得以前嗎？你必須親自回應程式碼審查的意見。（You remember back in the day, you used to actually have to, like, respond to code review comments.）
- `06:34` 你必須親自修復 CI。（You used to have to, like, fix CI.）
- `06:36` 你必須親自進行 rebase。（You used to have to rebase.）
- `06:38` 對。（Yeah.）
- `06:39` 我已經很久沒做這些事了。（Like, I haven't done that in a long time.）
- `06:40` 沒錯。（Yeah.）
- `06:41` 當你在 CLI 中與 Claude 同步工作時，你最常用的功能是什麼？（When you're in the CLI and you're synchronously working with Claude Code, what are your go-to features?）
- `06:47` 好吧，以前是計畫模式（plan mode）。（Okay, what they used to be is plan mode.）
- `06:49` 我現在不用那個了。（I don't use that anymore.）
- `06:50` 那你改用什麼？（What do you use instead?）
- `06:52` 自動模式（auto mode）。（Auto mode.）
- `06:53` 自動模式。（Auto mode.）
- `06:53` 它是最棒的。（It's the best.）
- `06:54` 取代了計畫模式？（Instead of plan mode?）
- `06:55` 取代了計畫模式。（Instead of plan mode.）
- `06:56` 對，因為較新的模型其實不再需要計畫步驟了。（Yeah, because the newer models, they don't actually need, like, a planning step anymore.）
- `07:00` 我認為這對於 Opus 4 到 4.5 左右的版本非常重要。（I think this was really important for, like, Opus 4 through maybe 4.5.）
- `07:05` 但從 4.6 開始，絕對是 4.7 之後，它就不再需要那個計畫步驟了。（Then I think starting with 4.6 and definitely with 4.7, it just doesn't need that planning step.）
- `07:09` 我想有些人可能還在用。（I think some people still use it.）
- `07:10` 他們喜歡保留那個產出物。（They like to have that artifact.）
- `07:11` 但我不用。（I don't use it.）
- `07:12` 我所有事情都用自動模式。（And I just do auto mode for everything.）
- `07:14` 因為我啟動 Claude。（Because then I start my Claude Code.）
- `07:16` 它就開始工作。（It starts to work.）
- `07:17` 然後我就去處理下一個 Claude 的任務。（And then I just, like, move on to the next Claude Code.）
- `07:19` 我不需要坐在那裡盯著它看。（And I don't have to sit there and watch it.）
- `07:20` 但在早期階段，Claude Code 有權限提示模型，對吧？（But from the very early stages, we had this, like, permission prompts model for Claude Code code, right?）
- `07:25` 它執行一個工具，然後問你：「嘿，你確定要執行這個工具嗎？」（Like, it runs a tool and then it asks you, like, hey, are you okay running this tool?）
- `07:29` 你必須回答是或否。（And you had to say yes or no.）
- `07:31` 在一年半前，那已經是我們能做到的極限了。（And at the time, that was kind of the best we had a year and a half ago.）
- `07:34` 因為我們當時沒有分類器。（Because we didn't have, you know, classifiers.）
- `07:36` 模型也沒有像今天這樣對齊得這麼好。（The model was not as well aligned as it is today.）
- `07:38` 所以自動模式是一個巨大的進步。（So auto mode was just such a big step up.）
- `07:41` 因為實際上，你並不想閱讀這些請求。（Because actually, you don't want to read most of these requests.）
- `07:44` 將請求路由到不同的模型並讓它進行安全性檢查，效果好得多。（Just routing it to a different model and having it check for security works so much better.）
- `07:49` 如果某件事看起來有點可疑，或者不是你想執行的指令，或者不安全，模型就會直接拒絕。（And if a thing, like, is a little sus or, you know, this isn't a command that you think you want to run or it's not safe, the model will just deny it.）
- `07:57` 然後你可以回頭再允許它。（And then you can go back and you can allow it later.）
- `08:00` 我認為這是階段性的改變之一。（I think this has been one of those, like, step changes.）
- `08:02` 我們在一年前根本不可能做到這一點。（We just, there's no way we could have done this a year and a half ago.）
- `08:04` 當你接受 99% 的請求時，人類的天性就是閱讀時會感到麻木。（It's just human nature when you accept 99% of requests that your eyes just glaze over when you read it.）
- `08:11` 所以實際上，我們認為自動模式比閱讀每一個權限提示更安全。（And so actually, we feel that auto mode is more safe than reading every single permission prompt.）
- `08:16` 因為這意味著你只會關注最重要的事情。（Because it means that you're only paying attention to the most important thing.）
- `08:20` 而不是被那些 99% 都是「是」的垃圾訊息淹沒。（And not, like, being spammed a bunch of things that are just 99% yes.）
- `08:24` 我認為安全性就是這樣，你可以談論它，但要真正正確地執行又是另一回事。（I think security is one of these things, like, you can talk about it and then it's a totally different thing to actually do it correctly.）
- `08:30` 因為它看起來並不總是如你所想的那樣。（Because it just doesn't always look the way that you think it's going to look.）
- `08:33` 這一切都在於持續的紅隊測試（red teaming）、滲透測試，以及建立威脅模型，並利用這些來找出這個東西會如何被攻擊。（And it's just all about, like, always red teaming, always pen testing, always looking, you know, always having a threat model and then using that to figure out, you know, how is this thing going to get attacked?）
- `08:43` 人們會如何進行提示詞注入（prompt injection）？（How are people going to get prompt injected?）
- `08:44` 沒錯。（Exactly.）
- `08:45` 我覺得團隊對此非常執著。（And I just feel like the team is just, like, obsessed with this.）
- `08:48` 這非常重要，因為結果就是我信任 Agent 的執行。（And it's so important because, as a result, I just trust the agent to run.）
- `08:53` 我可以繼續處理其他任務，並同時運行第二個 Agent。（And I can move on and I can just have, like, a second agent.）
- `08:57` 如果我不信任它，我就無法做到這一點。（And if I didn't trust it, then I just wouldn't have been able to do that.）
- `09:00` 在內部，為了將自動模式推向使用者，我們必須先真正信任它。（And internally, to actually get auto mode out to our users, we needed to really trust it first.）
- `09:07` 所以我們收集了數千個完整的 Agent 軌跡和權限提示的轉錄，並讓自動模式分類它是否安全。（And so what we did was we collected thousands of transcripts of, like, an entire agent trajectory and a permission prompt and had auto mode classify whether or not it was safe.）
- `09:18` 它在這方面表現得非常好。（And it was extremely good at this.）
- `09:20` 然後我們找來紅隊測試人員，讓他們嘗試進行提示詞注入並駭入程式庫。（So then we got red teamers and we asked them to try to prompt inject and try to hack the code base.）
- `09:26` 我們利用這些來建立評估標準（evals），並確保所有這些攻擊都被拒絕。（And we used this to create evals and made sure that all of these were denied.）
- `09:30` 接著我們讓內部的團隊嘗試進行提示詞注入並駭入 Claude Code 的自動模式。（And then we had our own internal teams try to prompt inject and hack Claude Code, Claude Code's auto mode.）
- `09:37` 然後我們改進了自動模式，確保我們能捕捉到所有這些攻擊。（And then we improved auto mode to make sure that we caught all of these.）
- `09:40` 所以它不僅能保護你免受現今野外漏洞的威脅，還能抵禦我們所能構建的最聰明的攻擊。（So it's not only just protecting you against the vulnerabilities that are out there in the wild today, but the most intelligent attacks that we can construct.）
- `09:49` 沒錯，這老實說是一種很奇怪的方法。（Yeah, I mean, it's like, it's honestly like a weird approach.）
- `09:52` 過去一年裡，每當有人提出某個功能時，我都會覺得：「啊，不，這絕對行不通。」（I feel like there's like all these features the last year where the first time someone pitched it, I was like, ah, no, no way that's not going to work.）
- `09:58` 但我發現隨著時間推移，我學到其實是我錯了。（way that's not gonna work and i feel like over time i've just learned like i'm actually wrong）
- `09:59` 我經常有這種感覺。（And I feel like over.）
- `10:01` 因為在模型上進行開發真的很奇怪，這就像是所有我多年來學到的工程知識，（like so often now because like building on the model is so weird yeah it's just like all this）
- `10:07` 很多我都必須拋棄。（like engineering stuff that i've learned over the years like so much of it i just have to like）
- `10:11` 這就是現在工作的一部分，我們正在基於新事物進行開發，（throw out and this is just like part of what the job is now like we're building on a new thing and）
- `10:14` 我們必須重新學習。自動模式絕對是其中之一，我第一次聽到時，（we just have to relearn it and i auto mode was definitely one of these i was like the first time）
- `10:19` 我心想：「把提示詞路由到模型？不可能，那行不通。」但結果證明，從經驗來看，它運作得非常好。（i heard it i was like route the prompt to a model no way that's not gonna work and then it actually）
- `10:23` 我聽說你也很喜歡 Loop，對，我愛死 Loop 了。（turns out empirically it works really really well i heard you also love loop um i yeah i love loop）
- `10:29` 你是怎麼使用的？我想對於 Loop，我們經歷了一個轉變，大約一年半前，（how do you use it i think for loop there's this transition that we went through like a year and）
- `10:35` 我們當時想：「好吧，有原始碼，但工程師真正應該互動的對象，（a half ago where we were like all right there's source code but actually the thing an engineer）
- `10:41` 也許不是原始碼，而是 Agent。」所以我們跨出了這一步：（should interact with maybe it's not the source code maybe it's the agent and so we made this leap of）
- `10:46` 我不寫原始碼，我跟 Agent 對話，然後 Agent 幫我寫原始碼。（like i don't write the source code i talk to an agent and the agent writes the source code for me）
- `10:51` 我覺得現在我們正在跨出下一步：我不跟 Agent 對話了，（and i think right now what's happening is we're making the next leap i don't talk to an agent）
- `10:56` 我跟 Loop 或例行程序對話，它會幫我提示 Claude，這太瘋狂了。（anymore i talk to a loop or i talk to a routine and it prompts Claude Code for me and it's just it's crazy）
- `11:04` 這才過了一年半，卻有了兩次巨大的躍進。如果退一步看，（i mean it's been like it's a year and a half and this is like two big leagues if you take like a step）
- `11:08` 你是如何看待整個工程組織的變革？我要戴上我的商業分析帽了。（back how are you seeing entire engineering orgs change i'm gonna put i'm gonna put on my business）
- `11:13` 我有一個最喜歡的案例研究，來自 90 年代的哈佛商業評論，（cat hat i i have this like favorite case study this is like a harvard business review from the 90s）
- `11:18` 他們當時在討論：「電腦已經普及了，為什麼我們沒看到生產力提升？」（and they were talking about like computers are here why are we not seeing the productivity benefits）
- `11:22` 這是一個非常棒的快照，記錄了當時的真實感受。（and it's just this like amazing snapshot into like what it actually felt like at the time）
- `11:27` 因為人們以前使用大型主機，後來公司轉向個人電腦，（because like you know people used to use mainframes at some point companies switched to personal）
- `11:31` 這是一個新事物，公司正在摸索如何使用它，（computers it was sort of a new thing and companies were trying to figure out how to how they use it）
- `11:35` 就像他們現在摸索如何使用 AI 一樣。結果發現，要從電腦獲得生產力提升，（the same way they're trying to figure out how to use ai right now and it turned out that to get the）
- `11:40` 你不能只是保留紙本檔案櫃和紙筆作業流程，然後在旁邊放一台電腦做點小事。（productivity benefits from computers what you had to do isn't like you have your paper filing cabinet and）
- `11:46` 實際上，你必須拋棄檔案櫃，拋棄所有的紙筆，（your like paper and pen business process and then there's like a computer on the side that does）
- `11:50` 然後把電腦放在中心，所有事情都必須透過電腦運作。（something actually what you have to do is you throw out the filing cabinet you have to throw out all your）
- `11:55` 它必須成為每個商業流程的核心。我覺得在 Anthropic，我們做到了這一點，（paper and all your pens and then you put a computer in the center and everything has to run through the）
- `11:59` 當你入職時，你不會問別人問題，沒人會問我問題，（computer it has to be at the center of every business process and i i feel like at anthropic we do）
- `12:03` 他們入職時，你可能也一樣，他們會問 Claude。這有點奇怪，（this thing where when you onboard you don't ask people questions like no one asks me questions when they）
- `12:09` 這是我待過的第一家這樣的公司。我覺得對我們來說，Claude 就是一切的核心。（onboard you probably have the same thing they ask Claude Code and this is kind of weird like this is the first）
- `12:15` 每當我有問題，我就問 Claude；每當我寫程式，我就用 Claude；每當我需要程式碼審查，（company i've been at like that and i feel like for us Claude Code is just at the center of everything）
- `12:19` Claude 就會做；每當我需要安全性審查，Claude 就會做；每當我需要填寫表格，（whenever i have a question i ask Claude Code whenever i write code i use Claude Code whenever i need a code review）
- `12:23` Cowork 就會做。所以 Claude 就是一切的核心。我覺得那些真正搞懂的公司，（Claude Code does it whenever i need a security review Claude Code does it whenever i need to you know fill out a form）
- `12:29` 現在已經有很多了，他們就是把 Claude 放在核心位置。（or something co-work does it so it's just like Claude Code is at the center of everything and i i feel like）
- `12:34` 但我認為對電腦而言，轉型花了 10 到 15 年，但對於 AI，（the companies that are really figuring it out and there's a bunch of them now they're just putting）
- `12:38` 因為我們大部分的工作已經數位化了，而且 Claude 可以使用電腦、（Claude Code at the center of it but i think for computers the transition took 10 to 15 years but actually）
- `12:43` 寫程式並執行程式，這個轉型發生得快得多。我覺得這真的非常令人興奮。（for ai because so much of our work is already ready digitized and Claude Code can use the computer）
- `12:49` 現在我不需要再打擾別人了。當我與人互動時，是因為這很有趣，（and it can write code and run code this transition is happening a lot faster i think it's just like）
- `12:54` 我可以與他們合作，我們可以一起創造東西，而不是因為我需要從他們那裡得到什麼，（really it's just really exciting like i feel like now i don't have to bug people anymore and when i）
- `13:00` 因為 Claude 現在確實可以處理很多那樣的事情。我也覺得身為工程師，（interact with people it's because it's like fun and i get to collaborate with them on stuff and we get）
- `13:05` 我從未像現在這樣享受工程工作，因為那些繁瑣的部分我都不需要做了。（to create something together it's not that like i need them i need something you know from them）
- `13:10` 我只是在想點子，與客戶交談，我不再有待辦事項清單了，（because like Claude Code can actually do a lot of that stuff now and i also feel like as an engineer i've）
- `13:14` Claude 幫我建立了所有東西，所以我的工作就是想出這些點子，這真的很有趣。（just never had this much fun doing engineering because they're like the tedious part i don't）
- `13:18` 好吧，有個問題：未來是產品導向還是工程導向？每個人都會成為 PM，還是每個人都會成為工程師？（have to do like i'm just coming up with ideas i'm talking to customers and every idea i don't like i）
- `13:24` 每個人都會兩者兼具。我強烈認為這些角色正在融合。看看我們的團隊，（don't have a to-do list anymore like Claude Code just builds everything and so my job is to come up with）
- `13:28` 我們的產品團隊都會寫程式，我們的開發者關係團隊都會寫程式，我們的設計團隊都會寫程式，（these ideas and it's just so fun okay so here's a question is the future product or engineering like）
- `13:33` 然後看看我們的工程師，他們很多人都能端到端地交付產品。他們有建構的想法，（is everyone going to be a pm or is everyone going to be an engineer everyone's going to be both）
- `13:37` 他們親手建構，他們與法務和行銷合作，弄清楚如何向世界傳達這一點，並確保它是安全的，還有安全性團隊也是。（i i feel pretty strongly that these roles are merging like when we look at our team our product）
- `13:43` 很多時候，他們就是端到端地完成整個流程。所以我認為現在 AI 真的造福了那些充滿好奇心、（team all rights code our dev role team all rights code our design team all rights code and then we）
- `13:50` 有產品品味、熱愛端到端所有權的人。現在很多人都在運行數百個 Agent，（look at our engineers and a lot of them ship products end to end they have an idea for what）
- `13:55` 你認為人們在從單一 Agent 過渡到多個，甚至數百個 Agent 時，應該採用什麼產品？（to build they build it they work with legal and marketing to figure out how we communicate this to）
- `14:01` 直到最近，我寫程式的方式是開六個終端機分頁，裡面有同一個 repo 的六個 git checkout，然後我在它們之間切換。（the world and make sure it's safe and with security too and a lot of times they just see through this）
- `14:06` 現在完全不同了。我只有一個分頁，我使用我們剛發布的新 Agent 視角，這太棒了，（whole process end to end so i think right now ai really benefits people who have a lot of curiosity）
- `14:13` 我很高興我們花時間迭代它，讓它變得這麼好。（how a lot of product taste who love to have this like end-to-end ownership and now a lot of people）
- `14:19` 而且我也使用桌面應用程式，因為我不必在那裡擺弄 checkout，它會幫我處理工作樹（work tree）的複製。（are running like hundreds of agents what are the products that you think people should be adopting as）
- `14:25` 我六個月前沒想到的是，現在我一半的工程工作都不在電腦前了。（they transition from single to multiple to hundreds until recently the way that i wrote code was i had like）
- `14:32` 我有太多 Agent 在運行，所以我直接從手機開始。我使用遠端控制，這現在太神奇了。（six terminal tabs with six git checkouts of the same repo and then i would just like tab between them）
- `14:38` 我會在電腦上啟動一些東西，然後用手機遠端控制，我可以四處走動，去買杯咖啡，（now it's pretty different i have like one tab i use the new agent view that we just shipped it's like）
- `14:43` 然後檢查我的 Agent，也許再啟動另一個 Agent。有時我在跟人聊天，（so good and i'm so glad that we took a while to iterate on it to make that really good）
- `14:48` 我們想出一個新點子，我就會當場啟動一個 Agent，用語音模式跟它對話，讓它建構東西，（and i also use the desktop app because i don't have to fiddle with checkouts that way it just like）
- `14:53` 我甚至不需要回到電腦前了。（you know it does the work tree cloning like it creates the work trees for me）
- `14:58` 我記得你剛開始這樣做的時候，你會離開工作崗位，把電腦留在桌上，插著電，螢幕鎖定，（and the thing that i would not have expected six months ago is probably half my engineering now）
- `15:03` 我以為你之後會回到辦公室拿電腦，但那已經很晚了，我心想：（i don't have my phone so i just have like i have so many agents running that i just start from my）
- `15:08` 「嗯，也許你只是不小心把它留在這了。」結果第二天又發生了，（phone i use a remote control which is like amazing now and like i'll start something on my computer and）
- `15:14` 第三天又發生了，我心想：「等等，這太奇怪了，因為你還在提交 PR，你的電腦就在我旁邊。」（then i'll just remote control in for my phone and i'll just like walk around i'll like get coffee and）
- `15:18` 我記得你回應說：「對啊，我正在沙發上寫程式。」沒錯，那週遠端控制功能變得非常強大。（then i'll check in on my agents and maybe i'll start another agent and sometimes i'm like talking to）
- `15:23` 對了，另一個使用者一直問的問題是，在大型企業中，該如何進行脈絡工程（context engineering）？（someone and we come up with a new idea i'll just start an agent on the spot i'll like talk to it）
- `15:27` 人們以前談論提示詞工程，談論脈絡工程，這與當時模型所處的階段相符。（with voice mode and just have it build something and i don't even have to go back to my computer）
- `15:31` 在 Sonnet 3.5 的時代，你必須進行提示詞工程；在 Opus 4 的時代，你必須進行脈絡工程。（anymore i remember when you started doing this because you would actually leave work have your）
- `15:36` 但對於今天的模型，你根本不需要做這些。你給它最小化的系統提示詞、最小化的工具，（computer on your desk open plugged in screen locked and i just thought you would like come back）
- `15:41` 然後讓模型自己去搞定。你只需要給模型一些獲取脈絡的方法，我認為這是最重要的。你怎麼看？（to the office at some point to get your computer but then it would be like pretty late and i was like）
- `15:45` 我的看法非常相似。我是脈絡極簡主義者，所以我的基本哲學是：只告訴模型它需要知道的資訊，剩下的讓它自己去搞定。（hmm maybe you just like left it here by accident and then it happened again the next day）
- `15:50` 我認為當你給模型太多脈絡時，就像是在微觀管理它，有時模型知道更好的方法來達到相同的結果。（and it happened again the next day and i was like wait this is so weird because you're landing pr so）
- `15:55` 我個人傾向於給模型這種自由，而且總體來說，我們也在讓我們的 harness 更精簡，這樣你就有更多空間放自己的提示詞，（your computer is right next to me and i remember you responding and you're like yeah i'm coding from）
- `16:00` 讓它能更好地遵循你的提示詞。現在有各種不同的方式使用 Claude，但我感覺一年後，（my couch yeah that was the week that remote control got really good yeah so another thing that users are）
- `16:06` 這將會是一套全新的東西，如果還是這些東西，那才令人驚訝。因為我認為我們現在正看到巨大的趨勢，（asking about all the time is how do you do context engineering especially in a large enterprise this is）
- `16:12` Agent 運行的時間更長，它們更自主。我很少一次只運行一個 Agent，通常是幾個、幾十個、幾百個甚至幾千個。（the thing you know people used to talk about prompt engineering they used to talk about context）
- `16:15` 所以它的外觀形式將會與過去完全不同。我不知道會是什麼樣子，（engineering this is sort of matching where the model was at the time back in the days of sonnet）
- `16:21` 而且在很大程度上，這將取決於團隊去摸索。這就是為什麼我很高興我們以這種方式經營團隊，（3.5 you had to prompt engineer back in the days of opus 4 you had to context engineer but with the）
- `16:27` 每個人都能想出點子，每個人都能思考產品，每個人都一直與使用者交談，因為我不認為這些點子會來自我們，（models of today you don't do any of this you give it the minimal possible system prompt the minimal）
- `16:32` 而是會來自團隊，以及我們社群中每一個與我們一起建構的人。（possible tools and then you let the model figure it out like you just have to give the model some way）
- `16:37` 為了引入 context，我認為這是最重要的事情，你是怎麼想的？我的看法非常相似。（to pull in the context i think that's the most important thing how do you think about it i see things）
- `16:41` 我是一個 context 極簡主義者，所以我的總體哲學是：只告訴模型它需要知道的資訊，（very similarly i'm a context minimalist so my general philosophy is tell the model only what it）
- `16:48` 剩下的讓它自己去推敲。我認為當你給模型太多 context 時，（needs to know and let it figure out the rest of it i think when you give the model too much context）
- `16:55` 就有點像是在微觀管理它，有時模型知道更好的方法來達成（it's kind of like you're micromanaging it and sometimes the model knows a better way to get to）
- `17:01` 相同的結果，我個人傾向於給模型這種自由去發揮。總體而言，（the same outcome and i personally prefer to give the model that freedom to do that and then in general）
- `17:07` 我們也正在讓我們的 harness 更精簡，這樣你就有更多空間來輸入自己的 prompt，也能讓它（we're also making our harness more lean so that you have more room for your own prompts and so that）
- `17:13` 更好地遵循你的 prompt。現在有各種不同的 Claude Code 使用方式，但我感覺在（follows your prompts better there's all these different ways to squad now but i feel like in a）
- `17:18` 一年後，這將會是一套全新的東西，如果到時候還是這些（year it's going to be a totally new set of things and it's going to be so surprising if it's still these）
- `17:23` 同樣的東西會讓人非常驚訝，因為我認為我們現在正看到這些巨大的趨勢正在發生，Agent 們（same things because i i think like we're seeing these giant trends happening right now agents are）
- `17:28` 運行的時間更長，它們更具自主性。我很少一次只運行一個 Agent，通常是（running for longer they're more autonomous very rarely am i running one agent at a time it's usually）
- `17:34` 幾個 Agent，或是幾十個、幾百個甚至幾千個，所以這種形式因素（like a few agents or dozens or hundreds or thousands and so like the form factor for that）
- `17:38` 將會與過去的截然不同，我不知道它會變成什麼樣子，但我（it's going to be really different than what came before and i don't know what it's going to be and i）
- `17:43` 認為在很大程度上，這將取決於團隊去找出答案。這就是為什麼我（think in a large part it's going to be up to the team to figure it out and this is um this is why i'm）
- `17:48` 很高興我們以這種方式管理團隊，每個人都能提出想法，（like so happy we run the team that the way that we do where everyone just comes up with ideas and）
- `17:52` 每個人都能思考產品，每個人都隨時與使用者交流，因為我不認為（everyone is able to think about the product everyone talks to users all the time because i don't think）
- `17:57` 這些想法會來自我們，它們將完全來自團隊，以及我們（these ideas are going to come from us it's going to come from the team totally and from everyone in our）
- `18:02` 社群中與我們一起開發的每一個人。（community building with us）

## 標籤

Claude Code, Agent, 功能更新, 自動化, CLI, Anthropic, Claude