Log in

Documents agents can ship

Slideless

Your agent writes the page. Slideless hosts it, versions it, and hands you a link for each person you send it to.

Open Slideless Read the documentation slideless.ai

How it works

A folder in, a link out, and everything that happens on it kept.

  1. 01 One command

    Your agent pushes a folder. It comes back as a link.

    A deck is a folder of HTML: a presentation, a report, a plan, a small app. Your agent writes it and runs one command, from the CLI, over MCP, or with an API key. The first push creates the deck in your workspace; every later push is a new version, and only what changed travels.

  2. 02 Hosted and versioned

    Every version is kept. Nothing is lost by moving forward.

    Versions are numbered and immutable. The deck page shows its history with live thumbnails, and any version can be pulled back byte for byte. Attachments travel with the version they belong to.

  3. 03 Share links

    Each recipient gets a link of their own, and you see it open.

    A share link is a door into the deck: it follows the latest version or stays pinned to one, expires when you say, can ask for a password, and counts its opens without ever storing who. Revoke it and it dies. A deck with no link is private.

  4. 04 Forms and files

    The page can ask questions, and the answers come back to you.

    Mark a form in your HTML and the link serves it live: answers and uploaded files land with the deck, every edit kept, and a named link remembers its respondent. Annotator links let a reviewer leave notes anchored to the page, no account needed.

One deck, many doors

One artefact, every version of it kept, and a separate door for each person you send it to.

Each door can follow the latest version or stay pinned to one, expire, ask for a password, and be revoked. What comes back through it, an open, an answer, a note, lands on the deck it belongs to.

Your agent push The deck, every version kept v1 v2 v3 One link each Marie The client A reviewer Opens Answers Notes and all of it comes back to the deck

What it does

The whole of it, in the product’s own words.

  • The artefact

    What an agent produced, kept as HTML with its whole history.

    • Versions Immutable and numbered. Pull any one back, browse the history on the deck page, keep the attachments that shipped with it.
    • Built for agents A CLI, an MCP endpoint on every instance behind its own OAuth server, scoped API keys, and an AGENT.md briefing per deck.
    • Embedding One script renders a link inline on your own site, with a placement label so you know which page opened it.

  • The way out to a person

    One link per recipient, and everything they do on it comes home.

    • Share links Per recipient, following the latest version or pinned to one, with expiry, a password, opens and last-opened counts, and instant revocation.
    • Forms and file fields Any form in the page is served live; responses and uploaded files stay with the deck, downloadable one by one or as a zip.
    • Annotations Reviewer links let anyone leave a note on a passage, a spot or a region. The notes reach the owner’s inbox.
    • Link analytics One event per open: when, from which site, which placement, which browser family. Never an IP address, a location or a full URL.

  • The workspace around it

    Who may push, who may read, and what you take with you.

    • Collaborators Grant an outside person the right to push new versions of one deck, and nothing else.
    • Workspace admin People and invitations, API keys, files, an audit log of every privileged action, and a full export of the workspace as a zip.

Who it is for

People who run agents

Hand the work to a human

Claude Code, an MCP client, a CI job: whatever produces the page, Slideless is where it becomes a URL someone can open, forward and answer.

Studios and consultancies

Send decks, collect answers

Client-facing decks and dossiers with a link per recipient, opens you can see, and forms that bring the documents you asked for back to the deck.

Teams on their own infrastructure

Keep it on your side

One Docker image and a Postgres. A self-hosted instance never phones home, and the source is yours to read.

Where it came from

One small question, with large consequences.

Slideless answers one small question: when your agent finishes a piece of work, how does it hand you something you can share?

Its answer is a page and a link. The agent writes the deck, the memo, the dashboard; Slideless hosts it, versions it, and the link is yours to send. A colleague opens it, a client answers the form on it, a reviewer leaves a note on it, and all of that comes back to the deck.

Slides were only the first shape. What Slideless really keeps is the artefact an agent produces, as HTML, with its history, and we think a new kind of software gets built on pages like these.

A photogram of three lantern slides fanned from one corner, a strip of film and a luggage tag, toned sepia.
The photogram Three slides from one corner, and a tag for whoever it goes to.

Open, on your terms

Source available. Self-host it, or let us run it.

Slideless is fair-code under the Sustainable Use License: the source is public, self-hosting is free for your own use, and it may not be resold or hosted for others. The cloud edition at slideless.antasphere.com is operated by us, on your Antasphere account, so one login opens it with every other tool of the fleet.

Send a message

Your name, email address and message are stored so we can answer you, are used for nothing else, and are deleted automatically after 90 days. What happens to your message