[khaliqgant]

Summary

• upgrade Next.js from 16.4.0 to the security-fixed 16.4.3 patch release selected by next upgrade --agent=security
• set experimental.agentUpgrade to security so future builds retain security upgrade reminders
• refresh the npm lockfile for the exact Next.js release and its transitive packages

Verification

• npm ci — passed from the workspace root
• npx --workspace web next --version — Next.js v16.4.3
• npm run typecheck — passed
• npm run lint — passed with two pre-existing warnings
• npm test — 50 web files / 568 tests and 11 router files / 118 tests passed
• npm run build — passed; 244 static pages generated
• npm audit --json — no finding for next; 20 unrelated existing dependency findings remain

Duplicate-work check

Checked local and remote branches, commit history, upgrade markers, and all open pull requests before and after the change. No equivalent Next.js 16.4.3 security upgrade was in progress.

---

^{Need help on this PR? Tag @codesmith-bot with what you need.}

---

Summary by cubic

Upgrades Next.js in the web workspace from 16.4.0 to the security-fixed 16.4.3 patch release and relaxes the OpenNext version assertion so the upgrade builds in Cloudflare.

• Pins next to 16.4.3 in web/package.json and updates the OpenNext compatibility check in web/scripts/prepare-opennext.mjs.
• Sets experimental.agentUpgrade to security in web/next.config.mjs so future builds keep security upgrade reminders.
• Refreshes the lockfile: Next.js now nests sharp 0.35.5 and its wasm32 packages, and the previous 0.35.4 sharp becomes dev-only.

Typecheck, lint, tests, and a production build all pass; no next finding in npm audit.

^{Written for commit 036bb5b. Summary will update on new commits.}

---

Agent Relay sessions

• codex session 01a18883 · opened via gh pr create · last active 2026-10-30

[coderabbitai]

Walkthrough

The web project updates its next dependency and the OpenNext preparation script’s version assertion to 16.4.3. It also adds agentUpgrade: 'security' to the Next.js experimental configuration.

Changes: Next security configuration

Layer / File(s)	Summary
Next.js security upgrade web/package.json, web/scripts/prepare-opennext.mjs, web/next.config.mjs	The next dependency and the version assertion change to 16.4.3. The experimental configuration adds agentUpgrade: 'security'.

Priority: Low

Estimated code review effort: 1 (Trivial) | ~5 minutes

Change: Other

Suggested reviewers: willwashburn

Merge Risk: Minimal · up to 036bb

The upgrade configuration is consistent and supported, with no actionable merge-blocking risk identified.

Pre-merge checks: 5

Check name	Status	Explanation
Title check		The title clearly and concisely describes the primary change: upgrading Next.js to version 16.4.3 for security.
Description check		The description directly covers the Next.js security upgrade, configuration change, lockfile refresh, and verification results.
Docstring Coverage		No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Full details: Docstring Coverage

Explanation

No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 2 files.

Finishing Touches

📝 Generate docstrings

• Commit to this branch
• Create a new PR

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{A rabbit checks the version line,
Then adds a setting, neat and fine.
The web config gets its update,
The script now checks the matching state.
Soft paws celebrate the change.}

_{Comment @coderabbitai help to get the list of available commands.}

[composalagent]

Composal Verify · PR #252

Timed out · 40 of 146 scenarios passed · 18 findings · commit 036bb5ba3bd1

Cleanup: Blocked.

Preview: https://b4a23c20-agentrelay-web.agent-workforce.workers.dev/

Findings

1. Not met: Resources shows “Relay Docs” and “RelayFile Docs” · View browser · Fix with agent
   • Expected “Resources shows “Relay Docs” and “RelayFile Docs”.”
   • What happened: The homepage Resources footer lacked both Relay Docs and RelayFile Docs, so Verify found that the website did not meet the expected outcome.
2. Not met: Gallery heading shows “Proactive agents, ready to deploy” · View browser · Fix with agent
   • Expected “Gallery heading shows “Proactive agents, ready to deploy”.”
   • What happened: Verify could not open the agent gallery because the Pear footer had no Agents link. Its Proactive Agents link opened a separate site instead.
3. Not met: A Google account sign-in page is shown · View browser · Fix with agent
   • Expected “A Google account sign-in page is shown.”
   • What happened: Agent Relay showed a page not found error when Verify selected Continue with Google, so the Google sign-in page did not open.
4. Not met: The heading reads 'Reviewer sign-in' · View browser · Fix with agent
   • Expected “The heading reads 'Reviewer sign-in'.”
   • Expected “A 'Sign in' button is shown.”
   • What happened: Agent Relay showed a page not found instead of the reviewer sign-in page, so Verify found neither the heading nor the sign-in button.
5. Not met: A Google account sign-in page is shown · View browser · Fix with agent
   • Expected “A Google account sign-in page is shown.”
   • What happened: Verify could not reach Google sign-in because Agent Relay showed a page not found for desktop setup.
6. Not met: A Google account sign-in page is shown · View browser · Fix with agent
   • Expected “A Google account sign-in page is shown.”
   • What happened: Agent Relay showed a not-found page instead of Google sign-in when Verify selected Try Free with Cloud on Flows.
7. Not met: A Google account sign-in page is shown · View browser · Fix with agent
   • Expected “A Google account sign-in page is shown.”
   • What happened: Agent Relay showed a page-not-found error instead of Google sign-in when Verify selected Sign up for free on the Teams page.
8. Not met: The heading reads 'Authorize a device' · View browser · Fix with agent
   • Expected “The heading reads 'Authorize a device'.”
   • What happened: Agent Relay showed a page not found instead of the device authorization page, so Verify could not check the prefilled device code.
9. Not met: The page shows 'Unable to join' · View browser · Fix with agent
   • Expected “The page shows 'Unable to join'.”
   • Expected “The page shows 'Invite not found'.”
   • What happened: Agent Relay showed a generic not-found page for the invalid invite link, so Verify did not see the expected invitation error messages.
10. Not met: The page shows 'That password is not correct.' · View browser · Fix with agent

• Expected “The page shows 'That password is not correct.'”
• What happened: Agent Relay showed a page not found instead of the reviewer login, so Verify did not see the wrong-password message.

11. A visitor can open Relayfile documentation from the homepage footer — Blocked · View browser · Fix with agent

• What happened: Verify could not confirm the Relayfile heading because the homepage footer had no RelayFile Docs link. Its Docs link opened general documentation instead.

12. A visitor can revisit Relayfile documentation using browser history — Blocked · View browser · Fix with agent

• What happened: The homepage footer had no RelayFile Docs link, so Verify could not confirm the documentation heading after using browser history. The Docs link opened the general introduction instead.

13. A visitor can resume Relayhistory after visiting the homepage — Blocked · View browser · Fix with agent

• What happened: Agent Relay showed a page not found for the Relayfile introduction, so Verify could not check the return to Relayhistory. Searching the documentation did not resolve the obstacle.

14. A visitor can open Flows from the public homepage footer — Blocked · View browser · Fix with agent

• What happened: The homepage footer had no visible Flows link, so Verify could not follow the requested route or confirm the product heading.

15. A visitor can identify the focused Brand specimen button — Blocked · View browser · Fix with agent

• What happened: Verify could not confirm the focused button’s accessible name because it repeatedly reported an outdated obstruction, even after repositioning the button.

16. A reader can find the available agent connection options — Blocked · View browser · Fix with agent

• What happened: Verify could not confirm the connection options because the introduction contents showed only What you use it for, not Ways To Connect. Reloading and switching documentation versions did not resolve the mismatch.

