◈OpenTree DashboardSign in

$ date -I # 2026-07-22

Public sharing, and the default that should have been private

Sharing agent output with someone outside the conversation sounds like flipping a “public” switch. But agent output is assembled from whatever was in context, and context is full of things that should never be public. The default matters more than the switch.

Why public-by-default is the wrong default here

An agent builds a page from query results, customer rows, and occasionally the token that fetched them. Public-by-default assumes the author reviewed every byte for disclosure, which is exactly the assumption an agent breaks. The safe posture is: shareable, but not to the whole internet, and not to a crawler.

What unlisted actually buys

A URL with a 22-character random token — drawn from 62 characters, so on the order of 1039 possibilities. It is not listed, not indexed, and not linked from anywhere. The threat model is not someone guessing it; it is someone the link was forwarded to, which is why the referrer is stripped and the page is noindex.

The gates, when unlisted is not enough

Reach you wantThe control
Anyone with the linkUnlisted token (the default)
Only people with a shared secretset_password
Only one company's staffset_email_gate on a work-email domain
Exactly one open, then goneBurn-after-read
Only for a whileset_expiry, which deletes on expiry

Public, when you really do mean public

Sometimes you do — a demo, a landing page, something you want indexed. That is a deliberate choice you make per link, not a default you forget to turn off. The point is the order: private first, public on purpose.

What a scan catches before it ships

Before the bytes are stored, they are scanned for the shapes of secrets and personal data; a hit blocks the publish unless you override. It is a backstop, not a promise — but it catches the most common way agent output leaks, which is a credential that rode along in the context.

The switch, done right

Publish gets you a private link in one call. Widening its reach is a second, explicit call — a password, a domain, or nothing at all if you truly want it open.

curl -X POST https://read.botook.ai/v1/publish -F file=@index.html

It is private in the sense that matters for sharing: unguessable, unindexed, unlinked. For a hard boundary — only these people — add a password or an email-domain gate on top.

Does the secret scan see my content?

It runs on your own deployment, before storage, and blocks on a hit. Nothing is sent anywhere to scan it; the check is part of the publish path in your account.

Keep reading