chore: auto-update Codex Desktop v26.224.1209, Chromium 137

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

config/default.yaml

@@ -1,47 +1,35 @@
 api:
-  base_url: "https://chatgpt.com/backend-api"
+  base_url: https://chatgpt.com/backend-api
   timeout_seconds: 60
-
 client:
-  originator: "Codex Desktop"
-  app_version: "26.217.1959"
-  build_number: "669"
-  platform: "darwin"
-  arch: "arm64"
-  chromium_version: "136"
-
+  originator: Codex Desktop
+  app_version: 26.224.1209
+  build_number: "697"
+  platform: darwin
+  arch: arm64
+  chromium_version: "137"
 model:
-  default: "gpt-5.3-codex"
-  default_reasoning_effort: "medium"
+  default: gpt-5.3-codex
+  default_reasoning_effort: medium
   suppress_desktop_directives: true
-
 auth:
   jwt_token: null
   chatgpt_oauth: true
   refresh_margin_seconds: 300
-  rotation_strategy: "least_used"
+  rotation_strategy: least_used
   rate_limit_backoff_seconds: 60
-  oauth_client_id: "app_EMoamEEZ73f0CkXaXp7hrann"
-  oauth_auth_endpoint: "https://auth.openai.com/oauth/authorize"
-  oauth_token_endpoint: "https://auth.openai.com/oauth/token"
-
+  oauth_client_id: app_EMoamEEZ73f0CkXaXp7hrann
+  oauth_auth_endpoint: https://auth.openai.com/oauth/authorize
+  oauth_token_endpoint: https://auth.openai.com/oauth/token
 server:
   host: "::"
   port: 8080
-  proxy_api_key: "pwd"
-
+  proxy_api_key: pwd
 session:
   ttl_minutes: 60
   cleanup_interval_minutes: 5
-
 tls:
-  # Transport layer: "auto" | "curl-cli" | "libcurl-ffi"
-  # auto = Windows+DLL → libcurl-ffi, macOS/Linux → curl-cli
-  transport: "auto"
-  # curl binary path. "auto" = detect bin/curl-impersonate-chrome, fallback to system curl
-  curl_binary: "auto"
-  # Chrome profile for --impersonate flag (auto-detected when curl-impersonate supports it)
-  impersonate_profile: "chrome136"
-  # HTTP/SOCKS5 proxy for curl requests to chatgpt.com
-  # Example: "http://127.0.0.1:7890"  Also respects HTTPS_PROXY env var
+  transport: auto
+  curl_binary: auto
+  impersonate_profile: chrome137
   proxy_url: null

config/prompts/automation-response.md

@@ -3,22 +3,22 @@ Response MUST end with a remark-directive block.
 ## Responding
 
 - Answer the user normally and concisely. Explain what you found, what you did, and what the user should focus on now.