17. A reader can open workspace onboarding from connection guidance — Blocked · View browser · Fix with agent

• What happened: The documentation did not show Ways To Connect, so Verify could not confirm whether the workspace tutorial opens Quickstart with “1. Install”.

18. A developer can locate guidance for reconnecting an existing workspace — Blocked · View browser · Fix with agent

• What happened: The documentation sidebar did not show Workspaces, and search did not find it, so Verify could not check the reconnect guidance.

19. A developer can find workspace key safety guidance while onboarding — Timed out · View browser · Fix with agent
20. A developer can learn the documented restrictions on observer tokens — Blocked · View browser · Fix with agent

• What happened: Verify could not confirm the observer token restrictions because it recorded an API table instead. Whether the documentation states the restrictions remains unconfirmed.

21. A developer can find expiration requirements for temporary access tokens — Timed out · View browser · Fix with agent
22. A developer can discover the available workspace diagnostic interfaces — Timed out · View browser · Fix with agent
23. A developer can distinguish channel and direct message destinations — Blocked · View browser · Fix with agent

• What happened: Verify could not check the destinations because Messaging Overview was not visible in the documentation navigation or search results.

24. A developer can find token-specific channel membership guidance — Blocked · View browser · Fix with agent

• What happened: Verify could not confirm the invite and join guidance because Agent Relay redirected the Channels page to an older version without Manage Membership. Searching the documentation did not resolve the obstacle.

25. A developer can find handle-array examples for private group messages — Timed out · View browser · Fix with agent
26. A developer can find reply and reaction guidance for DMs — Blocked · View browser · Fix with agent

• What happened: The DMs documentation redirected to an older version and was missing from the latest search results, so Verify could not check the reply and reaction guidance.

27. A developer can find pagination guidance for retrieving message threads — Timed out · View browser · Fix with agent
28. A developer can find reaction aggregation and removal guidance — Timed out · View browser · Fix with agent
29. A developer can find parent identifiers in threaded sending examples — Blocked · View browser · Fix with agent

• What happened: Agent Relay redirected the requested sending messages page to older documentation, so Verify could not check whether Reply In A Thread uses the parent’s messageId.

30. A developer can find the required client for action registration — Timed out · View browser · Fix with agent
31. A developer can find typed predicates for asynchronous action outcomes — Blocked · View browser · Fix with agent

• What happened: The Actions documentation showed a not-found page, so Verify could not check the completion predicates despite searching the docs.

32. A developer can trace orchestration guidance to failure recovery — Timed out · View browser · Fix with agent
33. A developer can find replay-safe event handler contract guidance — Blocked · View browser · Fix with agent

• What happened: Agent Relay redirected Event handlers to older documentation without a Handler contract section, so Verify could not confirm the idempotency guidance.

34. A developer can find the supported event listener selector styles — Blocked · View browser · Fix with agent

• What happened: Agent Relay showed a missing page for the requested orchestration documentation. Verify could not confirm the selector styles after searching the docs.

35. A developer can locate the canonical asynchronous action lifecycle — Blocked · View browser · Fix with agent

• What happened: The documentation sidebar did not have an Automation section, and search found no results, so Verify could not check Action lifecycle.

36. A reader can reach native Connect setup recovery guidance — Timed out · View browser · Fix with agent
37. A reader can find Relay Connect room error recovery guidance — Timed out · View browser · Fix with agent

• What happened: Worker interrupted; acknowledged progress and evidence retained. Unfinished work remains unverified.

38. A reader can trace fleet onboarding to connection verification guidance — Blocked · View browser · Fix with agent

• What happened: The Fleet setup guide showed a page not found and was missing from documentation search, so Verify could not check the node connection guidance.

39. A reader can find macOS fleet recovery through page contents — Timed out · View browser · Fix with agent
40. A reader can find fleet management follow-up documentation — Blocked · View browser · Fix with agent

• What happened: Agent Relay showed a not-found page for the fleet setup guide, so Verify could not check its Next steps links despite searching the docs.

41. A reader can trace public-agent activation to ownership verification guidance — Blocked · View browser · Fix with agent

• What happened: Agent Relay showed a page not found for the public-agent documentation, so Verify could not check the ownership echo guidance.

42. A reader can find serverless public-agent deployment verification guidance — Blocked · View browser · Fix with agent

• What happened: Agent Relay showed a page-not-found message for the public-agent article, so Verify could not check the serverless guidance. The related documentation had different sections.

43. A reader can find public-agent runtime and status guidance — Timed out · View browser · Fix with agent
44. A developer can find consistent existing-identity registration guidance — Timed out · View browser · Fix with agent
45. A reader can return to anchored archived Channels guidance — Timed out · View browser · Fix with agent
46. A reader can select appropriate Python onboarding in latest Quickstart — Blocked · View browser · Fix with agent

• What happened: Verify could not check Python onboarding because the Quickstart page did not show the language selector, even after Verify reloaded and returned to it.

47. A workspace member can enter Cloud through Google login — Blocked · View browser · Fix with agent

• What happened: Agent Relay's Google sign-in opened a page not found, so Verify could not sign in or check the workspace sidebar.

48. A workspace member can read desktop installation prerequisites — Timed out · View browser · Fix with agent
49. A workspace member can leave setup without connecting agents — Blocked · View browser · Fix with agent

• What happened: Agent Relay showed a page not found instead of Sessions, so Verify could not check the empty session history. Trying to sign in did not restore access.

50. A workspace member can dismiss agent setup using Escape — Blocked · View browser · Fix with agent

• What happened: Agent Relay's Google sign-in link showed a page not found, so Verify could not reach the dashboard or check focus on Connect agent.

51. A workspace member can read Claude Code OAuth guidance — Blocked · View browser · Fix with agent

• What happened: The selected preview showed a page not found for sessions, and Verify could not get past it after trying Google sign-in. The Claude Code OAuth guidance remains unchecked.

52. A workspace member can read Codex OAuth setup guidance — Blocked · View browser · Fix with agent

• What happened: Agent Relay's dev dashboard address did not resolve, and reloading did not help. Verify could not check the Codex OAuth setup guidance.

53. A workspace member can read other client OAuth guidance — Blocked · View browser · Fix with agent

• What happened: Agent Relay's Google sign-in page was not found, so Verify could not sign in or check the Other client OAuth setup.

54. A workspace member can inspect existing session access credentials — Blocked · View browser · Fix with agent

• What happened: Verify could not check active credentials because Agent Relay showed a not-found page for the sessions dashboard. Trying Google sign-in did not resolve it.

55. A workspace member can identify the session token workspace — Blocked · View browser · Fix with agent

• What happened: Agent Relay's Google sign-in opened a page not found, so Verify could not sign in or check the selected workspace.

56. A workspace member can identify the computer onboarding workspace — Blocked · View browser · Fix with agent

• What happened: The sessions dashboard showed a page not found, so Verify could not check the computer onboarding workspace. Returning home and choosing Google sign-in did not reach the dashboard.

57. A workspace member can apply a session filter using keyboard — Timed out · View browser · Fix with agent
58. A workspace member can clear an applied session search filter — Blocked · View browser · Fix with agent

• What happened: The sessions dashboard showed a page not found, so Verify could not check clearing the search filter even after trying to sign in.

59. A workspace member can choose the Finished session status — Blocked · View browser · Fix with agent

• What happened: Agent Relay’s Google sign-in opened a page not found, so Verify could not sign in or check the session status filters.

