[{"data":1,"prerenderedAt":683},["ShallowReactive",2],{"search-dialog-posts":3,"post-\u002Fposts\u002Fcodex-model-selection":316,"post-surround-\u002Fposts\u002Fcodex-model-selection":676},[4,12,21,29,37,47,57,67,77,85,96,104,112,121,129,137,147,155,164,173,181,188,195,207,215,224,236,241,247,254,260,266,272,279,286,291,298,304,310],{"path":5,"title":6,"description":7,"category":8,"tags":9},"\u002Fposts\u002Fgit-commands-cheatsheet","Git 常用指令與終端機筆記","2018 年整理的 Git 學習筆記，包含基本終端機指令、Git 操作、分支、reset、SourceTree、Vim 與一些常用設定。","notes",[10,11],"Git","版本控制",{"path":13,"title":14,"description":15,"category":16,"tags":17},"\u002Fposts\u002Fjs-prototype-inheritance","JavaScript 物件導向：建構函式、prototype 與繼承三步驟","整理 ES5 時代用建構函式加 prototype 手刻物件導向的完整流程——封裝屬性與方法、共用函式為什麼要掛在 prototype 上、以及繼承的三個步驟（call 借用母類別建構子、Object.create 接上原型鏈、修正 constructor 指向），並附上物件縮寫與計算屬性這兩個順便學到的 ES6 寫法。","frontend",[18,19,20],"JavaScript","物件導向","prototype",{"path":22,"title":23,"description":24,"category":16,"tags":25},"\u002Fposts\u002Fflexbox-notes","Flexbox 對齊與彈性尺寸筆記","記錄 Flexbox 的主軸與交錯軸對齊、flex-direction、flex-wrap，以及 flex-grow、flex-shrink、flex-basis 等常用屬性。",[26,27,28],"CSS","Flexbox","版面",{"path":30,"title":31,"description":32,"category":16,"tags":33},"\u002Fposts\u002Fscreen-orientation-api","screen.orientation：現在判斷與鎖定螢幕方向的做法","整理現在 JavaScript 判斷螢幕方向的方式，包括 screen.orientation、change 事件與 lock()，並說明 RWD 使用 matchMedia 或 CSS orientation 會更適合。",[18,34,35,36],"RWD","螢幕方向","PWA",{"path":38,"title":39,"description":40,"category":16,"tags":41},"\u002Fposts\u002Fpinia-vuex-state-management","Pinia \u002F Vuex 狀態管理及差異","紀錄 Vuex、Pinia 的狀態管理概念、差異與用法。",[42,43,44,45,46],"Pinia","Vuex","Vue3","狀態管理","Nuxt",{"path":48,"title":49,"description":50,"category":8,"tags":51},"\u002Fposts\u002Fpyenv-python-version-management","Python 多版本管理 pyenv","紀錄 macOS 與 Windows 使用 pyenv 管理 Python 版本的方式。",[52,53,54,55,56],"Python","pyenv","macOS","Windows","版本管理",{"path":58,"title":59,"description":60,"category":8,"tags":61},"\u002Fposts\u002Fnpm-publish-vue2-component","npm 發布流程","紀錄 Vue 2 元件的 npm 發布、dist-tag 與打包流程。",[62,63,64,65,66],"npm","Vue2","Vue CLI","套件發布","MIT",{"path":68,"title":69,"description":70,"category":8,"tags":71},"\u002Fposts\u002Fmobile-debugging-today","現在怎麼 debug 手機網頁：從裝一堆工具到幾乎不用裝","對照 2022 年那套 scoop、iTunes、remotedebug-ios-webkit-adapter 的繁瑣設定，整理現在偵錯手機網頁的做法：Android 無線偵錯、iOS 的實際選項、on-device console、Playwright 裝置模擬，以及本機 HTTPS 的處理。",[72,73,74,75,76],"debug","iOS","Android","Chrome DevTools","Playwright",{"path":78,"title":79,"description":80,"category":16,"tags":81},"\u002Fposts\u002Fplaywright-vs-cypress","E2E 測試現在選什麼：Playwright 與 Cypress 的實際差異","對照幾年前用 Cypress 的做法，說明 Playwright 為什麼變成多數新專案的預設選擇：真正的多瀏覽器支援、免費的平行執行、trace viewer 除錯，以及兩者在架構上的根本差異與各自仍然適合的場景。",[76,82,83,84],"Cypress","E2E","測試",{"path":86,"title":87,"description":88,"category":89,"tags":90},"\u002Fposts\u002Fjs-encoding-today","現在處理編碼：TextEncoder、Uint8Array 的 Base64 方法與 URLSearchParams","整理 JavaScript 現代編碼方式，使用 TextEncoder、TextDecoder 與 Uint8Array 處理 UTF-8 與 Base64，並說明 Base64URL、URLSearchParams 與 encodeURIComponent 的差異。","research",[91,92,93,94,95,18],"編碼","TextEncoder","Base64","URLSearchParams","Uint8Array",{"path":97,"title":98,"description":99,"category":16,"tags":100},"\u002Fposts\u002Fdart-sass-migration","Dart Sass 遷移筆記：node-sass 之後怎麼裝 Sass","node-sass 與 LibSass 已停止維護，現在改用 Dart Sass。整理 webpack 與 Vite 的安裝方式，以及為什麼不再像 node-sass 一樣容易遇到 Node.js 版本與原生編譯問題。",[101,102,103],"Sass","Webpack","Vite",{"path":105,"title":106,"description":107,"category":16,"tags":108},"\u002Fposts\u002Fdayjs-vue3-computed","day.js 搭配 Vue 3 的日期格式化","整理 Vue 3 日期格式化的常見做法，使用 day.js 取代舊專案常見的 moment.js，並以 method 或 computed 取代 Vue 2 filter，也補充原生 Intl.DateTimeFormat 的使用方式。",[44,109,110,111],"day.js","日期","Intl",{"path":113,"title":114,"description":115,"category":16,"tags":116},"\u002Fposts\u002Fes-modules-today","ES Module 現在的樣子：Node ESM、exports 與 import maps","整理現代 JavaScript ES Module 的常見用法，包括 Node.js 原生 ESM、package.json exports、瀏覽器 import maps、JSON import attributes，以及 Vite 動態載入的注意事項。",[117,118,119,120,103,18],"ES Module","Node.js","import maps","exports",{"path":122,"title":123,"description":124,"category":89,"tags":125},"\u002Fposts\u002Fstructured-clone","structuredClone()：終於有內建的深層拷貝","整理 JavaScript structuredClone() 的深層拷貝用法，說明 Date、Map、Set、循環參考的處理方式，以及 Function、class 與 Vue reactive Proxy 的注意事項。",[18,126,127,128],"structuredClone","深拷貝","Vue",{"path":130,"title":131,"description":132,"category":16,"tags":133},"\u002Fposts\u002Fdynamic-import","JavaScript 動態載入：import() 與 Vue 非同步元件","整理靜態 import、動態 import() 與 Vue defineAsyncComponent 的使用方式，並簡單補充 Vite import.meta.glob 的用途。",[18,134,135,103,136],"ES Modules","Vue 3","Code Splitting",{"path":138,"title":139,"description":140,"category":16,"tags":141},"\u002Fposts\u002Fscreen-wake-lock-api","Screen Wake Lock API：不用套件也能讓頁面保持亮著","整理 Screen Wake Lock API 的基本用法，說明 HTTPS、頁面可見性、切換分頁後重新取得 wake lock，以及 Vue／Nuxt 計時器使用時的注意事項。",[142,128,143,144,145,146],"Wake Lock","Nuxt4","行動裝置","計時器","Web API",{"path":148,"title":149,"description":150,"category":16,"tags":151},"\u002Fposts\u002Fhtml-meta-boilerplate-today","現在的 HTML meta 標籤怎麼寫","整理現在一個新頁面該有的 meta 標籤骨架——viewport 補上 viewport-fit=cover 因應瀏海與圓角螢幕、color-scheme 讓表單控制項跟著深色模式換色、theme-color 決定行動瀏覽器工具列顏色，以及基本的 SEO 與 Open Graph 標籤。",[152,153,154],"HTML","meta","SEO",{"path":156,"title":157,"description":158,"category":8,"tags":159},"\u002Fposts\u002Fdocker-node-postgres","把 Node + PostgreSQL 的 backend 裝進 Docker：Dockerfile、.dockerignore 與 compose","從「本機裝了就跑」到打包成容器的通用做法——Dockerfile 每一行的理由與 layer cache 為什麼決定了指令順序、.dockerignore 漏掉 node_modules 對原生模組是災難級的問題、容器之間為什麼不能用 localhost 互相找到對方，以及怎麼驗證資料真的寫進了 volume。",[160,161,118,162,163],"Docker","Docker Compose","PostgreSQL","Express",{"path":165,"title":166,"description":167,"category":16,"tags":168},"\u002Fposts\u002Fnuxt-server-proxy","Nuxt 3 \u002F 4 用 Server API 做代理與轉發","整理 Nuxt 3 與 Nuxt 4 使用 server\u002Fapi 轉發第三方 API 的方式，可以避免瀏覽器 CORS 問題、隱藏 API Key，也能在伺服器端加入快取。",[169,143,170,171,172],"Nuxt3","CORS","Nitro","API",{"path":174,"title":175,"description":176,"category":16,"tags":177},"\u002Fposts\u002Fnuxt4-project-setup","Nuxt 4 建立專案：和 Nuxt 3 有哪些不同","整理 Nuxt 4 建立專案的基本流程與目錄結構，並對照 Nuxt 3 的差異，包括 app\u002F 目錄、路徑別名、TypeScript，以及目前常用的 ESLint 與 Tailwind CSS 4 設定。",[143,44,178,179,180],"TypeScript","ESLint","Tailwind CSS 4",{"path":182,"title":183,"description":184,"category":16,"tags":185},"\u002Fposts\u002Fnuxt3-route-middleware","Nuxt 3 \u002F 4 的 Route Middleware：進頁面前先做判斷","整理 Nuxt 3 與 Nuxt 4 的 Route Middleware，用 defineNuxtRouteMiddleware 在進入頁面前檢查登入狀態，搭配 navigateTo 重新導向，並說明一般 middleware、global middleware 與 definePageMeta 的用法。",[169,143,186,187],"Middleware","驗證",{"path":189,"title":190,"description":191,"category":16,"tags":192},"\u002Fposts\u002Fnuxt-route-rules-redirect","Nuxt 3 \u002F 4 的 routeRules：重新導向與頁面設定","整理 Nuxt 3 與 Nuxt 4 的 routeRules 用法，可以依照不同網址設定重新導向、預渲染、SSR 與快取，並簡單對照 Nuxt 2 的舊做法。",[169,143,193,194],"routeRules","重新導向",{"path":196,"title":197,"description":198,"category":16,"tags":199},"\u002Fposts\u002Fios-iframe-google-login-blank-page","iOS iframe 串接 Google 登入出現空白頁：Popup 與頁面回收問題排查紀錄","記錄 iframe 內串接 Google 第三方登入時，部分 iOS 裝置因背景頁面遭到回收並重新載入，導致 Popup 登入流程中斷，以及最後透過 Redirect 分流與登入狀態接回機制處理的過程。",[73,200,201,202,203,204,205,206],"Safari","iframe","Google Login","GIS","OAuth","Popup","Redirect",{"path":208,"title":209,"description":210,"category":16,"tags":211},"\u002Fposts\u002Fios-login-tab-return-behavior","iOS 第三方登入後回不到原頁？分頁開啟關係與回頁行為實測","記錄 iOS Safari 與 Chrome 在多分頁第三方登入流程中，登入頁關閉後不一定回到原頁的實測，以及分頁開啟關係、window.close 與 window.focus 的限制。",[73,200,212,202,204,201,213,214],"Chrome","window.close","window.focus",{"path":216,"title":217,"description":218,"category":16,"tags":219},"\u002Fposts\u002Fgoogle-app-about-blank-placeholder","Google App 內建瀏覽器：about:blank 佔位頁被關閉的排查紀錄","記錄 iOS Google App 內建瀏覽器在非同步開啟外部頁面時，about:blank 佔位分頁被自動關閉，導致第三方登入或外部導轉失敗的排查與解法。",[73,220,221,222,204,223],"Google App","window.open","about:blank","WebView",{"path":225,"title":226,"description":227,"category":228,"tags":229},"\u002Fposts\u002Fclaude-code-codex-cli-init-basics","AI 相關紀錄 v1｜Claude Code \u002F Codex CLI 初始化與基本概念","從 Claude Code 與 Codex CLI 開始，整理 CLI、Coding Agent、Context、\u002Finit 與 CLAUDE.md／AGENTS.md 這幾個一開始最容易搞混的概念，以及在既有專案中的安裝與啟動方式。","ai",[230,231,232,233,234,235],"AI","Claude Code","Codex CLI","Coding Agent","CLAUDE.md","AGENTS.md",{"path":237,"title":238,"description":239,"category":228,"tags":240},"\u002Fposts\u002Fclaude-agents-md-project-guidelines","AI 相關紀錄 v2｜CLAUDE.md \u002F AGENTS.md 怎麼寫？專案規範與實際範例","整理 CLAUDE.md 與 AGENTS.md 的用途、適合記錄的專案規範，以及可直接參考的設定範例。",[230,231,232,234,235],{"path":242,"title":243,"description":244,"category":228,"tags":245},"\u002Fposts\u002Fclaude-codex-config-locations","AI 相關紀錄 v3｜Claude Code `.claude\u002F` \u002F Codex CLI 設定位置：全域與專案設定基本概要介紹","整理 Claude Code 與 Codex CLI 的使用者層級、專案層級設定位置，以及 rules、skills、agents 等目錄的用途。",[230,231,232,246],"設定檔",{"path":248,"title":249,"description":250,"category":228,"tags":251},"\u002Fposts\u002Fclaude-settings-codex-config","AI 相關紀錄 v4｜Claude Code settings \u002F Codex config 基本設定","整理 Claude Code settings.json 與 Codex config.toml 的設定層級、權限控制和常見基本設定。",[230,231,232,252,253],"settings.json","config.toml",{"path":255,"title":256,"description":257,"category":228,"tags":258},"\u002Fposts\u002Fclaude-codex-rules-structure","AI 相關紀錄 v5｜Rules：專案規則多了之後怎麼拆？","整理 Claude Code Rules 與 Codex AGENTS.md 的拆分方式，說明何時該拆、怎麼依目錄管理專案規則。",[230,231,232,259,235],"Rules",{"path":261,"title":262,"description":263,"category":228,"tags":264},"\u002Fposts\u002Fclaude-codex-slash-commands","AI 相關紀錄 v6｜Commands \u002F Slash Commands：CLI 裡的 `\u002F` 指令是什麼？","介紹 Claude Code 與 Codex CLI 的 Slash Commands，整理常用內建指令、自訂指令與 Skills 的差異。",[230,231,232,265],"Slash Commands",{"path":267,"title":268,"description":269,"category":228,"tags":270},"\u002Fposts\u002Fclaude-codex-skills","AI 相關紀錄 v7｜Skills：把重複工作流程整理起來","介紹 Claude Code 與 Codex Skills，整理適合保存成 Skill 的重複流程、基本結構與使用方式。",[230,231,232,271],"Skills",{"path":273,"title":274,"description":275,"category":228,"tags":276},"\u002Fposts\u002Fclaude-codex-agents-subagents","AI 相關紀錄 v8｜Agent \u002F Subagent：什麼時候真的需要分工？","整理 Agent、Subagent 與 Custom Agent 的用途，說明何時適合分工，以及它們和 Rules、Skills 的差異。",[230,231,232,277,278],"Agent","Subagent",{"path":280,"title":281,"description":282,"category":228,"tags":283},"\u002Fposts\u002Fmcp-basics","AI 相關紀錄 v9｜MCP：讓 AI 使用其他工具與資料","介紹 MCP 如何讓 AI 使用外部工具與資料，並以 Pencil MCP 說明實際用途、權限風險及與 Skill 的差異。",[230,284,231,232,285],"MCP","Pencil",{"path":287,"title":288,"description":289,"category":228,"tags":290},"\u002Fposts\u002Fai-coding-agent-concepts-summary","AI 相關紀錄 v10｜基本概念小結論","用一篇快速整理 CLAUDE.md、AGENTS.md、設定檔、Rules、Commands、Skills、Agent 與 MCP 的角色和差異。",[230,231,232,284,271,277],{"path":292,"title":293,"description":294,"category":228,"tags":295},"\u002Fposts\u002Fclaude-code-codex-model-selection","Claude Code 與 Codex：不同模型怎麼選？","比較 Claude Code 與 Codex 不同模型的速度、能力與成本取捨，依工作難度整理實用的選擇方向。",[230,231,296,297],"Codex","模型選擇",{"path":299,"title":300,"description":301,"category":228,"tags":302},"\u002Fposts\u002Fclaude-model-selection","Claude 模型簡單怎麼選？","整理 Claude 各模型在速度、能力與使用情境上的差異，提供從輕量工作到複雜任務的選擇方向。",[230,231,303,297],"Claude",{"path":305,"title":306,"description":307,"category":228,"tags":308},"\u002Fposts\u002Fcodex-model-selection","Codex 模型簡單怎麼選？","整理 Codex 各模型在速度、能力與使用情境上的差異，提供從簡單修改到大型端到端任務的選擇方向。",[230,296,309,297],"OpenAI",{"path":311,"title":312,"description":313,"category":228,"tags":314},"\u002Fposts\u002Fclaude-code-codex-cli-command-cheatsheet","Claude Code \u002F Codex CLI 常用指令速查表","整理 Claude Code 與 Codex CLI 的常用斜線指令、快捷操作與進階功能，方便需要時快速查找。",[230,231,232,265,315],"速查表",{"id":317,"title":306,"body":318,"category":228,"description":307,"draft":665,"extension":666,"image":667,"meta":668,"navigation":669,"path":305,"publishedAt":670,"relatedExperiments":671,"seo":672,"stem":673,"tags":674,"updatedAt":667,"__hash__":675},"posts\u002Fposts\u002F20260913.codex-model-selection.md",{"type":319,"value":320,"toc":655},"minimark",[321,325,328,339,342,345,412,415,418,422,425,431,434,437,443,446,449,451,454,457,466,468,474,477,480,486,489,491,494,497,503,506,509,514,517,519,522,525,531,534,537,544,546,552,555,558,560,564,567,573,576,582,585,588,591,597,600,603,611,614,616,619,622,628,631,634,637,643,646,652],[322,323,324],"p",{},"Codex 可以使用不同模型處理程式開發工作。",[322,326,327],{},"實際可以選到哪些模型，會依：",[329,330,336],"pre",{"className":331,"code":333,"language":334,"meta":335},[332],"language-text","Codex 版本\n帳號方案\nOpenAI 當下提供的模型\n","text","",[337,338,333],"code",{"__ignoreMap":335},[322,340,341],{},"而有所不同。",[322,343,344],{},"如果只是想先快速理解，目前可以大致分成：",[346,347,348,364],"table",{},[349,350,351],"thead",{},[352,353,354,358,361],"tr",{},[355,356,357],"th",{},"模型",[355,359,360],{},"可以先理解成",[355,362,363],{},"適合情境",[365,366,367,379,390,401],"tbody",{},[352,368,369,373,376],{},[370,371,372],"td",{},"GPT-5.6 Luna",[370,374,375],{},"快速、輕量",[370,377,378],{},"搜尋、小修改、簡單整理",[352,380,381,384,387],{},[370,382,383],{},"GPT-5.6 Terra",[370,385,386],{},"日常平衡",[370,388,389],{},"一般功能開發、日常 Coding",[352,391,392,395,398],{},[370,393,394],{},"GPT-5.6 Sol",[370,396,397],{},"高能力模型",[370,399,400],{},"複雜 Debug、架構分析、大型修改",[352,402,403,406,409],{},[370,404,405],{},"GPT-6 Astra",[370,407,408],{},"最高階選擇",[370,410,411],{},"大型 Codebase、複雜端到端任務",[322,413,414],{},"OpenAI 目前將 Terra 定位為能力與成本之間的平衡選擇，Luna 則是 GPT-5.6 系列中速度最快、成本最低的模型；Sol 是處理複雜專業工作的旗艦模型。GPT-6 Astra 則定位在最困難的端到端工作。",[416,417],"hr",{},[419,420,372],"h2",{"id":421},"gpt-56-luna",[322,423,424],{},"Luna 可以先理解成：",[329,426,429],{"className":427,"code":428,"language":334,"meta":335},[332],"快速\n+\n輕量\n",[337,430,428],{"__ignoreMap":335},[322,432,433],{},"比較適合範圍明確的小工作。",[322,435,436],{},"例如：",[329,438,441],{"className":439,"code":440,"language":334,"meta":335},[332],"幫我找出某個 function 在哪裡使用\n\n修改一小段 CSS\n\n整理 README\n\n修改幾個簡單命名\n",[337,442,440],{"__ignoreMap":335},[322,444,445],{},"這類任務通常不一定需要直接使用高階模型。",[322,447,448],{},"OpenAI 將 Luna 定位為適合高頻率、成本敏感工作，而且是 GPT-5.6 系列中速度最快的模型。",[416,450],{},[419,452,383],{"id":453},"gpt-56-terra",[322,455,456],{},"Terra 比較像：",[458,459,460],"blockquote",{},[322,461,462],{},[463,464,465],"strong",{},"日常開發時，能力與使用成本之間的平衡選擇。",[322,467,436],{},[329,469,472],{"className":470,"code":471,"language":334,"meta":335},[332],"實作一般功能\n\n修改 Component\n\n建立 API\n\n一般 Debug\n\n補測試\n",[337,473,471],{"__ignoreMap":335},[322,475,476],{},"都可以先考慮 Terra。",[322,478,479],{},"OpenAI 對 Terra 的官方定位就是：",[329,481,484],{"className":482,"code":483,"language":334,"meta":335},[332],"balance intelligence and cost\n",[337,485,483],{"__ignoreMap":335},[322,487,488],{},"也就是能力與成本之間取得平衡。",[416,490],{},[419,492,394],{"id":493},"gpt-56-sol",[322,495,496],{},"如果任務開始變得比較複雜，例如：",[329,498,501],{"className":499,"code":500,"language":334,"meta":335},[332],"很難追的 Bug\n\n大型 Refactor\n\n架構分析\n\n跨很多檔案的修改\n\n需要比較多推理的工作\n",[337,502,500],{"__ignoreMap":335},[322,504,505],{},"就可以考慮 Sol。",[322,507,508],{},"OpenAI 將 GPT-5.6 Sol 定位為：",[458,510,511],{},[322,512,513],{},"複雜專業工作的旗艦模型。",[322,515,516],{},"而且它本身也特別強調 Coding、Research、Science、Cybersecurity 與 Computer Use 等複雜工作。",[416,518],{},[419,520,405],{"id":521},"gpt-6-astra",[322,523,524],{},"如果工作規模再更大，例如：",[329,526,529],{"className":527,"code":528,"language":334,"meta":335},[332],"大型 Codebase\n\n複雜跨系統問題\n\n長時間多步驟任務\n\n需要大量工具操作\n\n從分析一路做到修改與驗證\n",[337,530,528],{"__ignoreMap":335},[322,532,533],{},"就可以考慮 GPT-6 Astra。",[322,535,536],{},"OpenAI 目前將 Astra 定位為：",[458,538,539],{},[322,540,541],{},[463,542,543],{},"最有能力、用來處理最困難端到端工作的模型。",[322,545,436],{},[329,547,550],{"className":548,"code":549,"language":334,"meta":335},[332],"分析整個專案\n↓\n找出問題\n↓\n規劃修改\n↓\n實際修改\n↓\n執行測試\n↓\n修正失敗\n↓\n重新驗證\n",[337,551,549],{"__ignoreMap":335},[322,553,554],{},"這類工作才比較符合 Astra 的使用情境。",[322,556,557],{},"但一般的小修改不一定需要直接使用最高階模型。",[416,559],{},[419,561,563],{"id":562},"那-gpt-53-codex-呢","那 GPT-5.3-Codex 呢？",[322,565,566],{},"之前 Codex 還有一個很常看到的模型：",[329,568,571],{"className":569,"code":570,"language":334,"meta":335},[332],"GPT-5.3-Codex\n",[337,572,570],{"__ignoreMap":335},[322,574,575],{},"它是 OpenAI 特別針對：",[329,577,580],{"className":578,"code":579,"language":334,"meta":335},[332],"Agentic Coding\n長流程程式開發\nTool Use\nTerminal 操作\n複雜執行\n",[337,581,579],{"__ignoreMap":335},[322,583,584],{},"最佳化的 Coding 模型。",[322,586,587],{},"不過模型更新很快。",[322,589,590],{},"現在 Codex 的主要選擇已經可以看到：",[329,592,595],{"className":593,"code":594,"language":334,"meta":335},[332],"GPT-5.6 Luna\nGPT-5.6 Terra\nGPT-5.6 Sol\nGPT-6 Astra\n",[337,596,594],{"__ignoreMap":335},[322,598,599],{},"所以如果只是剛開始使用 Codex，不需要特別去背不同世代的 Codex 模型。",[322,601,602],{},"知道：",[458,604,605],{},[322,606,607,610],{},[337,608,609],{},"GPT-5.3-Codex"," 是前一階段偏 Agentic Coding 的專用模型。",[322,612,613],{},"就已經足夠。",[416,615],{},[419,617,618],{"id":618},"不一定永遠使用最強模型",[322,620,621],{},"我目前會先簡單理解成：",[329,623,626],{"className":624,"code":625,"language":334,"meta":335},[332],"小修改、搜尋\n↓\nLuna\n\n\n一般日常開發\n↓\nTerra\n\n\n複雜 Coding \u002F Debug\n↓\nSol\n\n\n大型、高難度、端到端工作\n↓\nAstra\n",[337,627,625],{"__ignoreMap":335},[322,629,630],{},"但這不是硬性規則。",[322,632,633],{},"例如一個看似很小的 Bug，也可能需要很多推理；反過來，大量檔案修改如果規則很明確，也不一定非得使用最高階模型。",[322,635,636],{},"所以比起死背：",[329,638,641],{"className":639,"code":640,"language":334,"meta":335},[332],"這個工作 = 一定使用某個模型\n",[337,642,640],{"__ignoreMap":335},[322,644,645],{},"我覺得比較實際的是：",[329,647,650],{"className":648,"code":649,"language":334,"meta":335},[332],"先看工作複雜度\n↓\n需要多少推理？\n↓\n範圍有多大？\n↓\n再決定模型\n",[337,651,649],{"__ignoreMap":335},[322,653,654],{},"模型本身也會持續更新，所以實際使用 Codex 時，還是以當下提供的模型清單為準。",{"title":335,"searchDepth":656,"depth":656,"links":657},3,[658,660,661,662,663,664],{"id":421,"depth":659,"text":372},2,{"id":453,"depth":659,"text":383},{"id":493,"depth":659,"text":394},{"id":521,"depth":659,"text":405},{"id":562,"depth":659,"text":563},{"id":618,"depth":659,"text":618},false,"md",null,{},true,"2026-09-13",[],{"title":306,"description":307},"posts\u002F20260913.codex-model-selection",[230,296,309,297],"qFY9aI61RmPwYHm7CO8ST5fUQZTzhaj1OOcG_Red4YE",[677,680],{"title":312,"path":311,"stem":678,"description":313,"category":228,"publishedAt":679,"children":-1},"posts\u002F20260914.claude-code-codex-cli-command-cheatsheet","2026-09-14",{"title":300,"path":299,"stem":681,"description":301,"category":228,"publishedAt":682,"children":-1},"posts\u002F20260912.claude-model-selection","2026-09-12",1791786900369]