Repository navigation
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What was changed
This draft is intended to replace #270. It starts with the reviewed design and an executed proof; production plugin code and dependencies are unchanged. Keep #270 open until the replacement is implemented and ready.
The proposed implementation keeps #270's clone-free runner and native
agent.asTool()objects. Two supported upstream runtime hooks, at effective run-configuration consumption and actual model resolution, replace its three prototype interceptions and tool-source registry. A bundle check rejects SDK copies without the contract.The design under
typescript/openai-agents/design/runtime-policy/contains the developer-experience and maintenance comparisons and a self-contained runnable proof. Generated histories and logs are written under an ignored results directory; the dependency and plugin prototype edits are encoded once inprepare.py. Successful application code keeps the same native declarations and Temporal setup. Some unsupported nested configurations fail later, as tool output after the parent model Activity.Why?
#270's review/rework loop repeatedly found another path around Activity dispatch as validation moved between SDK hooks. The remaining duplicate-SDK cases ran models inside the Workflow and repeated them during replay. The prototype blocks those paths while retaining the original native tool objects and their approvals, guardrails and handlers.
Related issues this replacement is intended to fix:
This draft does not close these issues yet.
Checklist