60. A workspace member can choose descending session title sorting — Blocked · View browser · Fix with agent

• What happened: The selected preview showed a page not found instead of the sessions dashboard, so Verify could not check session sorting. Verify returned to login, but recovery stalled.

61. A workspace member can preserve a submitted conversation search — Timed out · View browser · Fix with agent
62. A workspace member can recover session search after navigation — Blocked · View browser · Fix with agent

• What happened: Agent Relay showed a page not found during Google sign-in, so Verify could not check whether session search survived navigation.

63. A workspace member can clear conversation words inside search — Timed out · View browser · Fix with agent
64. A workspace member can replace a selected status suggestion — Blocked · View browser · Fix with agent

• What happened: Agent Relay showed a page not found during Google sign-in, so Verify could not check the status suggestions.

65. A workspace member can combine words and quoted project filters — Timed out · View browser · Fix with agent
66. A workspace member can select sidebar status independently — Blocked · View browser · Fix with agent

• What happened: Agent Relay's Google sign-in opened a page not found, so Verify could not reach sessions or check the sidebar and filters.

67. A workspace member can remove conflicting session filter chips — Timed out · View browser · Fix with agent
68. A workspace member can remove search suggestions using keyboard — Blocked · View browser · Fix with agent

• What happened: The app showed a page not found for sessions, so Verify could not check search suggestions. Returning home and trying Google sign-in did not reach the workspace.

69. A workspace member can dismiss search and regain focus — Timed out · View browser · Fix with agent
70. A workspace member can recognize a future activity start — Blocked · View browser · Fix with agent

• What happened: The selected preview showed a page not found instead of the sessions dashboard, so Verify could not check the activity date range.

71. A workspace member can recognize reversed activity dates — Blocked · View browser · Fix with agent

• What happened: The selected preview showed a page-not-found screen for the sessions dashboard, so Verify could not check reversed dates. Going home and back did not resolve it.

72. A workspace member can recognize a missing activity end — Blocked · View browser · Fix with agent

• What happened: The sessions dashboard showed a page not found, so Verify could not check the end date or activity message, even after trying Google sign-in.

73. A workspace member can recognize excessive activity date ranges — Blocked · View browser · Fix with agent

• What happened: Agent Relay showed a page-not-found error for the sessions page, so Verify could not check the activity date range. Trying to sign in did not resolve it.

74. A workspace member can inspect one year of activity — Blocked · View browser · Fix with agent

• What happened: Agent Relay showed a not-found page instead of the sessions dashboard, so Verify could not check the one-year activity range. Trying to sign in did not get Verify to the dashboard.

75. A workspace member can recover invalid activity dates — Blocked · View browser · Fix with agent

• What happened: Agent Relay showed a page not found instead of the sessions dashboard, so Verify could not check activity date recovery.

76. A workspace member can return activity navigation to today — Blocked · View browser · Fix with agent

• What happened: The selected preview showed a page not found for the sessions dashboard, and Verify could not reach it through login. The Activity date and navigation were not checked.

77. A workspace member can inspect session grouping choices — Blocked · View browser · Fix with agent

• What happened: The app showed a page not found for the sessions dashboard, so Verify could not check the grouping choices. Trying Google sign-in did not unblock it.

78. A workspace member can cancel a session grouping choice — Timed out · View browser · Fix with agent
79. A workspace member can inspect lower session column controls — Timed out · View browser · Fix with agent
80. A workspace member can close table display using keyboard — Blocked · View browser · Fix with agent

• What happened: The selected preview showed a page not found instead of the sessions dashboard, so Verify could not check Table display keyboard focus.

81. A workspace member can inspect account actions using keyboard — Blocked · View browser · Fix with agent

• What happened: The sessions dashboard showed a page not found instead of the workspace, so Verify could not check the account menu. Trying to sign in again did not restore access.

82. A workspace member can reach flows using collapsed navigation — Execution cancelled · View browser · Fix with agent
83. A workspace member can skip navigation to session content — Blocked · View browser · Fix with agent

• What happened: The selected preview showed a page not found for the sessions dashboard, so Verify could not check focus on Activity. Returning home did not unblock the test.

84. A workspace member can navigate toward screen discovery by arrow — Execution cancelled · View browser · Fix with agent
85. A workspace member can preview agent usage using keyboard — Timed out · View browser · Fix with agent

• What happened: Agent Relay's Google sign-in led to a not-found page, so Verify could not access the workspace or check agent usage.

86. A workspace member can preview where agents are working — Execution cancelled · View browser · Fix with agent
87. A member sees Addresses unavailable on Dev — Blocked · View browser · Fix with agent

• What happened: Dev's Google sign-in showed a page not found, so Verify could not sign in or check Addresses.

88. A visitor is asked to sign in for a dashboard link — Blocked · View browser · Fix with agent

• What happened: The Dev site did not load because its address did not resolve, even after reloading. Verify could not check the sign-in option or Sessions list.

89. A visitor can find Google sign-in on the login page — Blocked · View browser · Fix with agent

• What happened: Verify could not confirm the 'New to Agent Relay?' link because the phrase appeared beside 'Learn more' and its link identity was unclear.

90. A visitor is asked to sign in to approve a device — Blocked · View browser · Fix with agent

• What happened: The selected preview showed a page not found instead of the device code form, even after reloading. Verify could not check the sign-in prompt.

91. A visitor can copy the Flows setup prompt — Blocked · View browser · Fix with agent

• What happened: Flows setup failed to become ready, leaving Copy setup prompt disabled. Verify could not check whether the button changes to Prompt copied.

92. A visitor can copy the Teams setup prompt — Blocked · View browser · Fix with agent

• What happened: The Teams setup page could not create a session, even after retries and a new session, so Verify could not check whether the prompt was copied.

93. A visitor can start a new signup session — Blocked · View browser · Fix with agent

• What happened: The signup page did not show a session ID because session creation failed even after retries and a reload. Verify could not check whether starting a new session changed it.

94. A visitor sees Flows signup needs terminal access — Blocked · View browser · Fix with agent

• What happened: The Flows signup setup session did not start, even after retries, so Verify could not check the terminal-access message.

95. A reviewer can open the Flows deploy onboarding — Blocked · View browser · Fix with agent

• What happened: Agent Relay remained unavailable after a retry, so Verify could not check the flow creation heading.

96. A reviewer can open the invite dialog without sending — Blocked · View browser · Fix with agent

• What happened: Agent Relay remained unavailable after Verify retried, so Verify could not check the invite dialog or its Send invitation button.

97. A reviewer can sign in with the reviewer password — Blocked · View browser · Fix with agent

• What happened: Agent Relay remained unavailable after Verify retried, so Verify could not sign in or check the OpenAI Review workspace.

98. A reviewer gets 'code not found' for an unknown device code — Blocked · View browser · Fix with agent

• What happened: Agent Relay remained unavailable after a retry, so Verify could not check the unknown device code message.

8 more findings in the run results.

Scenarios

