[Yash-Singh1]

In a new thread, clicking the context strip's permission mode opened the model selector before its permissions menu. The button now opens the shared permissions menu directly above itself, using the same supported modes, administrator restrictions, and draft change handler as the composer.

Validation: vp run check:changed passed format, lint, knip, affected typechecks, 55 focused tests, and React Compiler checks. The new browser regression test failed against the previous implementation and passes with the fix. Verified the real app in the Browser panel, including switching to Supervised and back to Full access, and captured before/after screenshots. CI passes on the current head; automated review is still completing.

Model: GPT 6.1 Sol. Harness: Codex in T3 Code.

[macroscopeapp]

Approvability

Verdict: Approved at c89e921

Macroscope's review found this PR approvable — The new-thread permissions chip now opens the existing permissions menu directly. Provider compatibility and managed-policy restrictions remain applied, with no change to default permissions.

^{You can add or adjust custom eligibility rules. Learn more.}

[coderabbitai]

Walkthrough

The context-strip permissions control now opens a runtime-mode menu. It resolves the displayed mode against supported modes and applies managed-policy denial reasons to options. ChatView supplies the mode-change callback, and ChatComposer uses the same runtime-option resolver.

Changes: Runtime mode permissions menu

Layer / File(s)	Summary
Resolve policy-aware runtime options apps/web/src/components/chat/runtimeModeConfig.ts, apps/web/src/components/chat/ChatComposer.tsx	resolveRuntimeModeOptions maps supplied modes to their configurations and adds a disabled reason when managed policy denies a mode. ChatComposer uses the helper instead of local option filtering and denial-reason mapping.
Add the context-strip permissions menu apps/web/src/components/ComposerContextPermissions.tsx, apps/web/src/components/ChatView.tsx, apps/web/src/components/chat/ComposerPermissionsSection.browser.test.tsx	ComposerContextPermissions resolves the compatible mode and renders ComposerPermissionsSection in a menu. ChatView passes supported modes and the mode-change callback. The browser test checks the menu options, mode selection, reopening, and Escape focus behavior.

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Feature

Sequence Diagram(s)

sequenceDiagram
  actor User
  participant ChatView
  participant ComposerContextPermissions
  participant ComposerPermissionsSection
  ChatView->>ComposerContextPermissions: Pass runtime mode, supported modes, and change callback
  User->>ComposerContextPermissions: Open permissions menu
  ComposerContextPermissions->>ComposerPermissionsSection: Render resolved mode and available options
  User->>ComposerPermissionsSection: Select a runtime mode
  ComposerPermissionsSection->>ChatView: Call runtime-mode change callback

Loading

Possibly related issues

• pingdotgg/t3code#29632 — This adds another runtime-mode picker entry point, but does not change draft-to-server synchronization.
• pingdotgg/t3code#6508 — This makes runtime mode editable from the new-thread context strip, but does not add project-level preference persistence.

Suggested labels: size:S

Suggested reviewers: t3dotgg, macroscopeapp

Merge Risk: Low · up to c89e9

Escape can move focus to the editor instead of the permissions trigger, disrupting keyboard navigation. The localized issue can be addressed in follow-up.

Pre-merge checks: 3 · 1

Failed checks: 1 warning

Check name	Status	Explanation	Resolution
Description check		The description clearly explains the problem, change, and verification. It does not provide the required scope and approval information. It also mentions screenshots without embedding or linking them,…	Add a Scope and approval section with the linked issue or maintainer approval, or explain why this focused fix qualifies for an exemption. Embed or link the before/after screenshots. Clarify whether the browser regression test was run and s…

Passed checks: 3 passed

Check name	Status	Explanation
Title check		The title names the main change: the new thread context strip now opens the full permissions menu directly. The changeset adds ComposerContextPermissions menu behavior, runtime mode option resolution,…
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: Title check

Explanation

The title names the main change: the new thread context strip now opens the full permissions menu directly. The changeset adds ComposerContextPermissions menu behavior, runtime mode option resolution, and a browser test for that flow. The title is a conventional commit in plain language and fits the diff. "Full access" is a specific mode name, and the menu also offers other supported modes, so the title is slightly narrower than the feature but still accurate.

Full details: Description check

Explanation

The description clearly explains the problem, change, and verification. It does not provide the required scope and approval information. It also mentions screenshots without embedding or linking them, and it conflicts with the objective stating that the browser test was not run.

Resolution

Add a Scope and approval section with the linked issue or maintainer approval, or explain why this focused fix qualifies for an exemption. Embed or link the before/after screenshots. Clarify whether the browser regression test was run and state its actual result.

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

Tip

🎯 Customize your risk assessments

Guide how CodeRabbit assesses merge risk and security architecture risk. Highlight sensitive changes and explain your security boundaries using Merge Risk Instructions and Security Risk Instructions in your review settings. Security architecture risk assessments require the Advanced plan or above.

✅ Automatic approvals, with your rules

Let CodeRabbit approve pull requests once required threads are resolved, pre-merge checks pass, and your risk limits are met. Enable Automatic approvals in review settings, with overrides for teams or file paths.

CodeRabbit Verify

• Run CodeRabbit Verify to test the changes in this pull request.

Recent review info

Run configuration

• Source mode: Auto
• Repository: pingdotgg/t3code
• Branch: t3/direct-full-access-menu
• File: .coderabbit.config.ts
• Commit: c89e921
• Layers: Repository TS config
• Review profile: CHILL
• Plan: Team
• Run ID: 773fdf1b-75bb-4e4c-8542-65f8f13ddd27

Commits

Reviewing files that changed from the base of the PR and between 12ec17c and c89e921.

Files selected for processing: 5

• apps/web/src/components/ChatView.tsx
• apps/web/src/components/ComposerContextPermissions.tsx
• apps/web/src/components/chat/ChatComposer.tsx
• apps/web/src/components/chat/ComposerPermissionsSection.browser.test.tsx
• apps/web/src/components/chat/runtimeModeConfig.ts

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 9 remain after this review.

[coderabbitai]

• Fix comments: Fix CodeRabbit comments on this PR