linkifact
Sign inPublish HTML
ProductIntegrationsSecurityDocsPricingSign inPublish HTML
Agent integrations

Share the output.
Carry the context.

Every Linkifact integration shares the same explicit artifact workflow and the same redacted session-continuation format. Publish a self-contained visual result, or review selected conversation context before handing it to another coding agent.

How portable session sharing works →

Integration release status: adapter source is available in the project checkout for maintainer QA. Public repositories, marketplace entries, and npm packages are not published yet; each guide shows its current release status. Read the exact machine status.

01C

Claude Code

Plugin + skills

Explicit artifact publishing plus reviewed Claude Code session handoff through a portable continuation bundle.

Beta status →
02O

Codex

CLI plugin + skills

Artifact publishing and reviewed continuation from a user-selected Codex conversation Markdown export. The IDE extension does not support plugins.

Beta status →
03π

Pi

TypeScript extension + skills

Native artifact tooling plus an explicit, review-gated Pi session exchange command.

Beta status →
04G

Gemini CLI

CLI extension + skills

Artifact publishing plus reviewed continuation from a user-selected /chat share export.

Beta status →
05⌁

Copilot CLI

Agent Plugin + skills

Artifacts and reviewed continuation from a user-selected /share file Markdown export.

Beta status →
One shared behavior

Portable, explicit, and pleasantly unsurprising.

01
No incidental uploads

HTML and transcripts stay local unless the user explicitly selects an input and requests publication.

02
Review before session sharing

Recognized secrets and absolute paths are redacted. Structured adapters omit recognized tool turns by default; opaque Markdown can contain tool output, so the user inspects the entire local bundle.

03
Modular continuation, not native resume

Versioned target renderers emit injection-warned Markdown with destination guidance. Linkifact never writes harness session stores or claims to restore private model state and live tools.

04
One release path

Maintainers can test the checked-in skills, CLI, and adapters now. Public install channels open only after beta validation.

Universal transports

One contract, several release paths.

CLI

Portable commands

The checked-in CLI validates artifacts and converts selected sessions into one strict bundle format. Public npm installation follows beta validation.

Workflow guide →
REST

Plain HTTPS

Post JSON or multipart HTML and receive the same versioned response contract.

API reference →
Compatible by design

Give your agents a shared output and context layer.

Create a free account to publish sandboxed artifacts, organize collections, and share reviewed session context.

Create a free account →