Give every coding agent the same source of truth.

Publish shared context, not loose files.

A folder of markdown can contain valuable context, but it is difficult to reuse when every agent needs the same local files and path conventions. okfshare gives that folder a stable publishing boundary. Your agent writes the bundle, the validator checks it, and the service creates an immutable revision with a durable URL.

Made for agent workflows

The canonical setup is npx okfshare@latest setup. Device pairing requires a human to open the pairing URL in a browser. If a pre-provisioned credential is supplied to the agent process, use OKFSHARE_TOKEN instead. Never paste credentials into chat, command arguments, project files, or output. Check only whether the variable exists, never print its value. The credential needs read and write scopes. Verify with npx okfshare@latest whoami and npx okfshare@latest doctor --json. Start with the free workspace or sign in to an existing one.

From agent output to reusable cited context in three stages.

1. Publish agent output

Keep using markdown and YAML frontmatter. Add a concept type, title, description, tags, sources, status, or verification events when they help readers understand the material. You do not need to learn a proprietary editor or rebuild your agent pipeline.

2. Resolve an immutable revision

okfshare checks safe file paths, required OKF fields, bundle size, secret patterns, and the root document before storage. A successful publish creates an immutable revision, which gives readers a consistent snapshot instead of a half-updated folder.

3. Retrieve and reuse context

Ask an authorized agent for bounded cited context, search by terms, or pull the complete revision. Humans can open the durable browser link directly.

The Open Knowledge Format keeps context portable.

OKF v0.2 is markdown with structured frontmatter. The required type field identifies what a document represents, while optional metadata records provenance, lifecycle, trust, and relationships. This keeps the content readable as plain text and useful to tools that understand the schema.

Metadata that travels with the document

Describe concepts with titles and summaries, connect related files with links, identify sources, and record when material was generated or verified. The format is intentionally small: add structure when it improves understanding, not because a platform requires a long form.

Publish, resolve, retrieve, reuse.

Publish from a local folder, resolve an immutable revision, then retrieve bounded cited context or pull a complete local copy. Use the durable browser link when a human needs to read the source.

Agent retrieval is authenticated and workspace-scoped. Browser visibility is a separate sharing choice for humans, so a durable link does not make retrieval anonymous.

Start sharing agent context for free.

The free launch includes 25 shares and 100 MB of bundle storage with no credit card or billing setup. Publish a small folder, then retrieve its context from an authorized agent.