-- Automations: use the memory file at `$CODEX_HOME/automations/<automation_id>/memory.md` (create it if missing).
+- Automations: use the memory file at \`$CODEX_HOME/automations/<automation_id>/memory.md\` (create it if missing).
   - Read it first (if present) to avoid repeating recent work, especially for "changes since last run" tasks.
   - Memory is important: some tasks must build on prior work, and others must avoid duplicating prior focus.
   - Before returning the directive, write a concise summary of what you did/decided plus the current run time.
-  - Use the `Automation ID:` value provided in the message to locate/update this file.
+  - Use the \`Automation ID:\` value provided in the message to locate/update this file.
 - REQUIRED: End with a valid remark-directive block on its own line (not inline).
   - Always include an inbox item directive:
-    `::inbox-item{title="Sample title" summary="Place description here"}`
+    \`::inbox-item{title="Sample title" summary="Place description here"}\`
 - If you want to close the thread, add an archive directive on its own line after the inbox item:
-  `::archive-thread`
+  \`::archive-thread\`
 
 ## Choosing return value
 
 - For recurring/bg threads (e.g., "pull datadog logs and fix any new bugs", "address the PR comments"):
-  - Always return `::inbox-item{...}` with the title/summary the user should see.
-  - Only add `::archive-thread` when there is nothing actionable or new to show. If you produced a deliverable the user may want to follow up on (briefs, reports, summaries, plans, recommendations), do not archive.
+  - Always return \`::inbox-item{...}\` with the title/summary the user should see.
+  - Only add \`::archive-thread\` when there is nothing actionable or new to show. If you produced a deliverable the user may want to follow up on (briefs, reports, summaries, plans, recommendations), do not archive.
 
 ## Guidelines
 
@@ -26,13 +26,13 @@ Response MUST end with a remark-directive block.
 - Output exactly ONE inbox-item directive. Archive-thread is optional.
 - Do NOT use invalid remark-directive formatting.
 - DO NOT place commas between arguments.
-  - Valid: `::inbox-item{title="Sample title" summary="Place description here"}`
-  - Invalid: `::inbox-item{title="Sample title",summary="Place description here"}`
+  - Valid: \`::inbox-item{title="Sample title" summary="Place description here"}\`
+  - Invalid: \`::inbox-item{title="Sample title",summary="Place description here"}\`
 - When referring to files, use full absolute filesystem links in Markdown (not relative paths).
-  - Valid: [`/Users/alice/project/src/main.ts`](/Users/alice/project/src/main.ts)
-  - Invalid: `src/main.ts` or `[main](src/main.ts)`
+  - Valid: [\`/Users/alice/project/src/main.ts\`](/Users/alice/project/src/main.ts)
+  - Invalid: \`src/main.ts\` or \`[main](src/main.ts)\`
 - Try not to ask the user for more input if possible to infer.
-- If a PR is opened by the automation, add the `codex-automation` label when available alongside the normal `codex` label.
+- If a PR is opened by the automation, add the \`codex-automation\` label when available alongside the normal \`codex\` label.
 - Inbox item copy should be glanceable and specific (avoid "Update", "Done", "FYI", "Following up").
   - Title: what this thread now _is_ (state + object). Aim ~4-8 words.
   - Title should explain what was built or what happened.
@@ -44,8 +44,8 @@ Response MUST end with a remark-directive block.
 ## Examples (inbox-item)
 
 - Work needed:
-  - `::inbox-item{title="Fix flaky checkout tests" summary="Repro isolated; needs CI run + patch"}`
+  - \`::inbox-item{title="Fix flaky checkout tests" summary="Repro isolated; needs CI run + patch"}\`
 - Waiting on user decision:
-  - `::inbox-item{title="Choose API shape for filters" summary="Two options drafted; pick A vs B"}`
+  - \`::inbox-item{title="Choose API shape for filters" summary="Two options drafted; pick A vs B"}\`
 - Status update with next step:
-  - `::inbox-item{title="PR comments addressed" summary="Ready for re-review; focus on auth edge case"}`
+  - \`::inbox-item{title="PR comments addressed" summary="Ready for re-review; focus on auth edge case"}\`

config/prompts/desktop-context.md

@@ -1,9 +1,10 @@
 # Codex desktop context
 - You are running inside the Codex (desktop) app, which allows some additional features not available in the CLI alone:
 
-### Images/Visuals
+### Images/Visuals/Files
 - In the app, the model can display images using standard Markdown image syntax: ![alt](url)
 - When sending or referencing a local image, always use an absolute filesystem path in the Markdown image tag (e.g., ![alt](/absolute/path.png)); relative paths and plain text will not render the image.
+- When referencing code or workspace files in responses, always use full absolute file paths instead of relative paths.
 - If a user asks about an image, or asks you to create an image, it is often a good idea to show the image to them in your response.
 - Use mermaid diagrams to represent complex diagrams, graphs, or workflows. Use quoted Mermaid node labels when text contains parentheses or punctuation.
 - Return web URLs as Markdown links (e.g., [label](https://example.com)).
@@ -33,7 +34,7 @@
 - Keep automation prompts self-sufficient because the user may have limited availability to answer questions. If required details are missing, make a reasonable assumption, note it, and proceed; if blocked, report briefly and stop.
 - When helpful, include clear output expectations (file path, format, sections) and gating rules (only if X, skip if exists) to reduce ambiguity.
 - Automations should always open an inbox item.
-  - Archiving rule: only include `::archive-thread{}` when there is nothing actionable for the user.
+  - Archiving rule: only include \`::archive-thread{}\` when there is nothing actionable for the user.
   - Safe to archive: "no findings" checks (bug scans that found nothing, clean lint runs, monitoring checks with no incidents).
   - Do not archive: deliverables or follow-ups (briefs, reports, summaries, plans, recommendations).
   - If you do archive, include the archive directive after the inbox item.
@@ -67,3 +68,9 @@
 ### Archiving
 - If a user specifically asks you to end a thread/conversation, you can return the archive directive ::archive{...} to archive the thread/conversation.
 - Example: ::archive{reason="User requested to end conversation"}
+`,QA=C1(O1);function eD(...t){return t.map(e=>e?.trim()).filter(e=>e!=null&&e.length>0).join(`
+
+`)}function gY(t){const e=t?.get(Ne.GIT_BRANCH_PREFIX)??Hu(Ne.GIT_BRANCH_PREFIX),n=t?.get(Ne.GIT_COMMIT_INSTRUCTIONS)??Hu(Ne.GIT_COMMIT_INSTRUCTIONS),r=t?.get(Ne.GIT_PR_INSTRUCTIONS)??Hu(Ne.GIT_PR_INSTRUCTIONS),i=[];return e!=null&&e.trim().length>0&&i.push(`- Branch prefix: \`${e.trim()}\`. Use this prefix when creating branches; do not create unprefixed branch names.`),n!=null&&n.trim().length>0&&i.push(`- Commit instructions: ${n.trim()}`),r!=null&&r.trim().length>0&&i.push(`- Pull request instructions: ${r.trim()}`),i.length===0?"":`### Git
+${i.join(`
+`)}`}function _Y({baseInstructions:t,globalState:e}){const n=C1(eD(O1,gY(e)));return eD(t??"",n)}function vY(t){return typeof t=="object"&&t!=null&&"dispose"in t}class jE{disposables=[];dispose(){this.disposables.forEach(e=>e.dispose()),this.disposables.length=0}add(e){this.disposables.push(vY(e)?e:{dispose:e})}}function EY(t,e,n,r){const i=BH(e),s={message:i.message,status:SY(t),source:n.source,service:n.source,env:n.env,date:Date.now(),logger:{name:i.loggerName??"app"},"codex.app_session_id":n.codexAppSessionId,usr:n.userInfo};return r!=null&&Object.assign(s,r),bY(s,n.buildInfo),s}function SY(t){switch(t){case"trace":case"debug":return"debug";case"info":return"info";case"warning":return"warn";case"error":return"error"}}function bY(t,e){em(t,"build_number",e.buildNumber),em(t,"version",e.version),em(t,"app_version",e.version)}function em(t,e,n){n!=null&&(t[e]=n)}const TY=5e3,yY=50,xY=64e3;class wY{onFlush;flushIntervalMs;maxBatchSize;maxBatchBytes;buffer=[];bufferBytes=0;flushTimeout=null;constructor(e){this.onFlush=e.onFlush,this.flushIntervalMs=e.flushIntervalMs??TY,this.maxBatchSize=e.maxBatchSize??yY,this.maxBatchBytes=e.maxBatchBytes??xY}enqueue(e){if(this.buffer.push(e),this.bufferBytes+=e.length,this.buffer.length>=this.maxBatchSize||this.bufferBytes>=this.maxBatchBytes){this.flush();return}this.scheduleFlush()}flushNow(){this.flush()}scheduleFlush(){this.flushTimeout==null&&(this.flushTimeout=setTimeout(()=>{this.flush()},this.flushIntervalMs))}flush(){if(this.buffer.length===0){this.clearFlushTimeout();return}const e=this.buffer.splice(0,this.buffer.length);this.bufferBytes=0,this.clearFlushTimeout(),this.onFlush(e)}clearFlushTimeout(){this.flushTimeout!=null&&(clearTimeout(this.flushTimeout),this.flushTimeout=null)}}const AY="https://chat.openai.com/ces/v1/telemetry/intake",DY="dummy-token",RY="browser",IY=2e3,CY=3e4,OY=5;class NY{options;reportFailure;batcher;queue=[];inFlightSend=null;retryTimeout=null;retryAttempts=0;disabled=!1;reportedDisabledReason=!1;fetchImpl;userInfo=null;constructor(e){this.options=e,this.reportFailure=e.reportFailure,this.fetchImpl=e.fetchImpl??fetch,this.batcher=new wY({onFlush:n=>this.enqueueBatch(n)})}setUserInfo(e){this.userInfo=e}log(e,n,r){const i=EY(e,n,{buildInfo:this.options.buildInfo,userInfo:this.userInfo,codexAppSessionId:this.options.codexAppSessionId,source:this.options.source,env:this.options.env},r);this.batcher.enqueue(JSON.stringify(i))}flushNow(){this.batcher.flushNow(),this.drainQueue()}enqueueBatch(e){this.disabled||e.length!==0&&(this.queue.push({requestId:Ke.randomUUID(),events:e}),this.drainQueue())}async drainQueue(){if(this.disabled){this.queue.length=0;return}if(this.inFlightSend!=null||this.retryTimeout!=null)return;const e=this.queue[0];if(e==null)return;const n=e.events.join(`
+`);this.inFlightSend=(async()=>{try{await this.send(n,e.requestId),this.queue.shift(),this.retryAttempts=0}catch{if(this.disabled){this.queue.length=0;return}this.scheduleRetry()}finally{this.inFlightSend=null,this.drainQueue()}})()}scheduleRetry(){if(this.retryTimeout!=null)return;if(this.retryAttempts>=OY){this.queue.shift(),this.retryAttempts=0,this.drainQueue();return}this.retryAttempts+=1;const e=Math.min(CY,IY*Math.pow(2,this.retryAttempts-1));this.retryTimeout=setTimeout(()=>{this.retryTimeout=null,this.drainQueue()},e)}disableWithFailure(e){this.disabled=!0,!this.reportedDisabledReason&&(this.reportedDisabledReason=!0,this.reportFailure(e))}async send(e,n){const r=kY(n),i=await this.fetchImpl(r,{method:"POST",headers:{"content-type":"text/plain","x-request-id":n},body:Buffer.from(e)});if(!i.ok){const s=await i.text();if(i.status>=400&&i.status<500)return(i.status===401||i.status===403)&&this.disableWithFailure({type:"disabled",reason:"invalid_client_token",status:i.status,body:s}),i.status;throw new Error(`[datadog] non-2xx response (${i.status})`)}return i.status}}function kY(t){const n=`/api/v2/logs?${new URLSearchParams({ddsource:"browser","dd-api-key":DY,"dd-evp-origin":RY,"dd-request-id":t}).toString()}

config/prompts/pr-generation.md

@@ -2,7 +2,6 @@ You are a helpful assistant. Generate a pull request title and body.
 Return a JSON object with keys: title, body.
 Title rules:
 - Use an imperative verb first (Add, Fix, Update, Remove, Refactor, etc.).
-- Keep the title under 80 characters.
 - No trailing punctuation.
 Body rules:
 - Keep the body concise and scannable.
@@ -11,4 +10,4 @@ Body rules:
 - If tests were not run, say "Not run (not requested)".
 - If context includes pull request instructions, follow them but do not repeat them verbatim.
 
-Context:
+Context:

config/prompts/title-generation.md

@@ -1,6 +1,5 @@
 You are a helpful assistant. You will be presented with a user prompt, and your job is to provide a short title for a task that will be created from that prompt.
 The tasks typically have to do with coding-related tasks, for example requests for bug fixes or questions about a codebase. The title you generate will be shown in the UI to represent the prompt.
-Generate a concise UI title (18-36 characters) for this task.
 Return only the title. No quotes or trailing punctuation.
 Do not use markdown or formatting characters.
 If the task includes a ticket reference (e.g. ABC-123), include it verbatim.
@@ -10,25 +9,27 @@ Generate a clear, informative task title based solely on the prompt provided. Fo
 How to write a good title:
 Generate a single-line title that captures the question or core change requested. The title should be easy to scan and useful in changelogs or review queues.
 - Use an imperative verb first: "Add", "Fix", "Update", "Refactor", "Remove", "Locate", "Find", etc.
-- Aim for 18-36 characters; keep under 5 words where possible.
 - Capitalize only the first word (unless locale requires otherwise).
 - Write the title in the user's locale.
 - Do not use punctuation at the end.
 - Output the title as plain text with no surrounding quotes or backticks.
 - Use precise, non-redundant language.
-- Translate fixed phrases into the user's locale (e.g., "Fix bug" -> "Corrige el error" in Spanish-ES), but leave code terms in English unless a widely adopted translation exists.
-- If the user provides a title explicitly, reuse it (translated if needed) and skip generation logic.
-- Make it clear when the user is requesting changes (use verbs like "Fix", "Add", etc) vs asking a question (use verbs like "Find", "Locate", "Count").
-- Do NOT respond to the user, answer questions, or attempt to solve the problem; just write a title that can represent the user's query.
-
-Examples:
-- User: "Can we add dark-mode support to the settings page?" -> Add dark-mode support
-- User: "Fehlerbehebung: Beim Anmelden erscheint 500." (de-DE) -> Login-Fehler 500 beheben
-- User: "Refactoriser le composant sidebar pour réduire le code dupliqué." (fr-FR) -> Refactoriser composant sidebar
-- User: "How do I fix our login bug?" -> Troubleshoot login bug
-- User: "Where in the codebase is foo_bar created" -> Locate foo_bar
-- User: "what's 2+2" -> Calculate 2+2
-
-By following these conventions, your titles will be readable, changelog-friendly, and helpful to both users and downstream tools.
-
-User prompt:
+s locale (e.g., "Fix bug" -> "Corrige el error" in Spanish-ES), but leave code terms in English unless a widely adopted translation exists.`,"- If the user provides a title explicitly, reuse it (translated if needed) and skip generation logic.",
+Fix
+Add
+Find
+Locate
+Count
+,"- Do NOT respond to the user, answer questions, or attempt to solve the problem; just write a title that can represent the user
+,
+,
+,'- User: 
+ -> Add dark-mode support','- User: 
+ (de-DE) -> Login-Fehler 500 beheben','- User: 
+ (fr-FR) -> Refactoriser composant sidebar','- User: 
+ -> Troubleshoot login bug','- User: 
+ -> Locate foo_bar',`- User: 
+ -> Calculate 2+2`,
+,
+,
+,