Skip to content

[Docs] Document token analytics and task recovery - #2439

Draft
roomote-community[bot] wants to merge 1 commit into
developfrom
feature/docs-audit-38itvwt69y5ak
Draft

[Docs] Document token analytics and task recovery#2439
roomote-community[bot] wants to merge 1 commit into
developfrom
feature/docs-audit-38itvwt69y5ak

Conversation

@roomote-community

Copy link
Copy Markdown
Contributor

​Opened on behalf of @mrubens. Follow up by mentioning @roomote, in the web UI, or in Discord.

What changed

  • document token totals, chart behavior, detail rows, exports, and missing provider metadata in Cost Analytics
  • explain that stopping a task preserves resumable work while an explicit cancellation ends the current run
  • state that Snowflake requires key-pair authentication and existing password- or token-based connections must rotate

The audit inspected all 37 first-parent merges on develop in the exact 24-hour window from 2026-09-09T03:00:45.879Z through 2026-09-10T03:00:45.879Z. Existing Agent Guidance, bounded monitoring, native charts, Blank slate, scheduling, and source-control provider documentation already matched shipped behavior and were left unchanged.

Why this change was made

Recent product changes added user-visible analytics data and changed task recovery and Snowflake authentication boundaries without fully updating their public workflow guidance.

Impact

Users and operators can now interpret token usage, choose between resumable stopping and permanent cancellation, and migrate Snowflake credentials correctly. Mintlify validation and broken-link checking passed. Rendered screenshots are unavailable because the local Mintlify preview returned an internal error for missing generated Next.js artifacts; no visual proof is claimed.

@roomote-community

roomote-community Bot commented Sep 10, 2026

Copy link
Copy Markdown
Contributor Author

1 issue outstanding. See task

  • apps/docs/fast-sessions.mdx:120 Stop is documented as resumable, but the Session-card control performs terminal cancellation.

Reviewed aa01b94

requires execution access and stops the displayed task run without stopping the
parent Session or sibling tasks. Cancellation errors appear on the card; check
the resulting task status rather than assuming the request succeeded.
parent Session or sibling tasks. Stop preserves the task's sandbox, work, and

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.

The visible Session-card Stop control currently calls cancelTaskRunCommand with a run ID, and that path passes terminate: true to stopTaskRun. This is a terminal cancellation that shuts down the sandbox, so a later message cannot resume the stopped run as documented. Either make that control use the soft-stop path or describe Stop as terminal.

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.

1 participant