// slideless

Your agent made it.
Now share it.

Claude built the artifact. The hard part is getting it in front of someone who is not you, on a link that does not break.

01 / 06

// the problem

The artifact link breaks

Tied to the conversation. Private chat, deleted chat, or a viewer without access → it does not load.
It can expose your chat. A shared conversation shows the conversation, not just the deck.
No tracking, no history. You cannot see who opened it, and unpublishing is a permanent wipe.

02 / 06

// the fix

Slideless serves the exact HTML Claude wrote, on its own durable URL. No rebuild, no git repo, no design tool.

$ slideless push ./deck.html --title "My deck"

✓ Presentation pushed · Share ID: 0192f1c3-…

$ slideless share 0192f1c3-…

✓ https://app.slideless.ai/share/0192f1c3-…?token=…

03 / 06

// signup

No password to invent. The agent reads the 6-digit code from your inbox and you are in.

$ slideless auth signup-request --email you@example.com

→ 6-digit code sent to your inbox

$ slideless auth signup-complete --code 123456 --first-name "Alex"

✓ Signup complete

04 / 06

// artifact vs slideless

05 / 06

// this deck

[ you are looking at one ]

An agent wrote this HTML. One command put it on a permanent URL, embedded right inside the article you are reading.

06 / 06