Context at a glance

Show useful context about the shared session

Before reading a long transcript, recipients can see what kind of session they are opening: how much conversation it contains, how tool-heavy it was, how long it ran, and—when available—which model and effort setting produced it.

Automatic transcript statistics

The server derives user turns, assistant replies, tool calls, line count, byte size, timestamps, and duration from the JSONL.

Human-readable title

A title is extracted from available session records and included in the readable URL suffix and browser metadata.

Optional runtime context

The skill can send model, reasoning effort, and subscription-plan labels as headers without changing the transcript body.

Derived from the uploaded record

InstaShare scans the structured events to count meaningful user and assistant turns and tool-use blocks. The earliest and latest relevant timestamps produce a session duration when both are available. These values describe the captured transcript, not CPU time, billing, or uninterrupted active work.

The title comes from session metadata when present and falls back to useful transcript content. A slug-safe version is appended to the short random identifier, creating a URL that is easier to recognize while preserving the identifier used for lookup.

Some context exists only at runtime

The persisted Claude Code record may contain a base model identifier, but it does not always preserve the full display label, context-window marker, or reasoning effort shown in the live interface. The running agent can pass those optional values in request headers. The plan label may be read from local Claude account configuration.

Missing values degrade gracefully. InstaShare does not invent an effort level or plan, and the viewer can still show transcript-derived counts without those headers.

Metadata refreshes with a stable-link update

When the same session is shared again, counts, timestamps, duration, title, and available session metadata are recomputed. Header-less updates do not intentionally wipe earlier effort or plan values that cannot be reconstructed from the JSONL.

How it works

01

Parse meaningful events

User, assistant, and tool-use records are identified across the transcript.

02

Compute counts and timing

Relevant timestamps and event totals become summary statistics.

03

Merge optional headers

Live model, effort, and plan context is accepted when supplied.

04

Present concise context

The viewer header and My shares list display the fields that are available.

Important limits

  • Duration is derived from recorded event timestamps and should not be treated as exact active-working time.
  • Model, effort, and plan labels are optional and can be absent from older or custom uploads.

Try it in a Claude Code session.

Install the readable skill, then say “share this chat” when the conversation is ready.