01
Resume where the team left off
Shared threads keep the transcript available to people who need the context.
Shared threadsConversations
What are Conversations in Tale?
Conversations are the shared threads your team resumes — history, handoffs, and context that outlive a single session so work does not restart from a blank composer.
How shared conversations work
Compare models, resume grounded threads, scope by project, and approve actions that leave the chat.
01 Arena
Compare drafts before you hand off
Shared threads can run the same prompt through two models so the next owner picks the stronger reply — without leaving the conversation.
02 Projects
Threads belong to workspaces
Projects decide which members see which threads — support escalations stay out of engineering.
03 Approvals
Approve from inside the thread
When a conversation would send mail or change a system, the approval card lands where the work already is.
04 Knowledge
Ground shared replies in the same libraries
Everyone in the thread sees the same citations — no private context that the next reader cannot check.
Why shared threads matter
Threads your whole team can pick up — with history, handoffs, and governance that travel with the conversation.
02
Handoffs without copy-paste
Pass a thread to a specialist agent or teammate without losing citations and tool history.
Agents in chat03
History you can search
Open Show chats to list every thread you can resume — and search across the history.
Chat overview04
Governance stays attached
Approval cards and their resolved state remain in the transcript as a record of what was allowed.
05
Projects when work grows
When a thread becomes a tracked body of work, Projects carry files, agents, and backlog beside the conversation.
Projects overview
Conversations FAQ
Tale Conversations are shared chat threads your team can resume, with history, handoffs, and attached approval records.
Chat is the everyday composer surface. Conversations names the shared, durable thread layer teams hand off and resume.
Yes. A shared thread keeps its full history, so a person or a specialist agent can pick it up without losing context — and governance stays attached to every action.
No — projects scope who sees what. A thread lives in its workspace, and only that workspace's members can read or resume it.
See Tale on your stack
Book a guided demo or talk to the team about self-hosted deployment, pricing, and hardware.