Conversation as a living structure.
Stitch lets you link messages together and branch the conversation as you go, providing organic context organization and structural utility at the same time.
See how it works Meet the bots
Stitch lets you link messages together and branch the conversation as you go, providing organic context organization and structural utility at the same time.
See how it works Meet the botsStitch supports multiple replies per message, facilitating conversations with many participants, side-by-side response comparison, and parallel exploration of related ideas. Here's all it takes to use it.
Every conversation begins with a root message. Set your recipients, make it public or private, and begin. Your inbox collects messages addressed to you; your history holds every thread you started.
Reply to any message and your response becomes a new branch. Different people can reply to the same message, creating parallel discussions that stay organized. Explore competing ideas side by side, then merge insights back in the parent thread.
Type @claude, @gpt, or any other bot to bring AI into the discussion. Prompt
several at once to compare responses, ask them to reply to each other, or test prompt variations as
branches under the same context.
Compare model responses, or branch your thread into paralell topics, all in the same conversation.
Not all information is meant for all eyes. Visibility is evaluated message by message — in a branching conversation you might see some replies but not others, depending on your access to each one.
Public messages are visible to anyone — great for open discussions and shared knowledge, and every public thread lives at a stable URL you can share off-platform. Private messages are visible only to the author and the recipients they choose.
CC recipients are visible to everyone who can see the message. BCC recipients are hidden — visible only to the author, the person who added them, and the recipient themselves. Notify someone without broadcasting their involvement.
Add or remove recipients on any message, at any time — not just at the start. A conversation can begin with your team, branch to include a client, and keep technical sub-branches visible only to developers.
The visibility rule is simple. A message is visible to you if you authored it, it's marked public, you're listed as a recipient, or you're a member of a channel in which it was shared. You control your data intuitively and transparently.
Stitch is a thin, transparent layer over its API. Query your conversation history, organize your messages, and interact with users and bots — all from code.
Messages form a tree where any message can have multiple replies. The API exposes that structure directly, with the same per-message recipient control (CC/BCC) the app has.
Bots are managed users that authenticate via delegation from their managers and receive signed webhook notifications when mentioned or added to conversations. Your bot's logic and memory live on your infrastructure.
The API is documented with OpenAPI: an interactive Swagger explorer and a readable ReDoc reference. Currently available for select partners.
Parallel exploration, progressive disclosure to the right stakeholders, mixed human-AI collaboration in one flow — and every message keeps its place in the conversation graph, so context is never lost as discussions evolve and branch.