feat: support Foundry hosted Harness v2 agents - #1
Merged
Merged
Conversation
Signed-off-by: Sertac Ozercan <sozercan@gmail.com>
Signed-off-by: Sertac Ozercan <sozercan@gmail.com>
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 57988dbe9d
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "Codex (@codex) review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "Codex (@codex) address that feedback".
This was referenced Sep 8, 2026
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
1 participant
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.
Add optional ACP, lifecycle broker, hosted supervisor and gateway modes for Orka's Harness v2 contract. Keep the existing Harness v1 adapter and provider-static schema mode. Tools and artifact access remain governed by Orka; Azure credentials and provider session identities stay within the adapter deployment.
Persist remote ownership before submission, validate exact lease and runtime fences, and retain uncertain acknowledgments without replay. Durable storage failures close admission and take precedence over successful-looking responses. Reject conflicting JSON aliases before accepting ownership evidence or executing provider tool output, while preserving case-sensitive tool arguments. Confirm original-owner settlement and retirement before replacing a hosted lifetime.
The final source passed
make verifyand the full native Linux/amd64 suite,go test -race -count=1 -timeout=8m -v ./...: 269 top-level tests and 776 subtests, with no skips or race reports.The current hosted images passed Orka conformance, governed write cancellation before effect, ordinary Task/Session cleanup, authenticated empty drain, and original hosted-runtime retirement. The cancellation case recorded zero fixture writes and retained the original one-attempt
OutcomeUnknowneffect. Real-model Task cancellation, real-model timeout, cancellation after effect, and model stream loss are still pending.Earlier hosted deployments exercised text, same-Session continuation, governed read/write tools, authorization and fence rejection, lease renewal, and original-owner retirement. Those results retain their original image and runtime scope. Earlier failed or inconclusive cases and unresolved owners remain recorded. A fresh hosted lifetime passed ordinary AgentRuntime deletion and cleanup-Secret removal while its original endpoint remained live. Its warm-up model Task succeeded, but an exact-text assertion failed before cancellation was attempted. That scenario remains failed.
This remains an experimental single-lifetime package with an approximately 30-minute hosted connection limit. It does not reconnect or resume across boots. Interactive approvals and ACP filesystem, terminal, session-load and media methods are unsupported. The tested composition does not support positive repository editing/publication; generic stateful or SSE MCP transports are outside the supported Orka loopback proxy contract. Task cancellation and socket closure do not prove that Azure inference stopped.