In DataMind Oda, a chat can be shared with colleagues as a read-only copy, and it can hold more than one version: when you edit, rewind or retry a message, Oda cuts a branch and keeps the earlier path. This page covers both; the deeper mechanics are linked where they live.
A chat can be shared with colleagues in your company as a read-only copy, and a share does not follow the chat on its own. Share DataMind Oda chats covers the Share… dialog, the files that travel with a copy, and how to update or stop a share.
They find the chat under Shared with me in their sidebar and open a read-only view, marked Read-only. There they can read the conversation with its charts, images and pages, download a file, or choose Open in browser. A file row's Download {name} button confirms with Saved to {path}, or fails with Could not download {name}..
To carry the work on, a reader chooses Continue in my Oda. Oda copies the chat with its files into a folder they choose: their current workspace (Current workspace · {name}), another of their workspaces, or Choose folder…. While it prepares the copy, the button reads Starting…; if some files cannot be saved, Oda names them, Some files could not be saved: {names}, and a copy that cannot be made at all reads Could not continue the conversation.. The shared copy and your chat stay as they are. Shared with me is the full guide for the reader's side.
When you change something in a chat's past, Oda cuts a new version and keeps the earlier path. Three actions do this, and / is the command form:
The actions stay hidden while a reply runs, and a failure reads The new version could not be created: {message}. When a message has several versions, a ‹ n/m › switcher appears on it: Previous version and Next version step between them, and it names the one you are on, for example Version 2 of 3. The switcher is disabled at the ends and while a reply runs (its tooltip reads Stop the running reply first). The chat stays one chat in the sidebar, with a small branch glyph whose tooltip counts its versions, for example 3 versions. Conversation branches has the full story, and the conversation map draws the whole tree.
A rewind can also put back the files Oda changed after the message: the Rewind to this message dialog carries the choice Restore files Oda changed after this message ({count}), on by default. Only files Oda itself wrote or edited can come back; changes made by shell commands, memory, skills and scheduled tasks, and files changed outside Oda, are not restored. Rewind and restore files covers the detail.
Separate from versions, the actions on a message offer Branch into a new conversation: it starts a new chat of its own that carries the conversation up to that point. Your follow-up work continues in the new chat, and the original never sees it. The action is described with the rest of the message actions on Actions on a message.
Sharing needs the Share DataMind Oda Chats permission, and it is offered in the DataMind Oda desktop app and the VS Code extension. Without the permission the Share… entries do not appear; if a share is refused anyway, Oda reads Your account is not allowed to share conversations. Your administrator sets the permission on your role; Manage DataMind Oda for your company explains how.
A read-only copy under Shared with me in their sidebar, marked Read-only. They can read the conversation, download its files, open it in a browser, and continue it in their own Oda; they cannot change the copy, and anything they do in a continued copy stays theirs.
Yes. Open Share… again and choose Update share: the copy is replaced with the chat's newer messages and files. Until then the share keeps the content from when it was shared or last updated.
Yes. Open Share… and choose Stop sharing: access ends for everyone and the link stops working. Your chat and files stay as they are, and you can share the chat again later.
Under Include files generated in this conversation, the dialog lists the files Oda created or changed in the chat; they start unticked, and only the ones you tick travel with the copy. Add file… adds a file the list misses. The dialog checks the selection as you pick and holds Share back until the list fits the share's limits.
Their own chat: Oda copies the conversation and the shared files into a folder they choose and opens it for them. Your chat, your files and the share stay as they are.
Edit, Rewind to here and Retry, or the / command. Each cuts a version that continues from just before the message you changed, and the earlier path stays reachable from the switcher and the map.
In the same chat. Move between them with the ‹ n/m › switcher on the message, or open the conversation map; the sidebar keeps one row for the whole chat, with a branch glyph that counts the versions.
Only if you keep Restore files Oda changed after this message ({count}) ticked in the rewind dialog, and only for files Oda itself wrote or edited. Changes made by shell commands, memory, skills and scheduled tasks, and files changed outside Oda, are not restored.
No. Branch into a new conversation starts a separate chat that carries the conversation up to that point; what you do next happens only in the new chat. For another version of the same chat, use Edit, Rewind to here or Retry instead.