You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Supported per-session isolated Codex home for local-only capture (Orca 1.4.224)
#39712
Supported isolated Codex-state launch for local-only capture
Orca 1.4.224, Windows; local-only Entire capture must remain disabled until isolation is proven.
What supported native per-session launch binds one NEW Codex session and its children to an independent provider home and independent Git repository while retaining an already authorized account, without copying auth files, changing machine-wide active-account/profile/environment settings, or importing existing sessions?
The installed worker-start/terminal interfaces inspected do not advertise that binding. Official Codex/account docs describe account-scoped homes and new launches following the active account. The current settings docs also describe cross-account history sharing enabled by default. Which settings and supported launch contract guarantee no old history reads/copies/shares and no impact on other sessions? Please distinguish current docs from version 1.4.224 and identify a supported version/change if necessary.
Please provide command/API/UI contract, precedence, credential-reference behavior, child-process binding and readback/rollback. We are not asking to upload/import any history, credentials or sessions.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Supported isolated Codex-state launch for local-only capture
Orca 1.4.224, Windows; local-only Entire capture must remain disabled until isolation is proven.
What supported native per-session launch binds one NEW Codex session and its children to an independent provider home and independent Git repository while retaining an already authorized account, without copying auth files, changing machine-wide active-account/profile/environment settings, or importing existing sessions?
The installed worker-start/terminal interfaces inspected do not advertise that binding. Official Codex/account docs describe account-scoped homes and new launches following the active account. The current settings docs also describe cross-account history sharing enabled by default. Which settings and supported launch contract guarantee no old history reads/copies/shares and no impact on other sessions? Please distinguish current docs from version 1.4.224 and identify a supported version/change if necessary.
Please provide command/API/UI contract, precedence, credential-reference behavior, child-process binding and readback/rollback. We are not asking to upload/import any history, credentials or sessions.
References: https://www.onorca.dev/docs/agents/codex ; https://www.onorca.dev/docs/settings
All reactions