Every session deserves a URL.

Bring your CLI agent’s sessions into a readable web view. Find the issue, follow the evidence, and share it with a colleague as an end-to-end encrypted link, within seconds.

curl -fsSL https://session.link/install.sh | sh

Works with your favorite agent harness.

Claude Code Codex OpenCode pi omp Hermes Agent DeepSeek Harness
session.link/demo
The session.link viewer opens on a research recommendation and its human input, with search, conversation navigation, and agent activity below.

Open the live example, a fictional session rendered by the real viewer.

How it works

From your terminal to a link a colleague can read, in three commands.

Ready whenever you need it.

curl -fsSL https://session.link/install.sh | sh
curl -fsSL https://session.link/install.sh | sh downloading slink_0.9.1_darwin_arm64.tar.gz (v0.9.1)… checksum ok ✓ installed slink v0.9.1 → /usr/local/bin/slink
One native binary, under 15 MBNo Node, no SDK, no account to start reading.

Run it in your project. Pick a session and start reading.

slink view
slink view http://127.0.0.1:57359#access=j7BO… Local preview ready · nothing uploaded http://127.0.0.1:57359#access=j7BO… Saved previews: ~/.slink/previews Ctrl-C to stop the viewer.
The local viewer lists this project’s sessions by day, with a search field above them.

Choose a session, confirm, and get an encrypted link for your colleague.

slink share --pick
slink share --pick 3fa9c1 5m ago Go ahead, search this session 5 spans sample-model b07e42 50m ago Why failed requests kept retrying 4 spans sample-model 9d14ae 1d ago Make the empty state useful 3 spans sample-model share which? [3fa9c1] "Go ahead, search this session" 5 spans · sample-model · 3 KB · reconstructed · captured 5m ago ✓ no credentials detected ready to publish to https://session.link as you@example.com encrypted — anyone with the complete link can view it Publish? [y/N] y ✓ published (URL copied) https://session.link/s/k7qm2xrw9tbn4c#key=Zp3vX8… anyone with this link can view it take offline: slink delete s/k7qm2xrw9tbn4c
session.link/s/k7qm2xrw9tbn4c#key=Zp3vX8…URL copied

Your session.
You’re always in control.

Every share is encrypted on your machine. The key travels in the link, never to the server.

session.link/s/k7qm2xrw9tbn4c
#key=Zp3vX8…

What session.link stores

Ciphertext. Each share is sealed on your machine with its own AES-256-GCM key before upload.

What the link unlocks

Let people try it before they configure itStart with a sample project that produces a useful result.

Readable, for whoever holds the link. The key rides in the # fragment, which browsers never send to the server.

Rather name your readers? Named shares open only for the verified emails you invite.

Local until you publish

Opening and preparing a view keeps the material on your machine. Publishing is an explicit action, and slink delete takes a link offline again.

Review what travels

A shared view holds only what you include, plus your note. Exports are checked for common credential formats before upload. It is a safety net, so still review sensitive content yourself.

Yours to keep

The CLI, viewer, and session format are open source. Your captures stay on disk, readable with or without the hosted service.