Work together without sharing unfinished drafts
Understand what your team can see and how drafts stay with you.
What your project shares
All project members can read its sent messages, shared context, bookmarks, and shared files. A chat belongs to its project; it is not a private direct message to Steward.
Your unsent message and its draft attachments are private to you. They become part of the shared project when you send them.
Leave and return to a draft
Contributors and managers can type an unsent message in the composer. Steward saves drafts quietly for your account, project, and chat, without a save-status indicator. You can switch chats and return to your unfinished text. A new-chat draft stays with its project until you submit the first message.
Let an upload finish before sending. If saving or uploading fails, read the composer’s message and use its retry action. Keep the tab open until unsynced work is safely saved.
Resolve a draft conflict
If the same draft changed on another device, Steward keeps your local text and shows a choice. Select Keep this version to use the version in front of you, or Use saved version to use the saved version.
Read both versions before choosing, especially if you worked on the draft in another tab. A conflict does not silently send your text.
Correct a sent message
Send a follow-up message to clarify or correct a submitted request. If Steward is still working on your run, your message guides that active run; see guide a run. Sent messages have no edit control. A follow-up does not undo business actions already taken, so explain any correction or next action clearly.
Keep shared work understandable
Use one chat for a continuing question and another for a separate topic. Steward generates a recognizable title after your first message. Bookmark important decisions and put reusable project guidance in shared context.