Introducing shared chats and How this was made

Shipping with an agent is usually the easy part. Explaining what happened is harder. You send a link to a polished page, and five minutes later someone asks how you got there. The prompts, the dead ends, the file edits: all of that stayed in a chat window they cannot see.

We tried the usual workarounds. Screenshots of chat are messy. Pastebins are public by default. Dropping a JSONL into a ticket puts the story next to the work instead of with it. The transcript should live on the same URL as the artifact, with the same permissions.

That is what shared chats do. Dropway already turns a folder into a live, access controlled URL. Now the conversation behind the build can go with it, either in the org library or as a How this was made panel on the site.

A chat log is just an org object: a transcript you import or keep adding to. Messages are normal turns, or short action notes (like a file edit with a one line comment). A log can sit in the library on its own, or attach to one site.

Free keeps the last 10 messages per log. Pro goes to 100. Business and Enterprise are uncapped. You can create logs on every plan.

Go to Chats, then Share a conversation. Paste or upload an export, optionally pick a site, and you are done. If it is attached, the site gets a How this was made control that opens the transcript.

You can attach, detach, or move a log later without copying anything. Owners and admins can also turn shared chat logs off for the whole org in Settings if you need to pause the feature.

dropway chat share publishes an export. Add --site to attach it right away, and --derive-actions if you want tool activity turned into short action rows.

dropway chat share ./session.jsonl --site my-docs --source claude_code
dropway chat share ./session.jsonl --site my-docs --derive-actions

As you keep working, dropway chat append adds messages or actions by chat id or by --site.

dropway chat append --site my-docs --message "Reworked the hero copy"
dropway chat append --site my-docs --action file_edit --path index.html --comment "Tightened the headline"

You will also use list, show, attach, detach, and panel (to toggle the served panel without deleting the log).

Over MCP you get share_chat, append_chat, and get_site_chat. An assistant can save the session while it works, attach it to a site, and keep adding turns or action notes so the panel stays up to date.

In practice that means you can build, deploy, and share the transcript without leaving Cursor, Claude, or Codex.

On an attached site, viewers get a How this was made control. It opens the transcript on the same host, so the site’s access rules apply automatically. Logs that are only in the library stay private to the org until you attach them.

Next time you deploy something worth sharing, attach the session too. One link for the page and the story behind it.