GreatEugenius commented on code in PR #918: URL: https://github.com/apache/flink-agents/pull/918#discussion_r3655725587
########## dev/agent-skills/flink-agents-dev/references/platforms/codex.md: ########## @@ -0,0 +1,110 @@ +# Codex Interaction Adapter + +Use this adapter only when explicit host context identifies Codex. + +## Capability Check + +The current session and mode's tool contract is authoritative. Codex exposes its +native closed-choice UI through `request_user_input` in Plan mode. Before the first +decision gate, check the explicit collaboration mode and the available tool +contract. + +When the session is not in Plan mode, respond with one short message in the user's Review Comment: **Make Codex interaction capability-driven and keep the policy authoritative in one place.** I tested this flow on a Codex surface where `/plan` was not an available user command. The adapter stopped the task and requested a mode switch even though the generic numbered fallback could have continued. Could we make the current tool contract the only capability signal? - If `request_user_input` is currently exposed and callable, use it. - Otherwise, immediately use the generic numbered fallback. - Do not require `/plan`, `Shift+Tab`, or a Plan-to-Default handoff. The mode and fallback sequence is currently defined in `SKILL.md`, `application-patterns.md`, and `platforms/codex.md`. Could we keep the portable rule authoritative in one place and have the other files reference it? Otherwise, changing only one copy may leave the Skill with inconsistent instructions. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
