Merge branch 'main' into codex-mcp-agents-image-fix

Author: jhall-openai

authors.yaml

@@ -494,7 +494,7 @@ heejingithub:
   avatar: "https://avatars.githubusercontent.com/u/169293861"
 
 
-himadri: 
+himadri518: 
   name: "Himadri Acharya"
   website: "https://www.linkedin.com/in/himadri-acharya-086ba261/"
   avatar: "https://avatars.githubusercontent.com/u/14100684?v=4"
@@ -504,4 +504,4 @@ jhall-openai:
   website: "https://www.linkedin.com/in/jhall14/"
   avatar: "https://avatars.githubusercontent.com/u/198997750?v=4"
 
-  
+  

examples/codex/Autofix-github-actions.ipynb

@@ -15,7 +15,8 @@
     "\n",
     "Below is the pipeline flow we’ll implement:\n",
     "\n",
-    "![](images/ci-codex-workflow.png)"
+    "\n",
+    "<img src=\"../../images/ci-codex-workflow.png\"  width=\"700\"/>"
    ]
   },
   {
@@ -33,7 +34,8 @@
     "\n",
     "- You’ll need to check the setting to enable actions to create PRs on your repo, and also in your organization:\n",
     "\n",
-    "![](images/github-pr-settings.png)"
+    "\n",
+    "<img src=\"../../images/github-pr-settings.png\" width=\"700\"/>\n"
    ]
   },
   {
@@ -159,8 +161,7 @@
     "\n",
     "You can navigate to the Actions tab under Repo to view the failing jobs in your Actions workflow. \n",
     "\n",
-    "\n",
-    "![](images/failing-workflow.png)\n"
+    "<img src=\"../../images/failing-workflow.png\" width=\"700\"/>\n"
    ]
   },
   {
@@ -171,7 +172,7 @@
     "The Codex workflow should be triggered upon completion of the failed workflow. \n",
     "\n",
     "\n",
-    "![](images/codex-workflow.png)\n",
+    "<img src=\"../../images/codex-workflow.png\" width=\"700\"/>\n",
     "\n"
    ]
   },
@@ -183,7 +184,8 @@
     "## Step 5: Codex generated PR for review\n",
     "And after the Codex workflow completes execution, it should open a pull request from the feature branch codex/auto-fix. Check to see if everything looks good and then merge it.\n",
     "\n",
-    "![](images/codex-pr.png)"
+    "<img src=\"../../images/codex-pr.png\" width=\"700\"/>\n",
+    "\n"
    ]
   },
   {

examples/codex/codex_mcp_agents_sdk/building_consistent_workflows_codex_cli_agents_sdk.ipynb

@@ -114,7 +114,7 @@
     "\n",
     "| Example gameplay | Game Over Score |\n",
     "| :---: | :---: |\n",
-    "| <img src=\"../../../images/game_example_1.png\" alt=\"Example gameplay\" width=\"320\" /> | <img src=\"../../../images/game_example_1.png\" alt=\"Game Over Score\" width=\"320\" /> |"
+    "| <img src=\"../images/game_example_1.png\" alt=\"Example gameplay\" width=\"320\" /> | <img src=\"../images/game_example_2.png\" alt=\"Game Over Score\" width=\"320\" /> |"
    ]
   },
   {
@@ -203,7 +203,7 @@
     "In this example, we intentionally have the Project Manager agent enforce gating logic between each of the specialized downstream agents. This ensures that artifacts exist before handoffs are made. This mirrors real world enterprise workflows such as JIRA task orchestration, long-chained rollouts, and QA sign-offs.  \n",
     "\n",
     "<div align=\"center\">\n",
-    "  <img src=\"../../../images/multi_agent_codex_workflow.png\" alt=\"Multi-Agent Codex Workflow with Codex MCP\" style=\"max-width: 100%; width: 960px;\" />\n",
+    "  <img src=\"../images/multi_agent_codex_workflow.png\" alt=\"Multi-Agent Codex Workflow with Codex MCP\" style=\"max-width: 100%; width: 960px;\" />\n",
     "  <br />\n",
     "  <em>Multi-agent orchestration with Codex MCP and gated handoffs producing artifacts.</em>\n",
     "</div>\n",
@@ -633,15 +633,15 @@
     "Let’s take a look at the agent trace for the team of agents above.\n",
     "\n",
     "<div align=\"center\">\n",
-    "  <img src=\"../../../images/multi_agent_trace.png\" alt=\"Multi-Agent Codex Workflow with Codex MCP\" style=\"max-width: 100%; width: 960px;\" />\n",
+    "  <img src=\"../images/multi_agent_trace.png\" alt=\"Multi-Agent Codex Workflow with Codex MCP\" style=\"max-width: 100%; width: 960px;\" />\n",
     "</div>\n",
     "\n",
     "In this Trace, we can confirm that every agent handoff is quarterbacked by our Project Manager Agent who is confirming that specific artifacts exist before handoff to the next agent. Additionally, we can see specific innovations of the Codex MCP Server and generate each output by calling the Responses API. The timeline bars highlight execution durations, making it easy to spot long-running steps and understand how control passes between agents.\n",
     "\n",
     "You can even click into each trace to see the specific details of the prompt, tool calls, and other metadata. Over time you can view this information to further tune, optimize, and track your agentic system performance.\n",
     "\n",
     "<div align=\"center\">\n",
-    "  <img src=\"../../../images/multi_agent_trace_details.png\" alt=\"Multi-Agent Trace Details\" style=\"max-width: 100%; width: 960px;\" />\n",
+    "  <img src=\"../images/multi_agent_trace_details.png\" alt=\"Multi-Agent Trace Details\" style=\"max-width: 100%; width: 960px;\" />\n",
     "</div>\n"
    ]
   },