Linkifact for Copilot CLI

Make it in Copilot CLI.
Open it anywhere.

Use the open Agent Plugins format for artifact publishing and reviewed continuation from a deliberately exported Copilot CLI conversation.

01 / Distribution

Public install pending.

This page previews the checked-in Copilot CLI 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.

MAINTAINER SOURCE PATHintegrations/copilot/Source preview · public publication pending · tested with GitHub Copilot CLI 1.0.83

Keep 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 →
02 / Ask

Be explicit about sharing.

The integration only publishes after a clear artifact or share request. Incidental HTML generation stays local.

YOU

Use the linkifact-publish skill to turn this release report into a visual HTML brief and share it.

Linkifact publish is authorized by this request
✓

Account-owned artifactExact expiry returned by the API

https://linkifact.com/artifacts/7fz2…
03 / Share

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.

04 / Continue

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.

EXPLICIT SESSION REQUEST/share file ./copilot-session.md, then use linkifact-session to export that path with generic-markdown to ./reviewed-session.json.
Source
A user-selected Markdown file from Copilot CLI's /share file command
Review + publish
Inspect the entire canonical bundle, create an owner-private key with session recovery-key, then run session publish with --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.

INTEGRATION NOTE

The checked-in integration uses the canonical skill and CLI for account-authenticated publication. Linkifact reads only the selected export, not Copilot's native store. Public plugin distribution follows release validation.

Start from Copilot CLI

Share the result—or carry the context forward.

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