Result	Scenario	Persona	Outcomes	Duration
Failed	A visitor can locate documentation resources in the homepage footer	Signed-out visitor	0/1	1m 4s
Passed	A visitor can skip homepage navigation using the keyboard	Signed-out visitor	1/1	16s
Passed	A visitor can select the real-time team coordination feature	Signed-out visitor	1/1	21s
Passed	A visitor can select the homepage timezone coordination feature	Signed-out visitor	1/1	25s
Passed	A visitor can select public-agent debugging using the keyboard	Signed-out visitor	1/1	17s
Passed	A visitor can open Relay documentation from the homepage footer	Signed-out visitor	1/1	39s
Passed	A visitor can return home after using skip navigation	Signed-out visitor	1/1	32s
Blocked	A visitor can open Relayfile documentation from the homepage footer	Signed-out visitor	0/1	2m 15s
Blocked	A visitor can revisit Relayfile documentation using browser history	Signed-out visitor	0/1	4m 15s
Blocked	A visitor can resume Relayhistory after visiting the homepage	Signed-out visitor	0/1	2m 51s
Blocked	A visitor can open Flows from the public homepage footer	Signed-out visitor	0/1	4m 25s
Passed	A visitor can select the Flows code-review example by keyboard	Signed-out visitor	1/1	1m 1s
Passed	A visitor can open Flows documentation from its product page	Signed-out visitor	1/1	37s
Passed	A visitor can inspect wordmark choices in the Brand Kit	Signed-out visitor	1/1	35s
Passed	A visitor can open the web theme using keyboard activation	Signed-out visitor	1/1	45s
Passed	A visitor can navigate past disabled Brand button specimens	Signed-out visitor	1/1	1m 1s
Blocked	A visitor can identify the focused Brand specimen button	Signed-out visitor	0/1	1m 56s
Passed	A visitor can read the reusable web theme token snippet	Signed-out visitor	1/1	51s
Passed	A visitor can open Relay documentation from the Pear page	Signed-out visitor	1/1	55s
Failed	A visitor can open the agent gallery from Pear	Signed-out visitor	0/1	7m 2s
Passed	A visitor can browse use cases from the agent gallery	Signed-out visitor	1/1	37s
Passed	A visitor can locate the pull-request automation use case	Signed-out visitor	1/1	19s
Passed	A visitor can read the PR Reviewer configuration requirements	Signed-out visitor	1/1	41s
Passed	A visitor can read the Repo Hygiene configuration requirements	Signed-out visitor	1/1	28s
Passed	A visitor can return to use cases after reading hygiene details	Signed-out visitor	1/1	27s
Passed	A visitor can read the Linear Implementer configuration requirements	Signed-out visitor	1/1	1m 38s
Passed	A visitor can read the Granola Prospect configuration requirements	Signed-out visitor	1/1	54s
Passed	A visitor can read the news-monitor configuration requirements	Signed-out visitor	1/1	43s
Passed	A visitor can read the Vendor Monitor configuration requirements	Signed-out visitor	1/1	43s
Passed	A visitor can read the music-alert configuration requirements	Signed-out visitor	1/1	26s
Passed	A visitor can read the multi-agent team coordination description	Signed-out visitor	1/1	48s
Passed	A visitor can read the infrastructure-monitor configuration requirements	Signed-out visitor	1/1	46s
Passed	A visitor can read the Inbox Buddy configuration requirements	Signed-out visitor	1/1	23s
Passed	A visitor can read the Linear Slack configuration requirements	Signed-out visitor	1/1	41s
Passed	A visitor can reveal the public agent-authoring prompt	Signed-out visitor	1/1	21s
Passed	A visitor can open technical docs from messaging marketing	Signed-out visitor	1/1	18s
Passed	A visitor can find support guidance through the homepage footer	Signed-out visitor	1/1	23s
Passed	A visitor can read the privacy policy from support	Signed-out visitor	1/1	44s
Failed	A visitor can focus the privacy policy telemetry reference	Signed-out visitor	0/1	1m 30s
Passed	A visitor can open trust guidance through keyboard navigation	Signed-out visitor	1/1	2m 4s
Passed	A reader can reach public documentation from the homepage footer	Dev workspace member	1/1	1m 10s
Blocked	A reader can find the available agent connection options	Dev workspace member	0/1	6m 15s
Blocked	A reader can open workspace onboarding from connection guidance	Dev workspace member	0/1	6m 33s
Failed	A developer can identify the workspace credential required for onboarding	Dev workspace member	0/1	1m 49s
Failed	A developer can find harness installation guidance before spawning agents	Dev workspace member	0/1	4m 41s
Blocked	A developer can locate guidance for reconnecting an existing workspace	Dev workspace member	0/1	1m 21s
Timed out	A developer can find workspace key safety guidance while onboarding	Dev workspace member	0/1	—
Blocked	A developer can learn the documented restrictions on observer tokens	Dev workspace member	0/1	1m 37s
Timed out	A developer can find expiration requirements for temporary access tokens	Dev workspace member	0/1	—
Timed out	A developer can discover the available workspace diagnostic interfaces	Dev workspace member	0/1	—
Blocked	A developer can distinguish channel and direct message destinations	Dev workspace member	0/1	4m 18s
Blocked	A developer can find token-specific channel membership guidance	Dev workspace member	0/1	7m 19s
Timed out	A developer can find handle-array examples for private group messages	Dev workspace member	0/1	—
Blocked	A developer can find reply and reaction guidance for DMs	Dev workspace member	0/1	1m 46s
Timed out	A developer can find pagination guidance for retrieving message threads	Dev workspace member	0/1	—
Timed out	A developer can find reaction aggregation and removal guidance	Dev workspace member	0/1	—
Blocked	A developer can find parent identifiers in threaded sending examples	Dev workspace member	0/1	7m 43s
Timed out	A developer can find the required client for action registration	Dev workspace member	0/1	—
Blocked	A developer can find typed predicates for asynchronous action outcomes	Dev workspace member	0/1	4m 42s
Timed out	A developer can trace orchestration guidance to failure recovery	Dev workspace member	0/1	—
Blocked	A developer can find replay-safe event handler contract guidance	Dev workspace member	0/1	2m 9s
Blocked	A developer can find the supported event listener selector styles	Dev workspace member	0/1	1m 24s
Blocked	A developer can locate the canonical asynchronous action lifecycle	Dev workspace member	0/1	8m 49s
Passed	A reader can find account-free Relay Connect guest prerequisites	Dev workspace member	1/1	28s
Timed out	A reader can reach native Connect setup recovery guidance	Dev workspace member	0/1	—
Timed out	A reader can find Relay Connect room error recovery guidance	Dev workspace member	0/1	18s
Blocked	A reader can trace fleet onboarding to connection verification guidance	Dev workspace member	0/1	4m 7s
Timed out	A reader can find macOS fleet recovery through page contents	Dev workspace member	0/1	—
Blocked	A reader can find fleet management follow-up documentation	Dev workspace member	0/1	1m 20s
Failed	A reader can find the separate public-agent registration prerequisites	Dev workspace member	0/1	2m 37s
Blocked	A reader can trace public-agent activation to ownership verification guidance	Dev workspace member	0/1	1m 36s
Blocked	A reader can find serverless public-agent deployment verification guidance	Dev workspace member	0/1	2m 43s
Timed out	A reader can find public-agent runtime and status guidance	Dev workspace member	0/1	—
Timed out	A developer can find consistent existing-identity registration guidance	Dev workspace member	0/1	—
Failed	A reader can switch archived Channels guidance to the latest version	Dev workspace member	0/1	1m 18s
Not confirmed	A reader can switch current Channels guidance to an archived version	Dev workspace member	0/1	41s
Timed out	A reader can return to anchored archived Channels guidance	Dev workspace member	0/1	—
Passed	A reader can return to anchored current Channels guidance	Dev workspace member	1/1	1m 32s
Passed	A reader can return to directly opened archived Channels guidance	Dev workspace member	1/1	1m 14s
Blocked	A reader can select appropriate Python onboarding in latest Quickstart	Dev workspace member	0/1	2m 42s
Blocked	A workspace member can enter Cloud through Google login	Dev workspace member	0/2	1m 27s
Timed out	A workspace member can read desktop installation prerequisites	Dev workspace member	0/2	—
Blocked	A workspace member can leave setup without connecting agents	Dev workspace member	0/1	1m 10s
Blocked	A workspace member can dismiss agent setup using Escape	Dev workspace member	0/1	53s
Blocked	A workspace member can read Claude Code OAuth guidance	Dev workspace member	0/1	1m 20s
Blocked	A workspace member can read Codex OAuth setup guidance	Dev workspace member	0/1	1m 14s
Blocked	A workspace member can read other client OAuth guidance	Dev workspace member	0/1	1m 13s
Blocked	A workspace member can inspect existing session access credentials	Dev workspace member	0/1	1m 3s
Blocked	A workspace member can identify the session token workspace	Dev workspace member	0/1	1m 27s
Blocked	A workspace member can identify the computer onboarding workspace	Dev workspace member	0/1	1m 8s
Timed out	A workspace member can apply a session filter using keyboard	Dev workspace member	0/1	—
Blocked	A workspace member can clear an applied session search filter	Dev workspace member	0/1	1m 17s
Blocked	A workspace member can choose the Finished session status	Dev workspace member	0/2	1m 20s
Blocked	A workspace member can choose descending session title sorting	Dev workspace member	0/1	1m 10s
Timed out	A workspace member can preserve a submitted conversation search	Dev workspace member	0/2	—
Blocked	A workspace member can recover session search after navigation	Dev workspace member	0/1	1m 3s
Timed out	A workspace member can clear conversation words inside search	Dev workspace member	0/1	—
Blocked	A workspace member can replace a selected status suggestion	Dev workspace member	0/2	54s
Timed out	A workspace member can combine words and quoted project filters	Dev workspace member	0/3	—
Blocked	A workspace member can select sidebar status independently	Dev workspace member	0/2	56s
Timed out	A workspace member can remove conflicting session filter chips	Dev workspace member	0/1	—
Blocked	A workspace member can remove search suggestions using keyboard	Dev workspace member	0/2	1m 3s
Timed out	A workspace member can dismiss search and regain focus	Dev workspace member	0/1	—
Blocked	A workspace member can recognize a future activity start	Dev workspace member	0/1	1m 18s
Blocked	A workspace member can recognize reversed activity dates	Dev workspace member	0/2	1m 7s
Blocked	A workspace member can recognize a missing activity end	Dev workspace member	0/2	1m 24s
Blocked	A workspace member can recognize excessive activity date ranges	Dev workspace member	0/1	1m 25s
Blocked	A workspace member can inspect one year of activity	Dev workspace member	0/1	1m 1s
Blocked	A workspace member can recover invalid activity dates	Dev workspace member	0/2	1m 23s
Blocked	A workspace member can return activity navigation to today	Dev workspace member	0/2	1m 22s
Blocked	A workspace member can inspect session grouping choices	Dev workspace member	0/1	1m 3s
Timed out	A workspace member can cancel a session grouping choice	Dev workspace member	0/1	—
Timed out	A workspace member can inspect lower session column controls	Dev workspace member	0/2	—
Blocked	A workspace member can close table display using keyboard	Dev workspace member	0/1	46s
Blocked	A workspace member can inspect account actions using keyboard	Dev workspace member	0/1	1m 26s
Blocked	A workspace member can reach flows using collapsed navigation	Dev workspace member	0/1	—
Blocked	A workspace member can skip navigation to session content	Dev workspace member	0/1	55s
Blocked	A workspace member can navigate toward screen discovery by arrow	Dev workspace member	0/1	—
Timed out	A workspace member can preview agent usage using keyboard	Dev workspace member	0/1	56s
Blocked	A workspace member can preview where agents are working	Dev workspace member	0/1	—
Blocked	A member sees Addresses unavailable on Dev	Dev workspace member	0/3	1m 9s
Blocked	A visitor is asked to sign in for a dashboard link	Signed-out visitor	0/2	45s
Failed	A visitor can begin Google sign-in from the login page	Signed-out visitor	0/1	49s
Failed	A visitor can open agent signup from the Teams page	Signed-out visitor	1/2	40s
Blocked	A visitor can find Google sign-in on the login page	Signed-out visitor	1/2	38s
Failed	A visitor can read the reviewer sign-in page	Signed-out visitor	0/2	1m 15s
Passed	A visitor can see both signup options on the Teams page	Signed-out visitor	3/3	21s
Passed	A visitor gets not found at the retired Flows onboarding URL	Signed-out visitor	1/1	46s
Failed	A visitor is asked to sign in for desktop setup	Signed-out visitor	0/1	45s
Blocked	A visitor is asked to sign in to approve a device	Signed-out visitor	0/2	2m 45s
Failed	A visitor is sent to Google from Flows 'Try Free'	Signed-out visitor	0/1	42s
Failed	A visitor is sent to Google from Teams sign up	Signed-out visitor	0/1	57s
Failed	A visitor sees a device code prefilled from the link	Signed-out visitor	0/2	1m 7s
Passed	A visitor sees an expired session message on login	Signed-out visitor	2/2	31s
Failed	A visitor sees 'Invite not found' for a bad invite link	Signed-out visitor	0/2	46s
Passed	A visitor sees the invite notice on login	Signed-out visitor	1/1	49s
Failed	A visitor sees the reviewer wrong-password message	Signed-out visitor	0/1	58s
Blocked	A visitor can copy the Flows setup prompt	Signed-out visitor	0/1	5m 2s
Blocked	A visitor can copy the Teams setup prompt	Signed-out visitor	0/1	6m 40s
Failed	A visitor can see the five Teams signup steps	Signed-out visitor	3/4	1m 40s
Blocked	A visitor can start a new signup session	Signed-out visitor	0/1	7m 42s
Blocked	A visitor sees Flows signup needs terminal access	Signed-out visitor	0/1	4m 23s
Blocked	A reviewer can open the Flows deploy onboarding	OpenAI reviewer	0/1	8s
Blocked	A reviewer can open the invite dialog without sending	OpenAI reviewer	0/2	8s
Blocked	A reviewer can sign in with the reviewer password	OpenAI reviewer	0/2	8s
Blocked	A reviewer gets 'code not found' for an unknown device code	OpenAI reviewer	0/1	8s

