Make it in Codex.
Open it anywhere.
Give Codex a precise HTML artifact profile plus a redacted, provider-neutral path for handing selected conversation context to another agent.
Public install pending.
This page previews the checked-in Codex adapter while release validation is underway. The public source repository and install channel are not live yet, so there is no external command to run today.
plugins/linkifact/Source preview · public publication pending · tested with Codex CLI 0.153.1Keep using the local repository copy for development and QA. A reviewed public URL, exact install/update/uninstall commands, and release digest will replace this notice at release.
Machine-readable channel status →Be explicit about sharing.
The integration only publishes after a clear artifact or share request. Incidental HTML generation stays local.
Create a self-contained responsive dependency map, then publish it with Linkifact.
Account-owned artifactExact expiry returned by the API
https://linkifact.com/artifacts/7fz2…Viewer link out.
Account token stays in.
Your agent returns only the public share URL and exact expiry. The CLI reads the scoped account token from private configuration and never copies that credential into chat or routine output.
Carry context.
Leave runtime state behind.
Linkifact converts only a file you select into a provider-neutral Session Bundle. It recognizes and redacts common credential and absolute-path patterns, while structured adapters omit recognized tool turns by default. Opaque Markdown can contain tool or terminal output. Review the entire bundle because unknown sensitive content can remain.
Save a user-selected Codex conversation export as ./codex-session.md, then use $linkifact-session to export that file with generic-markdown to ./reviewed-session.json.- Source
- A user-selected Markdown conversation export from Codex
- Review + publish
- Inspect the entire canonical bundle, create an owner-private key with
session recovery-key, then runsession publishwith--confirm-privacy,--idempotency-key-file, and a scoped account token. - Two public URLs
- The branded viewer is for people; the cookie-free bundle URL is the only remote URL accepted by
session import. - Target renderer
- Select Codex, Claude Code, Pi, Gemini CLI, Copilot CLI, or generic Markdown and write the injection-warned continuation to an explicit private path.
- Built-in adapters omit
- Native metadata fields, hidden state, approvals, branches, and live tool handles
Never open, paste, stage, or commit the private key file; reuse it only for an uncertain retry of the exact reviewed bundle. Review the continuation file, then explicitly attach or paste it into a new request in the selected harness. No transcript discovery. No native session-store writes. No automatic model-provider upload. This is not native resume behavior.
The checked-in plugin combines the canonical skills with the checked-in CLI for account-authenticated publication. Public plugins are also available in Codex in the ChatGPT desktop app; the IDE extension does not support plugins. Linkifact supports a user-selected Markdown conversation export through generic-markdown without depending on any particular Codex slash-command spelling. Its raw rollout parser is experimental and compatibility-pinned to the supported response-item subset verified for Codex CLI 0.148.x and 0.153.x; interim assistant commentary and unknown structural variants are omitted. Codex also offers a native /import flow for selected Claude Code or Cursor setup, projects, and recent chats; Linkifact adds redaction-reviewed URL sharing and other harness pairs.
Share the result—or carry the context forward.
Create a free account to publish sandboxed artifacts, organize collections, and share reviewed session context.