Commit Graph
5 Commits
Author SHA1 Message Date
Felipe Coury bbf656dcf3 feat(tui): preselect suggested permission scope
Thread `suggestedScope` through the app-server permission approval
request and use it when constructing TUI approval requests. This
keeps the protocol backward compatible by defaulting the field to
`turn` when older clients omit it.

Add focused app-server and TUI coverage, plus a snapshot for the
session-suggested approval overlay so reviewers can see the
preselected session row.
2026-04-13 13:15:18 -03:00
Felipe Coury 097f431a88 feat(app-server): gate narrow permission requests by capability
Gate the `request_permissions` tool and the app-server request delivery path
on the surface capability handshake from `initialize`. The server now only
emits narrow permission approval requests to subscribed connections that
explicitly advertised support.

Keep the preset flow out of this branch so the review stays focused on one
transport path. Until the preset picker branch lands, app-server surfaces
continue to hide `request_permission_preset` even if they advertise the
future capability.
2026-04-12 21:57:21 -03:00
Jack Mousseau 7a6e30b55b Use request permission profile in app server (#14665) 2026-03-16 10:12:23 -07:00
Dylan HurdandCodex d241dc598c feat(core) Persist request_permission data across turns (#14009)
## Summary
request_permissions flows should support persisting results for the
session.

Open Question: Still deciding if we need within-turn approvals - this
adds complexity but I could see it being useful

## Testing
- [x] Updated unit tests

---------

Co-authored-by: Codex <noreply@openai.com>
2026-03-09 14:36:38 -07:00
Jack Mousseau e6b93841c5 Add request permissions tool (#13092)
Adds a built-in `request_permissions` tool and wires it through the
Codex core, protocol, and app-server layers so a running turn can ask
the client for additional permissions instead of relying on a static
session policy.

The new flow emits a `RequestPermissions` event from core, tracks the
pending request by call ID, forwards it through app-server v2 as an
`item/permissions/requestApproval` request, and resumes the tool call
once the client returns an approved subset of the requested permission
profile.
2026-03-08 20:23:06 -07:00