Skip to content

🤖 perf: document Report slowness and synthetic tape replay on the Profiling Xum page - #5625

Merged
ThomasK33 merged 2 commits into
mainfrom
perf/docs-report-and-replay
Oct 4, 2026
Merged

ThomasK33 merged 2 commits into
mainfrom
perf/docs-report-and-replay

Conversation

@ThomasK33

Copy link
Copy Markdown
Member

Summary

Documents two merged perf features on the Profiling Xum page (docs/reference/profiling.mdx), and fixes one wrong runtime message.

  1. Report slowness (🤖 perf: "Report slowness" local diagnostics bundle (F4) #5558): a new ## Report slowness section.
    • How to run it: the palette command, a link to its shortcut on the keyboard shortcuts page, and xum api perf-reports create.
    • Where the report goes: ~/.xum/perf/reports/<id>/.
    • A table of every file in the report: snapshot.json, trace.json, environment.json, README.txt, captures/ with manifest.json, hangs.json and app-metrics.json. The last two are desktop only.
    • What it never contains: tapes, chat content, prompts, tool payloads or environment variables.
    • A warning that path redaction is partial, not anonymization: copied CPU profiles keep the folder names below ~ (🤖 perf: F4 "Report slowness" sanitizer follow-ups #5561).
    • The "Report a performance problem" checklist now starts with this report.
    • docs/config/keybinds.mdx keeps the shortcut and links here, so each fact has one home.
  2. Tape replay (🤖 perf: replay synthetic session tapes through the desktop app with egress blocked (T3) #5612): a new "Replay a synthetic tape (contributors)" subsection.
    • What make perf-tape-replay runs and where its output goes.
    • It replays only synthetic fixtures. A warning says never to replay or commit real tapes.
    • An accordion explains how replay stays offline. Replay runs only when XUM_E2E=1 and XUM_REPLAY_HARNESS=1 are set, and the test harness sets them, not the Makefile. The app blocks renderer requests, while the harness takes background network offline. Tape paths are checked for absolute local syntax only: .. and symlinks are accepted.
  3. Refusal message (sessionTapeReplaySource.ts): it now says "Run make perf-tape-replay to use the isolated replay harness." The old text claimed the make target sets the markers. The existing test matches only /only inside the perf harness/, which is unchanged, so this PR adds no exact-copy test.

Validation

  • I ran the documented commands against a sandbox xum server with a temporary XUM_ROOT:
    • perf-reports create with the experiment off fails with PRECONDITION_FAILED and the documented message.
    • With the experiment on, it writes the documented layout: README.txt, captures/ with manifest.json, environment.json, snapshot.json and trace.json. Folders are 0700 and files 0600.
    • The environment.json keys match the page, and the home path appears nowhere in the bundle.
    • Two concurrent runs get CONFLICT with "a slowness report is already being written".
  • I rendered the page locally with the CI-pinned Mintlify and checked the new sections at desktop and 390 px widths. Both accordions expand.
  • make static-check-full passes, including mintlify broken-links. sessionTapeReplaySource.test.ts passes (25 tests).

Report slowness privacy warning and checklist, desktop

Report contents table at 390 px

Tape replay subsection with the offline accordion expanded, desktop


Generated with xum • Model: anthropic:claude-opus-5-5 • Thinking: high • Cost: $30.02

…ss markers

The E2E fixture sets XUM_E2E and the replay spec sets XUM_REPLAY_HARNESS.
The refusal now points to make perf-tape-replay without naming the variables.
Adds a Report slowness section (bundle contents, limits, partial path
redaction), a contributor section for make perf-tape-replay, and makes
the report the first item of the performance issue checklist. The
keybinds page links to the profiling page instead of repeating it.
@mintlify

mintlify Bot commented Oct 4, 2026 •

Copy link
Copy Markdown

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated
Mux 🟢 Ready View Preview Oct 4, 2026, 4:27 PM

💡 Tip: Enable Automations to automatically generate PRs for you.

@ThomasK33

Copy link
Copy Markdown
Member Author

@codex review

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 4, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-04T16:29:43.080418Z 638fbc5 Manual request
🔒 Security Review ✅ Completed 2026-10-04T16:32:44.464246Z 638fbc5 Manual request
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. More of your lovely PRs please.

Reviewed commit: 638fbc580d

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@chatgpt-codex-connector

Copy link
Copy Markdown

🛡️ Codex Security Review · Automatically triggered

Security review completed. No security issues were found in this pull request.

Reviewed commit: 638fbc580d

View security finding report

Only the user who started this review can view the report in Codex.

ℹ️ About Codex security reviews in GitHub

This is an experimental Codex feature. Security reviews are triggered when:

  • You comment "@codex security review"
  • A regular code review gets triggered (for example, "@codex review" or when a PR is opened), and you’re opted in so security review runs alongside code review

Once complete, Codex will leave suggestions, or a comment if no findings are found.

@ThomasK33
ThomasK33 added this pull request to the merge queue Oct 4, 2026
Merged via the queue into main with commit a4ddcec Oct 4, 2026
58 of 61 checks passed
@ThomasK33
ThomasK33 deleted the perf/docs-report-and-replay branch October 4, 2026 16:57

This branch was successfully deployed

1 active deployment
staging - docs — 638fbc58 Deployed Oct 4, 2026 by mintlify[bot]
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