Sharing results

A finished task has a Share button. It copies a read-only link that anyone can open without an Else account.

Two things about that link surprise people, so they go first:

1. The files are not in it. Whatever the run produced and you downloaded is yours only. A recipient sees the run, not the deliverables.
2. There is no way to turn the link off. Once created, treat it as permanent. This is a genuine gap, not a policy — the last section says what to do about it.

What the recipient sees

The published view is built from a fixed list of fields rather than by hiding things, so it cannot quietly grow. What is on that list:

• Your original prompt, in full.
• The title of the run.
• Its state — done, couldn’t finish, and so on.
• Every step: its name, its description, its state, and its written output.
• The final written answer.
• The error, if it ended in one.
• What the run cost, both the total and the cost of each individual step.
• When it was created and last updated.

What it leaves out

• The files it produced. The file list itself is withheld too, not just the downloads — filenames carry context of their own.
• Who you are. No account, no name, no email.
• Your spend limit for that run. The recipient sees what it cost, never the ceiling you had set.
• Which engine ran it.
• How the run was configured — which abilities were switched on, your approval setting, whether you asked it to plan first.
• Any question it stopped to ask you, and any conversation the run is linked to.

Shared pages also carry a noindex instruction, so search engines are asked to stay out. That is a request to crawlers, not a lock — as the Privacy Policy notes, it cannot recall copies or screenshots someone takes while a link is live.

Read the steps before you send

The cost being public is a deliberate design choice, and it is the item most worth pausing on: the total and the per-step figures travel with the link. Price on its own is not very meaningful without knowing which tier the run used — and the tier is one of the things a share link withholds — so a recipient sees a number without its context. See Model prices if you need the actual rates.

The other thing worth a glance is the step outputs. Those are the raw written results of each step, not a summary, and they can be more candid than the final answer — including the run’s own notes about what it could not do. That is usually the point of sharing a run. Just look before you send rather than after.

What to use it for, and what not to

Good uses. Showing a colleague how a result was arrived at. Getting a second opinion on the reasoning rather than the artefact. Recording what you asked for.

Not this. Delivering a document. If someone needs the spreadsheet, the deck or the PDF, download it and send the file — the link will never hand it over, no matter what the recipient does.

Not a website, either. A site the agent builds arrives as files you open locally. There is no hosted address, and a share link does not create one.

You cannot revoke a link

There is no “stop sharing” control in the product today. The ability to kill a link exists on our side, but nothing in the interface reaches it, so from where you are sitting a link you created stays live.

Two consequences, and they are the reason this page exists:

• Decide before you click Share, not after. There is no undoing it yourself.
• If you need a link killed, email hello@elsedoes.com with the run and we will do it. That is a manual request, and we are not going to describe it as a feature.

The Privacy Policy describes revoking a share link as something you can do. On the product side that control has not shipped yet, and this page is the accurate one until it does.