Eric Traut b588812e8c Use server-authoritative permissions in the TUI (#49472) ...

## Why

Client permission definitions and constraints can differ from those on the connected app server. Accepted permission changes also need to survive task transitions before their settings notifications arrive.

## What changed

- Discover permission profiles and availability from the connected server and apply selections through `thread/settings/update`, including custom profiles.
- Adopt the server's effective permission settings instead of reapplying local definitions or constraints.
- Retain accepted selections and effective approval settings across new tasks, forks, side conversations, directory changes, reconnects, and safety retries without blocking navigation on a settings notification.
- Recognize the current built-in permission preset when the server supplies an unnamed profile.

## Testing

Add regression coverage for conflicting client/server profile definitions, rejected and unchanged selections, consecutive requests with omitted approval settings, and permission carryover before confirmation. Extend discovery and menu tests to verify server-provided availability and unnamed-profile highlighting.

GitOrigin-RevId: bcd767b58dc92dc4f945189078e51e6e5fce6d24

2026-09-30 03:33:19 +00:00

..

assets

Remove follow-up prompt suggestions from the TUI (#48621)

2026-09-27 05:29:53 +00:00

src

Use server-authoritative permissions in the TUI (#49472)

2026-09-30 03:33:19 +00:00

tests

Honor app-server provider defaults in the TUI (#49161)

2026-09-29 04:17:32 +00:00

BUILD.bazel

Add an animated Codex logo to fresh conversations and onboarding (#46752)

2026-09-20 03:02:48 +00:00

Cargo.toml

Disable unused default dependency features (#47088)

2026-09-21 18:58:55 +00:00

styles.md

Standardize TUI menu description wording and punctuation (#47329)

2026-09-22 17:58:37 +00:00