Run a scenario again

Selected for this commit

• A developer can discover the available workspace diagnostic interfaces · Run
• A developer can distinguish channel and direct message destinations · Run
• A developer can find consistent existing-identity registration guidance · Run
• A developer can find expiration requirements for temporary access tokens · Run
• A developer can find handle-array examples for private group messages · Run
• A developer can find harness installation guidance before spawning agents · Run
• A developer can find pagination guidance for retrieving message threads · Run
• A developer can find parent identifiers in threaded sending examples · Run
• A developer can find reaction aggregation and removal guidance · Run
• A developer can find replay-safe event handler contract guidance · Run
• A developer can find reply and reaction guidance for DMs · Run
• A developer can find the required client for action registration · Run
• A developer can find the supported event listener selector styles · Run
• A developer can find token-specific channel membership guidance · Run
• A developer can find typed predicates for asynchronous action outcomes · Run
• A developer can find workspace key safety guidance while onboarding · Run
• A developer can identify the workspace credential required for onboarding · Run
• A developer can learn the documented restrictions on observer tokens · Run
• A developer can locate guidance for reconnecting an existing workspace · Run
• A developer can locate the canonical asynchronous action lifecycle · Run
• A developer can trace orchestration guidance to failure recovery · Run
• A member sees Addresses unavailable on Dev · Run
• A reader can find account-free Relay Connect guest prerequisites · Run
• A reader can find fleet management follow-up documentation · Run
• A reader can find macOS fleet recovery through page contents · Run
• A reader can find public-agent runtime and status guidance · Run
• A reader can find Relay Connect room error recovery guidance · Run
• A reader can find serverless public-agent deployment verification guidance · Run
• A reader can find the available agent connection options · Run
• A reader can find the separate public-agent registration prerequisites · Run
• A reader can open workspace onboarding from connection guidance · Run
• A reader can reach native Connect setup recovery guidance · Run
• A reader can reach public documentation from the homepage footer · Run
• A reader can return to anchored archived Channels guidance · Run
• A reader can return to anchored current Channels guidance · Run
• A reader can return to directly opened archived Channels guidance · Run
• A reader can select appropriate Python onboarding in latest Quickstart · Run
• A reader can switch archived Channels guidance to the latest version · Run
• A reader can switch current Channels guidance to an archived version · Run
• A reader can trace fleet onboarding to connection verification guidance · Run

