Repository navigation
feat: add cloud runtime client and image - #113
Merged
Merged
Conversation
jefft72
force-pushed
the
codex/cloud-runtime-client-image
branch
from
August 24, 2026 23:47
7b33139 to
9fa50cb
Compare
Reject cleartext cloud API and attachment URLs outside explicit loopback development hosts so bearer credentials and one-time runtime tickets cannot be exposed by configuration drift or a malformed control-plane response.
jefft72
force-pushed
the
codex/cloud-runtime-client-image
branch
from
August 24, 2026 23:51
9fa50cb to
e60daa8
Compare
Include the root TypeScript base configuration in the runtime image build context so workspace package builds can resolve their shared compiler settings inside the Docker build stage.
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.
Summary
Adds the typed cloud control-plane client and immutable runtime image release path for hosted Diffex sessions. Clients can create, list, inspect, attach to, stop, and delete sessions, while each connection obtains a fresh one-time attachment URL and validates the returned native protocol version.
Reasoning
REST lifecycle operations and the native WebSocket protocol have separate trust boundaries. The client therefore validates strict response shapes, requires HTTPS and WSS outside explicit loopback development hosts, and rejects protocol mismatches before streaming so browser bearer credentials and one-time tickets cannot leak through configuration drift.
Changes
Testing