Skip to content

[Docs] Sync public guides with shipped behavior - #1829

Merged
mrubens merged 1 commit into
developfrom
feature/sync-public-docs-2kd8yqlxt3k12
Aug 29, 2026
Merged

[Docs] Sync public guides with shipped behavior#1829
mrubens merged 1 commit into
developfrom
feature/sync-public-docs-2kd8yqlxt3k12

Conversation

@roomote-community

Copy link
Copy Markdown
Contributor

​Created by Roomote. View the task or mention @roomote for follow-up asks.

What changed

  • audited the 47 first-parent changes merged to develop during the previous 24 hours against their shipped behavior
  • documented the navigation Session launcher and Fast Session messaging through Roomote MCP
  • clarified the default Memory state for new Roomote Cloud deployments and the current Cost Analytics categories
  • documented how Fast forwards relevant supported attachments to coding tasks

Why this change was made

Several user-facing capabilities shipped without matching public documentation. These focused updates bring the affected guides back in line with the product while leaving internal-only changes and transient UI fixes out of durable docs.

Impact

Users and operators now have accurate guidance for starting Sessions, continuing Fast Sessions through MCP, configuring Memory, interpreting inference costs, and using attachments with Fast-delegated work.

Screenshots

The Sessions guide documents the navigation launcher

The Roomote MCP guide documents Fast Session messaging boundaries

The Memory guide documents the Roomote Cloud setup default

The Cost Analytics guide documents the default view and current types

The file attachments guide documents Fast forwarding

@roomote-community

roomote-community Bot commented Aug 29, 2026

Copy link
Copy Markdown
Contributor Author

1 issue outstanding. See task

  • apps/docs/file-attachments.mdx:16-18 Scope Fast attachment forwarding to the active turn.

Reviewed 1b81984

Comment on lines +16 to +18
Attachments sent to Fast stay available as conversation context. When Fast
delegates work or follows up with a coding task, it can forward the relevant
supported attachments with the instruction.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fast only has attachmentTexts and images from the active turn, and forwards them only when it sets includeAttachments. An attachment from an earlier Fast message is not available to a later delegated-task or follow-up call, so this wording promises a persistent forwarding capability that users cannot rely on. Please scope this to the current turn (or tell users to reattach the file before later delegation).

Suggested change
Attachments sent to Fast stay available as conversation context. When Fast
delegates work or follows up with a coding task, it can forward the relevant
supported attachments with the instruction.
Attachments from the current Fast turn stay available as conversation context.
When Fast delegates work or follows up with a coding task from that turn, it can
forward the relevant supported attachments with the instruction.

@mrubens
mrubens marked this pull request as ready for review August 29, 2026 19:44
@mrubens
mrubens merged commit d022012 into develop Aug 29, 2026
18 of 19 checks passed
@mrubens
mrubens deleted the feature/sync-public-docs-2kd8yqlxt3k12 branch August 29, 2026 19:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants