[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"article-phpstorm-20261-laravel-13-agent-tools-zh":3,"tags-phpstorm-20261-laravel-13-agent-tools-zh":35,"related-lang-phpstorm-20261-laravel-13-agent-tools-zh":52,"related-posts-phpstorm-20261-laravel-13-agent-tools-zh":56,"series-tools-ab4aa39b-978a-4d02-9802-e76964ca5c78":93},{"id":4,"title":5,"content":6,"summary":7,"source":8,"source_url":9,"author":10,"image_url":11,"keywords":12,"language":23,"translated_content":10,"views":24,"is_premium":25,"created_at":26,"updated_at":26,"cover_image":11,"published_at":27,"rewrite_status":28,"rewrite_error":10,"rewritten_from_id":29,"slug":30,"category":31,"related_article_id":32,"status":33,"google_indexed_at":34,"x_posted_at":10,"tweet_text":10,"title_rewritten_at":10,"title_original":10,"key_takeaways":10,"topic_cluster_id":10,"embedding":10,"is_canonical_seed":25},"ab4aa39b-978a-4d02-9802-e76964ca5c78","PhpStorm 2026.1 支援 Laravel 13…","\u003Cp>\u003Ca href=\"https:\u002F\u002Fwww.jetbrains.com\u002Fphpstorm\u002F\" target=\"_blank\" rel=\"noopener\">PhpStorm\u003C\u002Fa> \u003Ca href=\"\u002Fnews\u002Fai-funding-records-2026-zh\">2026\u003C\u002Fa>.1 上線了。這版很直接，JetBrains 把 IDE 當成工作中樞在做。它支援 \u003Ca href=\"https:\u002F\u002Flaravel.com\u002Fdocs\u002F13.x\" target=\"_blank\" rel=\"noopener\">Laravel 13\u003C\u002Fa>，也把 MCP 開給第三方 agent。還補了 \u003Ca href=\"https:\u002F\u002Fwww.php.net\u002Freleases\u002F8.5\u002Fen.php\" target=\"_blank\" rel=\"noopener\">PHP 8.5\u003C\u002Fa> pi\u003Ca href=\"\u002Fnews\u002Fopenai-nonprofit-arm-1b-investment-zh\">pe\u003C\u002Fa> operator 的 quick-fix。\u003C\u002Fp>\u003Cp>講白了，這版在解三種痛點。框架版本跟不上。agent 接不上。語言新語法沒工具幫你收尾。這些都不是炫技。這些是每天會卡你 10 分鐘的事。\u003C\u002Fp>\u003Cp>如果你在做 Laravel 專案，這次更新很有感。不是因為某個單一功能很炸。是因為整個編輯器開始更懂你的專案結構。\u003C\u002Fp>\u003Ch2>Laravel 支援變得更像實戰工具\u003C\u002Fh2>\u003Cp>JetBrains 這次把 Laravel 13、Livewire、Filament、Laravel Wayfinder，還有 \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fstaudenmeir\" target=\"_blank\" rel=\"noopener\">staudenmeir\u003C\u002Fa> 系列套件都納進支援範圍。這很實際。現在的 Laravel 專案很少只靠核心框架。常常還混了元件庫、路由輔助、生成式程式碼。\u003C\u002Fp>\n\u003Cfigure class=\"my-6\">\u003Cimg src=\"https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1775139172869-b3f7.png\" alt=\"PhpStorm 2026.1 支援 Laravel 13…\" class=\"rounded-xl w-full\" loading=\"lazy\" \u002F>\u003C\u002Ffigure>\n\u003Cp>IDE 如果只懂一半，開發體驗就會很碎。你改一個 method，跳提示不準。你搜一個 route，結果漏掉 package 產生的東西。這種小錯誤累積起來，很煩。\u003C\u002Fp>\u003Cp>PhpStorm 2026.1 也改進了 Eloquent method 的處理。Find Usages 更準。還多了 Route Search UI。對大型 Laravel 專案來說，這種功能比華麗動畫有用多了。真的，找路由名稱有時候比寫功能還花時間。\u003C\u002Fp>\u003Cp>PHP 8.5 也開始有感。這版能辨識 pipe operator 的適用位置，還能直接做 quick-fix。這代表團隊不用等到某個人有空重構。IDE 先幫你把可改的地方列出來。\u003C\u002Fp>\u003Cul>\u003Cli>支援 Laravel 13、Livewire、Filament\u003C\u002Fli>\u003Cli>Route Search UI 可快速找路由\u003C\u002Fli>\u003Cli>Eloquent method 與 Find Usages 更準\u003C\u002Fli>\u003Cli>PHP 8.5 pipe operator 可自動修正\u003C\u002Fli>\u003Cli>泛型 callable 的推斷也更好\u003C\u002Fli>\u003C\u002Ful>\u003Ch2>MCP 讓 agent 不再瞎猜\u003C\u002Fh2>\u003Cp>這版另一個重點是 \u003Ca href=\"https:\u002F\u002Fmodelcontextprotocol.io\u002F\" target=\"_blank\" rel=\"noopener\">MCP\u003C\u002Fa>。PhpStorm 內建 MCP server 現在可以把 inspections、quick-fixes、IDE search 和 IDE actions 開給第三方 agent 用。像 \u003Ca href=\"https:\u002F\u002Fwww.anthropic.com\u002Fclaude-code\" target=\"_blank\" rel=\"noopener\">Claude Code\u003C\u002Fa>、\u003Ca href=\"https:\u002F\u002Fcode.windsurf.com\u002F\" target=\"_blank\" rel=\"noopener\">Windsurf\u003C\u002Fa> 這類工具，就能先問 IDE 看到了什麼，再決定怎麼改。\u003C\u002Fp>\u003Cp>這差很多。沒有 MCP 時，agent 常常像盲人摸象。它只看檔案，不知道 IDE 已經抓到哪些錯誤。它也不知道某個 quick-fix 能不能直接套用。結果就是改得慢，還容易改歪。\u003C\u002Fp>\u003Cp>JetBrains 也加了 \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Flaravel\u002Fidea\" target=\"_blank\" rel=\"noopener\">Laravel Idea\u003C\u002Fa> 的 MCP 整合。這點我覺得很對。通用 agent 很方便，但框架專用工具更準。懂 Laravel 慣例的 agent，才比較不會亂動你的專案架構。\u003C\u002Fp>\u003Cblockquote>“The future of coding is not about replacing developers, but about amplifying their capabilities.” — Martin Fowler\u003C\u002Fblockquote>\u003Cp>這句 Martin Fowler 的話，放在這版很貼。PhpStorm 沒有把 agent 包裝成萬能開發者。它只是把工具給得更完整。最後拍板的人，還是人。\u003C\u002Fp>\u003Cp>JetBrains 也推出 \u003Ca href=\"https:\u002F\u002Fwww.jetbrains.com\u002Fjunie\u002F\" target=\"_blank\" rel=\"noopener\">Junie CLI\u003C\u002Fa> beta。它是 LLM-agnostic 的 coding agent，還支援 bring-yo\u003Ca href=\"\u002Fnews\u002Fcursor-kimi-open-source-bet-zh\">ur\u003C\u002Fa>-own-key。這代表團隊可以自己挑模型，也能自己控成本。這點對公司來說很重要，因為 API 帳單不會自己變溫柔。\u003C\u002Fp>\u003Ch2>AI、測試與索引，都是在減少摩擦\u003C\u002Fh2>\u003Cp>這版還有一個很務實的功能，叫 Next Edit Suggestions。JetBrains 說，這些 AI 建議可以跨檔案出現，而且不消耗 AI quota。意思很明白。它不是叫你一直跟聊天視窗互動，而是直接提醒你下一步該改哪裡。\u003C\u002Fp>\n\u003Cfigure class=\"my-6\">\u003Cimg src=\"https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1775139173644-fmhd.png\" alt=\"PhpStorm 2026.1 支援 Laravel 13…\" class=\"rounded-xl w-full\" loading=\"lazy\" \u002F>\u003C\u002Ffigure>\n\u003Cp>這種設計其實比較像老派 IDE 思維。少講話，多做事。對開發者來說，最有價值的 AI 功能，通常不是會聊天的那種。是能幫你少漏一個 import、少漏一個 reference、少漏一段同步修改的那種。\u003C\u002Fp>\u003Cp>測試與除錯也有補強。非 PHP 的 .ezt 檔現在能設 breakpoint，還支援 native path mapping。Go to Test 對 PHPUnit 的 \u003Ccode>#[UsesClass]\u003C\u002Fcode> 和 Pest 也更友善。這些聽起來很細，但測試流程一卡，整個心情都會差。\u003C\u002Fp>\u003Cp>索引也變聰明了。PhpStorm 會自動排除框架裡的 generated、cached、user-uploaded 目錄。大型 Laravel 專案常有這種雜訊資料夾。少掃這些檔案，IDE 就比較不會一直喘。\u003C\u002Fp>\u003Cul>\u003Cli>Next Edit Suggestions 不吃 AI quota\u003C\u002Fli>\u003Cli>Junie CLI beta 支援 BYOK\u003C\u002Fli>\u003Cli>.ezt breakpoint 支援 native path mapping\u003C\u002Fli>\u003Cli>Go to Test 對 PHPUnit 與 Pest 更好用\u003C\u002Fli>\u003Cli>自動排除 generated 與 cached 目錄\u003C\u002Fli>\u003C\u002Ful>\u003Ch2>git worktrees 與前端支援也補齊了\u003C\u002Fh2>\u003Cp>PhpStorm 2026.1 也把 git worktrees 做成一等公民。這對同時跑多條分支的人很有用。你不用一直 stash。也不用開一堆 clone。分支切換會乾淨很多。\u003C\u002Fp>\u003Cp>這種功能很適合做 feature branch 並行開發。比如一條分支修 bug，一條分支做新 API，一條分支處理 migration。worktrees 讓這些工作能並排放著，不用互相打架。\u003C\u002Fp>\u003Cp>終端機補全也補了 Git、Docker、kubectl 和自訂腳本。Linux 上還加了 Wayland 原生支援，X11 也能 fallback。這些都不是新聞稿最愛講的東西，但它們決定你用一天會不會煩。\u003C\u002Fp>\u003Cp>前端支援也沒落下。TypeScript 預設改用 service-powered type engine。React 支援 \u003Ccode>use memo\u003C\u002Fcode> 和 \u003Ccode>use no memo\u003C\u002Fcode> 標示。還有 Vue 3.1.8、Angular 21.x template、CSS \u003Ccode>color()\u003C\u002Fcode> function。對現在很多 Laravel 團隊來說，後端早就不是唯一戰場。\u003C\u002Fp>\u003Cp>另外，\u003Ca href=\"https:\u002F\u002Fwww.jetbrains.com\u002Fhelp\u002Fphpstorm\u002Fcode-with-me.html\" target=\"_blank\" rel=\"noopener\">Code With Me\u003C\u002Fa> 會在這版後退場，之後改成獨立 marketplace plugin。這很像 JetBrains 在整理產品線。舊協作路線收掉，agent-aware 工作流往前推。\u003C\u002Fp>\u003Ch2>這版放在 PHP 生態裡看更有意思\u003C\u002Fh2>\u003Cp>如果只看單一功能，PhpStorm 2026.1 好像只是更新清單很多。可放回 PHP 生態來看，這版其實很準。Laravel 團隊現在常同時碰框架、套件、agent、測試、前端、CI。IDE 如果還只做語法高亮，真的不夠。\u003C\u002Fp>\u003Cp>JetBrains 的策略也很清楚。它不是跟通用 AI 編輯器硬拼聊天能力。它是把 IDE 本來就懂的東西，變成 agent 能用的工具。這條路比較務實，也比較符合企業採購習慣。公司通常不想把核心流程交給黑盒子。\u003C\u002Fp>\u003Cp>對台灣開發團隊來說，這版最值得關注的點有三個。第一，Laravel 13 與周邊套件支援。第二，MCP 讓 agent 接上 IDE。第三，git worktrees 讓多分支開發更順。這三件事剛好對上現在很多團隊的日常。\u003C\u002Fp>\u003Cp>我覺得如果你們團隊已經在用 agent，或已經開始跑 worktrees，這版值得先在一個專案試。先看路由搜尋、Eloquent 提示、測試導向、MCP 流程會不會真的省時間。省下來的不是炫耀用的分數，是每天少掉的雜事。\u003C\u002Fp>\u003Ch2>結尾：先在一個專案試跑\u003C\u002Fh2>\u003Cp>我的建議很簡單。先挑一個 Laravel 專案升到 2026.1。看 Route Search、MCP、worktrees、PHP 8.5 quick-fix 四個點有沒有吃到你們的痛。這版不是要你重新學 IDE。它是要你少做幾次重複動作。\u003C\u002Fp>\u003Cp>如果你的團隊已經在碰 agent，我會更早升。因為這版的重點不是 UI。是 IDE 開始把自己當成 agent 的協作層。這件事，現在就可以開始測。\u003C\u002Fp>","PhpStorm 2026.1 加入 Laravel 13、MCP 給第三方 agent、PHP 8.5 pipe 修正與 git worktrees。對 Laravel 團隊來說，這版更像工作中樞。","laravel-news.com","https:\u002F\u002Flaravel-news.com\u002Fphpstorm-20261-released",null,"https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1775139172869-b3f7.png",[13,14,15,16,17,18,19,20,21,22],"PhpStorm","Laravel 13","MCP","PHP 8.5","git worktrees","JetBrains","Claude Code","Windsurf","Livewire","Filament","zh",2,false,"2026-04-02T14:12:36.67946+00:00","2026-04-02T14:12:36.581+00:00","done","7c67abf5-69b8-4ea4-8908-6137d4360f62","phpstorm-20261-laravel-13-agent-tools-zh","tools","64b03478-254b-4895-bb31-18ca39df1440","published","2026-04-08T09:00:51.821+00:00",[36,38,40,42,44,46,48,50],{"name":20,"slug":37},"windsurf",{"name":13,"slug":39},"phpstorm",{"name":22,"slug":41},"filament",{"name":21,"slug":43},"livewire",{"name":18,"slug":45},"jetbrains",{"name":15,"slug":47},"mcp",{"name":19,"slug":49},"claude-code",{"name":17,"slug":51},"git-worktrees",{"id":32,"slug":53,"title":54,"language":55},"phpstorm-20261-laravel-13-agent-tools-en","PhpStorm 2026.1 Adds Laravel 13 and Agent Tools","en",[57,63,69,75,81,87],{"id":58,"slug":59,"title":60,"cover_image":61,"image_url":61,"created_at":62,"category":31},"d058a76f-6548-4135-8970-f3a97f255446","why-gemini-api-pricing-is-cheaper-than-it-looks-zh","為什麼 Gemini API 定價其實比看起來更便宜","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1778869845081-j4m7.png","2026-05-15T18:30:25.797639+00:00",{"id":64,"slug":65,"title":66,"cover_image":67,"image_url":67,"created_at":68,"category":31},"68e4be16-dc38-4524-a6ea-5ebe22a6c4fb","why-vidhub-huiyuan-hutong-bushi-quan-shebei-tongyong-zh","為什麼 VidHub 會員互通不是「買一次全設備通用」","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1778789450987-advz.png","2026-05-14T20:10:24.048988+00:00",{"id":70,"slug":71,"title":72,"cover_image":73,"image_url":73,"created_at":74,"category":31},"7a1e174f-746b-4e82-a0e3-b2475ab39747","why-buns-zig-to-rust-experiment-is-right-zh","為什麼 Bun 的 Zig-to-Rust 實驗是對的","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1778767879127-5dna.png","2026-05-14T14:10:26.886397+00:00",{"id":76,"slug":77,"title":78,"cover_image":79,"image_url":79,"created_at":80,"category":31},"e742fc73-5a65-4db3-ad17-88c99262ceb7","why-openai-api-pricing-is-product-strategy-zh","為什麼 OpenAI API 定價是產品策略，不是註腳","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1778749859485-chvz.png","2026-05-14T09:10:26.003818+00:00",{"id":82,"slug":83,"title":84,"cover_image":85,"image_url":85,"created_at":86,"category":31},"c757c5d8-eda9-45dc-9020-4b002f4d6237","why-claude-code-prompt-design-beats-ide-copilots-zh","為什麼 Claude Code 的提示設計贏過 IDE Copilot","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1778742645084-dao9.png","2026-05-14T07:10:29.371901+00:00",{"id":88,"slug":89,"title":90,"cover_image":91,"image_url":91,"created_at":92,"category":31},"4adef3ab-9f07-4970-91cf-77b8b581b348","why-databricks-model-serving-is-right-default-zh","為什麼 Databricks Model Serving 是生產推論的正確預設","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1778692245329-a2wt.png","2026-05-13T17:10:30.659153+00:00",[94,99,104,109,114,119,124,129,134,139],{"id":95,"slug":96,"title":97,"created_at":98},"de769291-4574-4c46-a76d-772bd99e6ec9","googles-biggest-gemini-launches-in-2026-zh","Google 2026 最大 Gemini 盤點","2026-03-26T07:26:39.21072+00:00",{"id":100,"slug":101,"title":102,"created_at":103},"855cd52f-6fab-46cc-a7c1-42195e8a0de4","surepath-real-time-mcp-policy-controls-zh","SurePath 推出即時 MCP 政策控管","2026-03-26T07:57:40.77233+00:00",{"id":105,"slug":106,"title":107,"created_at":108},"9b19ab54-edef-4dbd-9ce4-a51e4bae4ebb","mcp-in-2026-the-ai-tool-layer-teams-use-zh","2026 年 MCP：團隊真的在用的 AI 工具層","2026-03-26T08:01:46.589694+00:00",{"id":110,"slug":111,"title":112,"created_at":113},"af9c46c3-7a28-410b-9f04-32b3de30a68c","prompting-in-2026-what-actually-works-zh","2026 提示工程，真正有用的是什麼","2026-03-26T08:08:12.453028+00:00",{"id":115,"slug":116,"title":117,"created_at":118},"05553086-6ed0-4758-81fd-6cab24b575e0","garry-tan-open-sources-claude-code-toolkit-zh","Garry Tan 開源 Claude Code 工具包","2026-03-26T08:26:20.068737+00:00",{"id":120,"slug":121,"title":122,"created_at":123},"042a73a2-18a2-433d-9e8f-9802b9559aac","github-ai-projects-to-watch-in-2026-zh","2026 必看 20 個 GitHub AI 專案","2026-03-26T08:28:09.619964+00:00",{"id":125,"slug":126,"title":127,"created_at":128},"a5f94120-ac0d-4483-9a8b-63590071ac6a","claude-code-vs-cursor-2026-zh","Claude Code 與 Cursor 深度對比：202…","2026-03-26T13:27:14.279193+00:00",{"id":130,"slug":131,"title":132,"created_at":133},"0975afa1-e0c7-4130-a20d-d890eaed995e","practical-github-guide-learning-ml-2026-zh","2026 機器學習入門 GitHub 實用指南","2026-03-27T01:16:49.712576+00:00",{"id":135,"slug":136,"title":137,"created_at":138},"bfdb467a-290f-4a80-b3a9-6f081afb6dff","aiml-2026-student-ai-ml-lab-repo-review-zh","AIML-2026：像課綱的學生實驗 Repo","2026-03-27T01:21:51.467798+00:00",{"id":140,"slug":141,"title":142,"created_at":143},"80cabc3e-09fc-4ff5-8f07-b8d68f5ae545","ai-trending-github-repos-and-research-feeds-zh","AI Trending：把 AI 資源收成一張表","2026-03-27T01:31:35.262183+00:00"]