Skip to main content
The Artifacta Codex plugin is the recommended setup for Codex users. It bundles the hosted Artifacta MCP connection, reusable persistence skills, and verified Codex transcript capture. Authentication happens through browser OAuth—there is no API key to copy and no local Artifacta process to run.
The plugin connects to https://mcp.artifacta.io/mcp. For CI, restricted networks, or explicit API-key control, use the local stdio setup instead.

​
Prerequisites

​
Install

Add the Artifacta marketplace, then install the plugin:
Authenticate the bundled MCP server:
The login command opens Artifacta in your browser. Sign in, choose the permissions you want to grant, and authorize the connection. Start a new Codex thread after installation so Codex loads the plugin’s skills and hooks. Open /hooks, review the bundled Artifacta hook, and trust its current definition if you want to use one-shot automatic transcript capture. Codex skips untrusted non-managed hooks.

​
Verify the install

Check the installed version:
The listing should show artifacta@artifacta as installed and enabled. The current plugin version is 1.1.0. In the new thread, ask:
“Use Artifacta MCP whoami and report my tenant and plan.”
Codex should call whoami without asking for an API key.

​
What the plugin adds

  • Hosted Artifacta MCP — read, upload, retrieve, share, delete, and session tools, authorized by the OAuth tier you choose.
  • persisting-outputs skill — stores reports, datasets, generated files, and other run outputs through Artifacta MCP.
  • capture-transcript skill — locates and verifies the current Codex rollout, creates a private snapshot, and uploads it through store_artifact.
The hosted MCP server cannot read a path on your computer. The skills send small local files as base64 content; they do not pass a local path to the remote server and do not invoke the local Artifacta CLI.

​
Capture a Codex transcript

For an immediate snapshot, ask:
“Use Artifacta to capture this Codex session’s transcript.”
The skill verifies the live rollout before copying or uploading it. The snapshot is tagged with metadata.type=transcript and metadata.capture=snapshot. For one capture at the current thread’s next Stop, include the explicit flag:
“Use Artifacta to capture this Codex session’s transcript —automatic.”
--automatic is one-shot consent for this thread. It does not enable every-turn capture, future-thread capture, or an ongoing background uploader. The trusted Stop hook requests one authenticated continuation, which uploads the snapshot through Artifacta MCP.
Artifacta does not redact transcript snapshots. They can contain prompts, tool arguments, tool results, credentials, and other sensitive text. Review what your session contains before requesting capture.
See Store session transcripts for capture metadata, retrieval, and limitations.

​
OAuth permissions

Artifacta permissions are nested: artifacts:read ⊆ artifacts:write ⊆ artifacts:destroy. The plugin may list all registered tools regardless of your grant. If a call exceeds the granted tier, Artifacta returns insufficient_scope and names the required scope. To broaden access, reauthorize:
Choose Destroy only when the workflow needs public share links, deletion, or irreversible session sealing.
get_artifact_download_url is read-scoped and returns a one-hour presigned URL for direct retrieval. It is not a stable public share link. create_download_link creates the stable dl.artifacta.io/lnk_… URL and requires artifacts:destroy.
The OAuth grant survives plugin removal. Revoke it separately from app.artifacta.io if you no longer want the connection authorized.

​
Update

Refresh the marketplace, then start a new thread so Codex loads the updated cached plugin:
For a project-local marketplace, reinstall the plugin after refreshing its marketplace definition.

​
Uninstall

This removes the plugin, its bundled MCP registration, skills, and hooks from Codex. It does not delete any Artifacta artifacts or revoke the OAuth grant.

​
What’s next