A skill for Claude Code & Codex

Sling your AI's work anywhere.

You're deep in a terminal session and the answer is good. SlingIT turns it into one clean, encrypted link — continue reading on your phone, send it to a teammate, drop it straight into an inbox.

> /slingit you@example.com

Claude packs the answer, encrypts it, and hands you the link.

End-to-end encrypted
One unique link per note
Nothing for readers to install

Quick start

~30 seconds, honestly

Install the skill
```
$ npx slingit install-skill
```
Adds /slingit to Claude Code and teaches Codex the same trick.
Sling it mid-session
```
> /slingit you@example.com
```
Claude packs up the result and slings it — the CLI encrypts locally, then emails you the link. No copy-paste.
Open it anywhere
```
https://slingit.dev/aB3xK9…#key
```
You get a link (and an email). It reads beautifully on a phone.

Why people like it

the important stuff, on sticky notes →

Readable, not raw

Markdown becomes a clean, typeset page — headings, tables, highlighted code — not a wall of text pasted into chat.

One link, one reader

Every note gets its own unique link. Only someone holding the link can open the note.

Encrypted end-to-end

The key travels after the # in the link and never reaches the server. Your note sits encrypted on Cloudflare.

Inbox included

Add an email address and the note lands there too — same link, ready to forward.

What people sling

Anything worth reading somewhere other than a terminal.

Claude CodeShow a teammate what Claude found

Three-hour debugging session, one root cause. /slingit anna@team.com and she reads the full write-up — no screenshots, no pasted walls of text.

On the goRead the answer on the bus

Ask for a summary before you leave — “sling this to my email”. The link opens on your phone as a clean, legible page.

CodexCodex slings it too

Same CLI underneath, works from any agent or script:

npx slingit shot review.md \
  --mailto you@example.com --from "Codex"

Team reviewLet people comment right on the page

Select a line and a comment box pops up right there, quoting your selection — or leave a note for the whole document. No login, no separate thread: replies live on the same link, encrypted like the note itself.

Any terminalPull the note — and the feedback — back in

Anyone holding the link can comment, no account either side. Bring it all into your next session, or skip straight to just the replies:

npx slingit pull https://slingit.dev/aB3xK9…#key --comments-only

Not just emailSlack it, don't just email it

The link is the whole delivery mechanism — no integration required. Skip --mailto, copy the link SlingIT prints (or add --copy), and paste it straight into Slack, a PR, a ticket — wherever the conversation already is.

Why it's safe

Built so you can sling something sensitive and still sleep well.

No one can peek — not even us

Notes are encrypted on your machine (AES-256-GCM) before anything is uploaded. The key travels after the # in the link — a part of the URL browsers never send to any server — so all that ever reaches storage is ciphertext nobody can open without your link.

The link can't be guessed

Every note lives at a random address with around 70 quintillion possibilities, paired with its own 256-bit key. There's no directory, feed, or search to browse — without the exact link there's nothing to find, and guessing one just isn't realistic.

You decide who, and for how long

A note goes only where you send its link — to one inbox or a whole channel, your call. Give it an expiry (--expire 7) and after seven days it's deleted from the server automatically, comments included. Gone means gone.

the full fine print lives in the privacy policy below