Share your work — or organize it first Krater gives you three ways to share: invite people into a live conversation or project, publish a read only public link, or put a /build artifact on the web ...
Krater gives you three ways to share: invite people into a live conversation or project, publish a read-only public link, or put a /build artifact on the web as a real site. Projects — the folders in your sidebar — keep related chats, files and instructions together, and you can share a whole project at once.
Open the chat, then Share (from the chat menu or the header). You have three options.
krater.ai/shared/... URL. Anyone you give the link can join.Both require a Krater account — invitees sign in (or sign up) to accept. There are two permission levels:
| Level | What they can do |
|---|---|
| Can view | Read the whole conversation. No replies. |
| Can edit | Read, plus post their own messages. |
The People with access list shows everyone, including pending invites — change a level or remove access anytime. Shared chats appear in the recipient’s sidebar with your avatar; they can leave whenever they want.
Flip Public link on to create a read-only snapshot at krater.ai/view/<code>. Anyone with the URL can read it — no account needed.
noindex, but treat the URL as public: anyone who has it can read.On your own chats, the share action on any assistant message publishes a public link that ends at that message — everything after it stays private. Shared-answer links are listed under Link access and can be revoked individually.
If you’re in a team, the same dialog can attach the conversation to it — all members can view and reply. More in Teams.
Projects are the folders in your sidebar. Click New project, name it, pick an icon and color — or start from a preset like Work, Coding or Travel — then:
Open a project and the knowledge panel sits on the right. Everything in it is automatically available to every chat in the project:
Deleting a project removes the project and its memories. Chats are moved out, not deleted.
Open the project → Share. Same model as conversations: email invites or an invite link (krater.ai/project-shared/...), each Can view or Can edit.
krater.ai/share/<code> page. Krater stores a durable copy so the link outlives chat retention; revoke it anytime.krater.ai/f/<code> page with preview and download.A /build artifact can go live on the web, not just in a link. Open it in Studio → Publish, pick a slug, done — your site is live at <slug>.krater.site.
| Plan | Live sites | Custom domains |
|---|---|---|
| Ultra | 2 | 2 |
| Max | 5 | 5 |
/keep/sites/<id>): visit analytics, custom domains, password protection, hide-from-search, removing the “Built with Krater” badge, unpublish or delete.The command itself: /build.
| What you share | URL looks like | Sign-in needed | What they get |
|---|---|---|---|
| Conversation (member) | krater.ai/shared/… |
Yes | Live chat — view or reply |
| Conversation (public) | krater.ai/view/… |
No | Read-only snapshot |
| Single answer | krater.ai/view/… |
No | Snapshot ending at that message |
| Project | krater.ai/project-shared/… |
Yes | All chats, files, memory |
| Generated media | krater.ai/share/… |
No | One media page |
| Keep file | krater.ai/f/… |
No | Preview + download |
| Published site | <slug>.krater.site |
No | Live website |