Skip to content

fix(app-control): validate app field type before case-fold#30089

Merged
siddseethepalli merged 1 commit into
mainfrom
swarm/43fc/task-216
May 9, 2026
Merged

fix(app-control): validate app field type before case-fold#30089
siddseethepalli merged 1 commit into
mainfrom
swarm/43fc/task-216

Conversation

@siddseethepalli
Copy link
Copy Markdown
Contributor

Address Codex P1 from #29592: non-start app-control tool input reaches checkNonStartAuthorization via an unchecked as unknown as HostAppControlInput cast (conversation-surfaces.ts:2067), so a non-string app payload would throw TypeError at .toLowerCase(). Replace the null-check with a typeof requestedApp !== 'string' guard so malformed input produces a controlled isError response.

Devin's stop-ownership note is intentional/no-op (idempotent stop confirmed in #30086).

Codex P1 on PR #29592: non-start tool input is cast through 'as unknown
as HostAppControlInput' without runtime validation in conversation-surfaces,
so a malformed payload with a non-string 'app' (number, object, etc.)
would throw a TypeError at requestedApp.toLowerCase() and abort the tool
flow instead of returning a controlled isError response.

Tighten the guard from a null-check to a typeof check so non-string
values produce the same controlled rejection as a missing field.
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