126 more scenarios in Composal.

Why these 146 scenarios were selected

• A visitor can locate documentation resources in the homepage footer: Next.js upgrade affects homepage rendering; scenario checks rendered footer documentation links.
• A visitor can skip homepage navigation using the keyboard: Next.js upgrade can affect page hydration and focus; scenario exercises homepage skip navigation.
• A visitor can select the real-time team coordination feature: Next.js upgrade affects client hydration; scenario checks real-time feature selection still works.
• A visitor can select the homepage timezone coordination feature: Next.js upgrade affects client hydration; scenario checks timezone feature selection still works.
• A visitor can select public-agent debugging using the keyboard: Next.js upgrade affects client hydration; scenario checks keyboard selection of the debugging feature.
• A visitor can open Relay documentation from the homepage footer: Next.js upgrade affects route loading; scenario opens Relay Docs and verifies its Introduction heading.
• A visitor can return home after using skip navigation: Next.js upgrade affects navigation and history restoration; scenario checks returning from docs to the homepage.
• A visitor can open Relayfile documentation from the homepage footer: Next.js upgrade affects route loading; scenario opens Relayfile docs and verifies the article heading.
• A visitor can revisit Relayfile documentation using browser history: Next.js upgrade affects routing and history; scenario verifies Relayfile after browser Back and Forward.
• A visitor can resume Relayhistory after visiting the homepage: Next.js upgrade affects routing and history; scenario checks Relayhistory restoration after visiting home.
• A visitor can open Flows from the public homepage footer: Next.js upgrade affects route loading; scenario follows the homepage Flows link and checks its heading.
• A visitor can select the Flows code-review example by keyboard: Next.js upgrade affects client hydration; scenario checks keyboard selection of the Flows code-review example.
• A visitor can open Flows documentation from its product page: Next.js upgrade affects route loading; scenario follows the Flows documentation link and checks its article.
• A visitor can inspect wordmark choices in the Brand Kit: Next.js upgrade affects page rendering; scenario loads Brand Kit and checks the wordmark gallery.
• A visitor can open the web theme using keyboard activation: Next.js upgrade affects route loading; scenario opens the web theme from Brand Kit and checks Color system.
• A visitor can navigate past disabled Brand button specimens: Next.js upgrade can affect rendered controls; scenario checks focus skips disabled theme button specimens.
• A visitor can identify the focused Brand specimen button: Next.js upgrade affects rendered controls; scenario checks the focused theme button retains an accessible name.
• A visitor can read the reusable web theme token snippet: Next.js upgrade affects page rendering; scenario verifies the theme token snippet remains visible.
• A visitor can open Relay documentation from the Pear page: Next.js upgrade affects route loading; scenario follows Pear's docs link and checks Introduction.
• A visitor can open the agent gallery from Pear: Next.js upgrade affects route loading; scenario navigates from Pear to the agent gallery and checks its heading.
• A visitor can browse use cases from the agent gallery: Next.js upgrade affects route loading; scenario opens use cases from the agent gallery and verifies the page.
• A visitor can locate the pull-request automation use case: Next.js upgrade affects page rendering and navigation; scenario locates the pull-request automation section.
• A visitor can read the PR Reviewer configuration requirements: Next.js upgrade affects agent detail routing and rendering; scenario opens PR Reviewer and checks APPROVERS.
• A visitor can read the Repo Hygiene configuration requirements: Next.js upgrade affects detail routing and rendering; scenario opens Repo Hygiene and checks NOTION_DATABASE_ID.
• A visitor can return to use cases after reading hygiene details: Next.js upgrade affects history restoration; scenario returns from Repo Hygiene to its use-case section.
• A visitor can read the Linear Implementer configuration requirements: Next.js upgrade affects detail routing and rendering; scenario opens Linear Implementer and checks MENTION.
• A visitor can read the Granola Prospect configuration requirements: Next.js upgrade affects detail routing and rendering; scenario opens Granola Prospect and checks LINEAR_TEAM_ID.
• A visitor can read the news-monitor configuration requirements: Next.js upgrade affects detail routing and rendering; scenario opens Hacker News Monitor and checks TOPICS.
• A visitor can read the Vendor Monitor configuration requirements: Next.js upgrade affects detail routing and rendering; scenario opens Vendor Monitor and checks VENDORS.
• A visitor can read the music-alert configuration requirements: Next.js upgrade affects detail routing and rendering; scenario opens Spotify Releases and checks SLACK_USER.
• A visitor can read the multi-agent team coordination description: Next.js upgrade affects page rendering; scenario verifies the multi-agent coordination description loads.
• A visitor can read the infrastructure-monitor configuration requirements: Next.js upgrade affects detail routing; scenario opens Cloudflare Monitor and checks its configuration content.
• A visitor can read the Inbox Buddy configuration requirements: Next.js upgrade affects detail routing and rendering; scenario opens Inbox Buddy and checks TELEGRAM_CHAT.
• A visitor can read the Linear Slack configuration requirements: Next.js upgrade affects detail routing and rendering; scenario opens Linear Slack and checks SLACK_CHANNEL.
• A visitor can reveal the public agent-authoring prompt: Next.js upgrade affects client hydration; scenario checks Show prompt expands the agent-authoring text.
• A visitor can open technical docs from messaging marketing: Next.js upgrade affects route loading; scenario follows messaging's docs link and verifies Introduction.
• A visitor can find support guidance through the homepage footer: Next.js upgrade affects route loading; scenario opens Support from the homepage and checks support content.
• A visitor can read the privacy policy from support: Next.js upgrade affects route loading; scenario opens Privacy Policy from Support and verifies its heading.
• A visitor can focus the privacy policy telemetry reference: Next.js upgrade affects privacy page rendering; scenario checks the telemetry link remains keyboard reachable.
• A visitor can open trust guidance through keyboard navigation: Next.js upgrade affects route loading; scenario keyboard-navigates from Privacy to Security and trust.
• A reader can reach public documentation from the homepage footer: Next.js upgrade affects route loading; scenario opens public documentation from the footer and checks Introduction.
• A reader can find the available agent connection options: Next.js upgrade affects docs rendering and anchor navigation; scenario checks Ways To Connect options.
• A reader can open workspace onboarding from connection guidance: Next.js upgrade affects docs route loading; scenario follows Build a workspace and verifies Quickstart installation.
• A developer can identify the workspace credential required for onboarding: Next.js upgrade affects docs rendering and navigation; scenario checks workspace join-secret guidance.
• A developer can find harness installation guidance before spawning agents: Next.js upgrade affects docs rendering and navigation; scenario checks the harness installation section.
• A developer can locate guidance for reconnecting an existing workspace: Next.js upgrade affects docs routing and rendering; scenario opens Workspaces and checks reconnect guidance.
• A developer can find workspace key safety guidance while onboarding: Next.js upgrade affects docs rendering and navigation; traverses workspace/authentication links to key guidance.
• A developer can learn the documented restrictions on observer tokens: Next.js upgrade affects docs rendering; opens authentication and navigates to observer restrictions.
• A developer can find expiration requirements for temporary access tokens: Next.js upgrade affects docs rendering and anchors; checks authentication Lifecycle content remains accessible.
• A developer can discover the available workspace diagnostic interfaces: Next.js upgrade affects docs rendering and navigation; reaches workspace Diagnostics and its links.
• A developer can distinguish channel and direct message destinations: Next.js upgrade affects docs route transitions; navigates from introduction to messaging send-path examples.
• A developer can find token-specific channel membership guidance: Next.js upgrade affects page rendering and anchors; checks Channels membership guidance remains reachable.
• A developer can find handle-array examples for private group messages: Next.js upgrade affects docs rendering; loads DMs and reaches the group-message example.
• A developer can find reply and reaction guidance for DMs: Next.js upgrade affects docs rendering and anchor navigation; reaches DM reply examples.
• A developer can find pagination guidance for retrieving message threads: Next.js upgrade affects docs rendering; loads Threads and navigates to pagination guidance.
• A developer can find reaction aggregation and removal guidance: Next.js upgrade affects docs rendering; loads emoji reactions and reaches aggregation guidance.
• A developer can find parent identifiers in threaded sending examples: Next.js upgrade affects docs rendering and anchors; checks threaded-send examples remain accessible.
• A developer can find the required client for action registration: Next.js upgrade affects docs navigation; sidebar transition to Actions must still expose registration guidance.
• A developer can find typed predicates for asynchronous action outcomes: Next.js upgrade affects docs rendering; opens Actions and reaches completion predicates.
• A developer can trace orchestration guidance to failure recovery: Next.js upgrade affects docs navigation; traverses orchestration guidance through the stall-guard section.
• A developer can find replay-safe event handler contract guidance: Next.js upgrade affects docs rendering and anchors; reaches the event-handler contract.
• A developer can find the supported event listener selector styles: Next.js upgrade affects sidebar routing and anchors; navigates to event-handler selector examples.
• A developer can locate the canonical asynchronous action lifecycle: Next.js upgrade affects docs route transitions; navigates from event handlers to Events lifecycle guidance.
• A reader can find account-free Relay Connect guest prerequisites: Next.js upgrade affects docs rendering; opens Relay Connect and reaches guest prerequisites.
• A reader can reach native Connect setup recovery guidance: Next.js upgrade affects page loading and links; follows Connect guest guidance into the native setup guide.
• A reader can find Relay Connect room error recovery guidance: Next.js upgrade affects docs rendering and anchors; checks Connect troubleshooting remains accessible.
• A reader can trace fleet onboarding to connection verification guidance: Next.js upgrade affects docs routing and anchors; traverses Connect to fleet connection verification.
• A reader can find macOS fleet recovery through page contents: Next.js upgrade affects docs rendering and contents navigation; reaches macOS fleet recovery guidance.
• A reader can find fleet management follow-up documentation: Next.js upgrade affects docs rendering and anchors; reaches fleet Next steps and its follow-up links.
• A reader can find the separate public-agent registration prerequisites: Next.js upgrade affects docs route transitions; follows introduction navigation to public-agent prerequisites.
• A reader can trace public-agent activation to ownership verification guidance: Next.js upgrade affects docs rendering and anchors; traverses public-agent ownership guidance.
• A reader can find serverless public-agent deployment verification guidance: Next.js upgrade affects docs rendering and anchors; reaches public-agent serverless guidance.
• A reader can find public-agent runtime and status guidance: Next.js upgrade affects docs rendering and navigation; reaches public-agent state guidance.
• A developer can find consistent existing-identity registration guidance: Next.js upgrade affects page loading; opens SDK and public-agent routes and checks registration guidance.
• A reader can switch archived Channels guidance to the latest version: Next.js upgrade affects client routing; version switching must load current Channels contents from an archived page.
• A reader can switch current Channels guidance to an archived version: Next.js upgrade affects client routing; version switching must load archived Channels contents.
• A reader can return to anchored archived Channels guidance: Next.js upgrade affects routing/history; Back after a version switch must restore the archived version indicator.
• A reader can return to anchored current Channels guidance: Next.js upgrade affects routing/history; Back must restore archived Channels contents after anchored navigation.
• A reader can return to directly opened archived Channels guidance: Next.js upgrade affects routing/history; Back must restore a directly opened archived documentation version.
• A reader can select appropriate Python onboarding in latest Quickstart: Next.js upgrade affects rendering/hydration; Quickstart language selection must remain correct after reload.
• A workspace member can enter Cloud through Google login: Next.js upgrade affects application routing/rendering; Google login must still reach the workspace sidebar.
• A workspace member can read desktop installation prerequisites: Next.js upgrade affects Cloud rendering/hydration; Connect agent must still expand installation prerequisites.
• A workspace member can leave setup without connecting agents: Next.js upgrade affects Cloud rendering/hydration; closing setup must still return to the empty sessions table.
• A workspace member can dismiss agent setup using Escape: Next.js upgrade affects Cloud hydration; keyboard setup dismissal must still restore Connect agent focus.
• A workspace member can read Claude Code OAuth guidance: Next.js upgrade affects Cloud rendering/hydration; Agent access must still display Claude OAuth guidance.
• A workspace member can read Codex OAuth setup guidance: Next.js upgrade affects Cloud hydration; selecting Codex must still render its OAuth setup guidance.
• A workspace member can read other client OAuth guidance: Next.js upgrade affects Cloud hydration; selecting Other client must still display its OAuth guidance.
• A workspace member can inspect existing session access credentials: Next.js upgrade affects Cloud rendering; Agent access must still show the no-active-credentials state.
• A workspace member can identify the session token workspace: Next.js upgrade affects Cloud hydration; opening the workspace menu must still show the selected workspace.
• A workspace member can identify the computer onboarding workspace: Next.js upgrade affects Cloud rendering/hydration; computer onboarding must still name the active workspace.
• A workspace member can apply a session filter using keyboard: Next.js upgrade affects Cloud hydration; keyboard filter interactions must still apply is:active.
• A workspace member can clear an applied session search filter: Next.js upgrade affects Cloud hydration; clearing the applied session filter must restore the search prompt.
• A workspace member can choose the Finished session status: Next.js upgrade affects Cloud hydration; sidebar interactions must still select only Finished status.
• A workspace member can choose descending session title sorting: Next.js upgrade affects Cloud hydration; repeated sort clicks must still produce Session descending.
• A workspace member can preserve a submitted conversation search: Next.js upgrade affects page loading/hydration; submitted session search and Finished status must survive reload.
• A workspace member can recover session search after navigation: Next.js upgrade affects routing/history; navigating to Flows and Back must preserve the submitted session search.
• A workspace member can clear conversation words inside search: Next.js upgrade affects dashboard hydration; clearing search checks the interactive toolbar still updates.
• A workspace member can replace a selected status suggestion: Next.js upgrade affects dashboard hydration; status selection checks interactive state still updates.
• A workspace member can combine words and quoted project filters: Next.js upgrade affects dashboard hydration; submitting search checks chips and retained text still render.
• A workspace member can select sidebar status independently: Next.js upgrade affects dashboard hydration; sidebar selection checks independent filter state still works.
• A workspace member can remove conflicting session filter chips: Next.js upgrade affects dashboard hydration; removing chips checks client filter updates still work.
• A workspace member can remove search suggestions using keyboard: Next.js upgrade affects dashboard hydration; keyboard suggestion removal checks client interactions still work.
• A workspace member can dismiss search and regain focus: Next.js upgrade affects dashboard hydration; Escape dismissal checks search focus restoration still works.
• A workspace member can recognize a future activity start: Next.js upgrade affects dashboard rendering and hydration; future-date entry checks validation still appears.
• A workspace member can recognize reversed activity dates: Next.js upgrade affects dashboard hydration; reversed dates check validation and disabled navigation still render.
• A workspace member can recognize a missing activity end: Next.js upgrade affects dashboard hydration; clearing the end date checks validation still renders.
• A workspace member can recognize excessive activity date ranges: Next.js upgrade affects dashboard hydration; excessive date ranges check validation still renders.
• A workspace member can inspect one year of activity: Next.js upgrade affects dashboard hydration; entering a valid year range checks accepted state still renders.
• A workspace member can recover invalid activity dates: Next.js upgrade affects dashboard hydration; correcting dates checks recovery to the empty activity state.
• A workspace member can return activity navigation to today: Next.js upgrade affects dashboard hydration; period navigation checks chart labels and disabled state still update.
• A workspace member can inspect session grouping choices: Next.js upgrade affects dashboard hydration; opening grouping controls checks menu options still render.
• A workspace member can cancel a session grouping choice: Next.js upgrade affects dashboard hydration; canceling grouping checks retained selection and keyboard focus.
• A workspace member can inspect lower session column controls: Next.js upgrade affects dashboard rendering and hydration; opening table display checks lower column controls.
• A workspace member can close table display using keyboard: Next.js upgrade affects dashboard hydration; keyboard closure checks panel dismissal and restored focus.
• A workspace member can inspect account actions using keyboard: Next.js upgrade affects dashboard hydration; keyboard account-menu interaction checks focused actions still work.
• A workspace member can reach flows using collapsed navigation: Next.js upgrade affects routing and hydration; collapsed-sidebar navigation checks the Flows empty state loads.
• A workspace member can skip navigation to session content: Next.js upgrade affects dashboard rendering and hydration; skip-link activation checks content focus still works.
• A workspace member can navigate toward screen discovery by arrow: Next.js upgrade affects dashboard hydration; arrow navigation checks screen-tab focus still works.
• A workspace member can preview agent usage using keyboard: Next.js upgrade affects dashboard hydration; opening Usage checks the selected screen's empty state still renders.
• A workspace member can preview where agents are working: Next.js upgrade affects dashboard hydration; opening Projects checks its empty state still renders.
• A member sees Addresses unavailable on Dev: Next.js upgrade affects page routing and rendering; opening Addresses checks its unavailable-service outcome.
• A visitor is asked to sign in for a dashboard link: Next.js runtime upgrade affects protected route handling; anonymous Sessions access checks the sign-in gate.
• A visitor can begin Google sign-in from the login page: Next.js runtime upgrade affects login rendering and navigation; Google sign-in checks the existing redirect.
• A visitor can open agent signup from the Teams page: Next.js upgrade affects route navigation; the Teams agent link checks signup routing and destination rendering.
• A visitor can find Google sign-in on the login page: Next.js runtime upgrade affects login page rendering; direct loading checks existing sign-in controls appear.
• A visitor can read the reviewer sign-in page: Next.js runtime upgrade affects route rendering; loading reviewer login checks its heading and sign-in control.
• A visitor can see both signup options on the Teams page: Next.js runtime upgrade affects public page rendering; loading Teams checks its heading and signup links.
• A visitor gets not found at the retired Flows onboarding URL: Next.js runtime upgrade affects unmatched route handling; the retired onboarding URL checks not-found rendering.
• A visitor is asked to sign in for desktop setup: Next.js runtime upgrade affects route handling; anonymous desktop setup checks the existing Google redirect.
• A visitor is asked to sign in to approve a device: Next.js upgrade affects device page rendering and hydration; anonymous code submission checks the sign-in gate.
• A visitor is sent to Google from Flows 'Try Free': Next.js upgrade affects routing and page hydration; the Flows Try Free link checks navigation to Google sign-in.
• A visitor is sent to Google from Teams sign up: Next.js upgrade affects routing and page hydration; Teams signup checks navigation to Google sign-in.
• A visitor sees a device code prefilled from the link: Next.js runtime upgrade affects query-bearing page loads; the device URL checks code prefill and page rendering.
• A visitor sees an expired session message on login: Next.js runtime upgrade affects query-bearing login loads; authError checks the expired-session message renders.
• A visitor sees 'Invite not found' for a bad invite link: Next.js runtime upgrade affects dynamic route loading; an invalid invite checks the existing error outcome.
• A visitor sees the invite notice on login: Next.js runtime upgrade affects query-bearing login loads; invite_token checks the invitation notice renders.
• A visitor sees the reviewer wrong-password message: Next.js runtime upgrade affects query-bearing route loads; reviewer error=invalid checks error-message rendering.
• A visitor can copy the Flows setup prompt: Next.js upgrade affects signup rendering and hydration; Flows prompt copying checks the interactive success state.
• A visitor can copy the Teams setup prompt: Next.js upgrade affects signup rendering and hydration; Teams prompt copying checks the interactive success state.
• A visitor can see the five Teams signup steps: Next.js upgrade affects signup rendering and hydration; expanding setup details checks steps and session data.
• A visitor can start a new signup session: Next.js upgrade affects signup hydration; starting a new session checks the displayed session ID still updates.
• A visitor sees Flows signup needs terminal access: Next.js upgrade affects signup rendering and hydration; waiting for readiness checks terminal-access status appears.
• A reviewer can open the Flows deploy onboarding: Next.js runtime upgrade affects authenticated route loading; opening deploy checks onboarding still renders.
• A reviewer can open the invite dialog without sending: Next.js upgrade affects settings rendering and hydration; opening Invite member checks the dialog still works.
• A reviewer can sign in with the reviewer password: Next.js runtime upgrade affects login and routing; reviewer sign-in checks authenticated dashboard arrival.
• A reviewer gets 'code not found' for an unknown device code: Next.js upgrade affects device page hydration; authenticated code submission checks the not-found error renders.

Recent verification history

Commit	Result	Started
036bb5ba3bd1	Timed out	2026-10-30 01:54 UTC
036bb5ba3bd1	Blocked	2026-10-30 01:47 UTC
f345a4815319	Blocked	2026-10-29 23:38 UTC

[chatgpt-codex-connector]

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-29T23:39:56.282856Z	f345a48	Draft marked ready

ℹ️ 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.

[devin-ai-integration]

Devin Review found 1 potential issue.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: f345a48153

ℹ️ 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".

[github-actions]

Preview deployed!

Environment	URL
Web	https://b4a23c20-agentrelay-web.agent-workforce.workers.dev

This is a Cloudflare Workers preview version of this PR's build.