Temporary shares
slew share publishes a throwaway page to an expiring URL — no project, no
setup, no cleanup. It exists for pages that don't deserve a project: an HTML
plan a coding agent just wrote, a one-off report, a prototype for a colleague.
slew share plan.html
slew ──┐ sharing plan.html
└────
Shared 1 file at https://quiet-harbor-lantern.slew.cloud
Expires Fri, 17 Jul 2026 22:01:36 GMT.
Usage
| Command | Effect |
|---|---|
slew share <file> |
Publish a single file, served as index.html at / |
slew share <directory> |
Publish a whole static build |
slew share <path> --ttl <days> |
Expire after 1–30 days (default 7) |
slew share <path> --password <pw> |
Gate the share behind a password |
slew share <path> --feedback |
Let readers comment on the page (see Feedback) |
slew shares |
List your live shares with their expiry and open comment counts |
slew shares comments <name-or-url> |
Read the comments readers left (--all includes resolved ones) |
slew shares resolve <name-or-url> <comment-id|all> |
Mark feedback as handled |
slew shares rm <name-or-url> |
Delete a share now — the URL stops serving immediately |
A share behaves like any deployed site — CDN, TLS, immutable asset caching —
until it expires. Expired shares stop serving immediately and a background
reaper deletes their files and records within the hour. There is nothing to
clean up manually — but if a page should disappear sooner than its TTL,
delete it with slew shares rm (the URL or the three-word name both work)
or the Delete button in the web console.
Feedback
A share is usually something you want a reaction to — a technical design, a
plan an agent wrote, a draft. --feedback puts a small comment widget on
every page of the share:
slew share design.html --feedback
Shared 1 file at https://quiet-harbor-lantern.slew.cloud
Feedback is on — readers can select text and comment. Read it with 'slew shares comments quiet-harbor-lantern'.
Expires Fri, 17 Jul 2026 22:01:36 GMT.
Readers select any passage and a Comment button appears; the note is attached to that text and shows up as a numbered highlight. General notes go in the panel behind the button in the corner. Nobody signs in — a name is optional and remembered in the browser — so the URL is the invitation, and everyone who can read the page can read its comments. Password-protected shares keep feedback behind the same unlock screen.
Then read it back where the page was written:
slew shares comments quiet-harbor-lantern
3 open comments on https://quiet-harbor-lantern.slew.cloud
1. cmt_7Hk… — Hessel · 01/09/2026, 15:02:11 · § Migration
> run the backfill in one transaction
This will lock the table for minutes — batch it.
2. cmt_9Qz… — Hessel · 01/09/2026, 15:04:40
Missing: what happens to in-flight jobs during the cutover?
…
Resolve one with 'slew shares resolve quiet-harbor-lantern <comment-id>' (or 'all').
Each comment carries the quoted passage and the nearest heading, so an agent
can act on it without the page in front of it. Resolve what you've addressed
and the highlight disappears for readers; --all shows resolved notes too.
The Claude connector exposes the same loop as tools:
share_page with feedback: true, then share_comments and
resolve_share_comment.
What is stored: the note, the optional name, the quoted text with a little surrounding context, the heading, and the page path. No IP address, no user agent. Comments are deleted with the share, and a share holds at most 500 open ones; a single reader is limited to 20 comments per ten minutes.
The same comment box works on any site, not just shares: see Client feedback for review links on your projects.
Naming
Shares get generated three-word names like quiet-harbor-lantern.slew.cloud:
easy to read aloud and retype, with enough combinations that a URL is
effectively unlisted. Treat the URL as a shareable link, not a secret — put
nothing on a share that would hurt to leak.
HTTP API
Both endpoints require a CLI token (Authorization: Bearer slew_…).
| Endpoint | Effect |
|---|---|
POST /shares?ttl=<days> |
Body is a tar.gz (Content-Type: application/gzip). Creates the share, uploads, and activates in one request. Returns { deployment_id, url, expires_at }. |
GET /shares |
Your live shares: { shares: [{ name, url, expires_at, feedback, open_comments, … }] }. |
DELETE /shares/:name |
Delete a live share: files and records, effective immediately. |
POST /shares?feedback=1 |
Same upload, with the comment widget on. The response carries feedback: true. |
GET /shares/:name/comments |
{ feedback, url, comments: [{ id, path, url, body, author, quote, section, created_at, resolved_at }] }, oldest first. ?open=1 hides resolved ones. |
PATCH /shares/:name/comments/:id |
Body { "resolved": true | false }. |
DELETE /shares/:name/comments/:id |
Delete one comment. |
Readers post through the share's own hostname (POST /_slew/feedback,
JSON), which is what the widget does; that endpoint exists only on shares
published with feedback on.
Shares never appear in GET /projects — they are a separate surface, and the
web console lists them under Temporary shares.
The agent skill
Coding agents generate HTML plans constantly; the missing piece is a URL you
can open. A ready-made skill teaches Claude Code (or any agent with a skills
directory) to publish pages through slew share whenever you ask for a link.
Install it from the skills registry with the CLI:
slew skill install slew-share --global # → ~/.claude/skills/, every project
Or copy it by hand — a skill is just markdown:
mkdir -p ~/.claude/skills/slew-share
curl -fsSL https://skills.slew.cloud/skills/slew-share/SKILL.md \
-o ~/.claude/skills/slew-share/SKILL.md
From then on, "share this plan" ends with a link like
quiet-harbor-lantern.slew.cloud in the chat. The skill needs the slew
CLI and a login (slew login, or SLEW_TOKEN in CI). Read it before
installing, and browse the other skills, at
skills.slew.cloud.