بنقرة واحدة
codex-pro-max
Use when Codex Pro Max is running; manage Codex session, conclusion, and wait through backend endpoints.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Use when Codex Pro Max is running; manage Codex session, conclusion, and wait through backend endpoints.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | codex-pro-max |
| description | Use when Codex Pro Max is running; manage Codex session, conclusion, and wait through backend endpoints. |
Use this skill only when http://127.0.0.1:53127/api/healthy is reachable. If not reachable, answer normally.
Use the current Codex thread id.
Endpoint flow, with no timeout on the wait request:
Invoke-RestMethod -Method Post "http://127.0.0.1:53127/api/codex/sessions/by-thread/<threadId>" -ContentType "application/json" -Body '{"displayName":"Current Codex Conversation"}'
Do the user's task.
Build the conclusion body with ConvertTo-Json. Do not hand-build JSON or paste raw AI text into a JSON string.
$conclusion = @'
<normal Codex conclusion>
'@
$body = @{ content = $conclusion } | ConvertTo-Json -Depth 4
Invoke-RestMethod -Method Post "http://127.0.0.1:53127/api/codex/sessions/by-thread/<threadId>/conclusion" -ContentType "application/json" -Body $body
Invoke-RestMethod -Method Post "http://127.0.0.1:53127/api/codex/sessions/by-thread/<threadId>/wait"
The wait loop is compulsory and indefinite:
timeoutMs, TimeoutSec, query-string timeout values, request-body timeout values, or host timeout wrappers to the /wait call./wait is pending, stay silent. Do not send progress messages just to say you are waiting./wait with status checks. Status checks are only for debugging and must be followed by /wait again./wait returns instruction.content, do that instruction, submit another conclusion, then immediately call /wait again./wait returns no instruction, timedOut=true, stopped=true, an empty response, a client timeout, a broken connection, or any non-instruction result, immediately call /wait again with the same thread id and no timeout.instruction.content; after handling it, return to the wait loop.Never stop waiting for Codex Pro Max unless the user explicitly tells you in this chat to stop using Codex Pro Max.