@_asperanders@petergyang Yes, it's actually the reason we're building - auth is at the core of what we do at https://t.co/FEdHJfK0V6 - all URLs are behind company auth by default (either Google/Microsoft SSO or OTP). Are you thinking about some additional auth methods?
The /slides skill by @petergyang is the best way to create a presentation �� templates and use cases all built in.
Once you've created a presentation, you can share it with a permanent URL using https://t.co/FEdHJfK0V6 either publicly or behind secure company auth.
See here.
/slides is such a great skill. Just created a beautiful product deck for @slashdisplay in just minutes – it looks amazing from the get-go.
The deck: https://t.co/57Nu2irzG0
@zarazhangrui if you're ever in need of a solution to easily host and share that html deck (directly from your agent) - passwords/SSO and audit logs going then look no further than https://t.co/FEdHJfK0V6
Big update shipped to the way we render Markdown, supporting Markdown Experience Guidelines (MDXG)
Published .mds now have:
• footnotes
• math formulas
• mermaid diagrams
• virtual pages
• search
Check out an example:
https://t.co/ugfKGFWEQa
Introducing the public agent skill for @slashdisplay - https://t.co/rwKrCGGf4f
Permanent URLs for your agent artifacts.
Publish HTML or Markdown behind company authentication from your AI assistant. Works across Claude Code, Cursor, Codex, OpenCode, Hermes, Pi, and OpenClaw.
A few more things it handles:
› Stats and audit logs – View counts per artifact, plus audit logs of exactly who accessed what.
› Unlimited viewers at every tier, no per-seat cliff
› Publish anonymously with curl, claim the URL later
Free signup -> https://t.co/FEdHJfK0V6
Introducing https://t.co/FEdHJfK0V6 – the gated publishing engine for agent-built artifacts.
Your agent makes beautiful HTML docs. One command puts it behind your company's SSO at a permanent URL.
$ dsp publish ./report.html
Comments make the artifacts a collaboration tool.
› Teammates leave inline comments.
› The agent reads them natively, edits the file, resolves the thread, republishes at the same URL.
No more copy-pasting feedback into chat. The artifact stays alive.