Open Artifact for Codex and ChatGPT desktop
Slide decks, design canvases, whiteboards, data dashboards and design systems as folders of files that open in one local page where you view, edit
and comment. Ask for /open-artifact slides …, design …, whiteboard … or data … (the skill is open-artifact:open-artifact).
Install
codex plugin marketplace add /path/to/open-artifacts/dist/plugins
then install Open Artifact from /plugins in the Codex CLI or the Plugins tab of the Codex or ChatGPT desktop app
(or codex plugin add open-artifact@open-artifact), and start a new session. Codex runs plugin hooks only once you
approve them in /hooks (again after each update); the tools work before that.
New artifacts go under the thread's folder (artifacts/<slug>). Codex starts the MCP server in the plugin's own
folder, so the daemon looks the thread's folder up: from its hook, or from the thread's rollout file in
~/.codex/sessions ($CODEX_HOME).
What it adds
mcp.json: theArtifact,ArtifactDataandArtifactCommentstools (stdio, through the local daemon);skills/open-artifact/: the skill, carrying the daemon;hooks/hooks.json: SessionStart, UserPromptSubmit and Stop.
Send to agent
Comments sent from the page reach the thread that made the artifact at session start, with your next message, or,
when they arrive while Codex works, by keeping its turn going (the Stop hook). Without the hooks they come with the
thread's next Open Artifact tool call. While the thread is idle, the daemon queues a short message for it with
codex queue --thread <id> --message … (the codex the ChatGPT app carries, else the one on the PATH;
$OPEN_ARTIFACT_CODEX_BIN names another). The desktop app runs a queued message as soon as the thread is idle (tried
with a thread open in the ChatGPT app), which starts a turn that handles the comments. A thread run only from the
command line (codex exec) gets it the next time it is resumed.
The page opens in the app's built-in browser, which the agent opens with the page's view_url, not in the
computer's browser.