Repository navigation
runtime client: preserve canonical HOME and native SSH login context #214
Description
The public runtime client does not reliably preserve the native login environment: it forwards an arbitrary caller HOME (or omits HOME when absent) and discards SSH session markers. This can make the native CLI consult a different login context from the operator's working session.
Confirmed source behavior at main c2c9d4d:
- A provider-free environment regression with caller HOME omitted has no HOME in the projected environment.
- A temporary caller HOME is forwarded instead of the OS account home.
- SSH_CONNECTION, SSH_CLIENT and SSH_TTY are dropped. No credential values are involved in these fixtures.
Separately, an authorized installed agent-collab 7.0.6 / runtime 5.0.7 intent request on macOS x86_64 returned native ERROR with authentication failed or timed out, zero turns/tokens, one process attempt and confirmed cleanup after about 61 seconds. The operator reports a working native CLI. The shell HOME already matched the OS account home, so an ephemeral HOME is not established as the cause of that specific call. Native model inventory in the SSH session also reported an authentication requirement; it inherited session markers that the installed client strips. Host/session equivalence with the working terminal remains unresolved. This is not provider downtime or proof that the operator is signed out.
Installed manifest SHA-256: a11571908933c48fc301838d1cdb5d5f71433924af5b4b8419fd7b658695f440.
Wire SHA-256: a675807e0ff5f0544d7cc9d659914ce2dadac9be8efd0fb56635815e5c3e842a.
Request shape: one context.documents.intent unit, standard quality/effort, max_parallel=1, dispatch_requested=true, no dependencies or cwd override, opaque task-comparison text. Installed coordinator used EOF-delimited stdin with no PTY and no shorter outer timeout. Request ID: 3b076246-4a51-4543-8541-caf4c0e41540.
A prepared source fix resolves HOME from the OS account and preserves SSH session markers while keeping credentials and agent sockets out of the projected environment. It preserves existing native configuration locations and introduces no copied profiles, provider-specific launcher, or new authentication machinery. Native qualification and publication remain pending. Related #208 concerns a distinct pre-dispatch selection stage; do not merge its failure classification with this native result.
Activity
sumitake commentedon Sep 15, 2026
Additive host clarification: the operator confirmed that the working native AGY session is on a different Mac from the Intel host running the recorded probe. Therefore the zero-turn authentication result cannot be attributed to canonical HOME or SSH-marker handling alone, and is not evidence of provider downtime. The client environment defects remain independently reproduced by source tests and are fixed in draft PR #215; source changes are not yet installed. A fresh limited-purpose native validation session is authorized and pending access to the working host. No credentials or native login settings were changed.
sumitake commentedon Sep 16, 2026
Additional LabMac evidence from the authorized release qualification task (2026-09-16 UTC). Installed plugin 7.0.6, runtime 5.0.7; manifest digest
a11571908933c48fc301838d1cdb5d5f71433924af5b4b8419fd7b658695f440.A provider-free
context.documents.intentplanning request selectedgemini/context.documents. One live request86d75d59-6eea-4eaf-aada-e83a2b352809through the same installed coordinator returned nativeauthentication failed or timed out, blank conversation/response, zero reported turns/tokens,execution_status=provider_error, return code 1 andcleanup_confirmed=true; observed attempts 1, replay count 0. Overall client status wasok, which was not treated as successful provider execution. Observation persistence separately reportedobservation_write_failed: PermissionError.Caller: Codex Desktop remote LabMac x86_64 session under its ordinary filesystem sandbox. Request used standard quality/effort, one intent work unit, current wire digest, pipes and EOF, no PTY or alternate provider command. No credentials were changed or searched, and the consumed request was not replayed. This observation does not isolate authentication from caller context and does not assess the uninstalled PR 215 candidate. The previously reported original LabMac authentication cause remains unproven.
sumitake commentedon Sep 16, 2026
Follow-up on installed agent-collab 7.0.6 / runtime 5.0.7, Intel macOS: an explicitly authorized fresh Gemini repository-plan review through the normal coordinator also returned
authentication failed or timed outwhen run in approved native host execution outside the incompatible caller sandbox. The provider's own sandbox remained enabled.Request
0fc053a0-780e-484d-97fb-b618e54303fb,review.repository, explicit Gemini, frontier/maximum, one device/inode-bound sealed repository. Manifesta11571908933c48fc301838d1cdb5d5f71433924af5b4b8419fd7b658695f440. One attempt, zero replay, about 61 seconds, zero turns/tokens, blank native conversation/response, returncode 1 and confirmed cleanup. The native error bytes were preserved; the shim's outerokdoes not constitute task success.This rules out an outer-sandbox initialization failure as a sufficient explanation for this fresh attempt; it does not identify the authentication cause, establish a provider outage, or qualify the unreleased canonical-HOME/SSH fix. No credentials, login profiles, settings, installed bytes or native permissions were changed. No replay is planned.
sumitake commentedon Oct 19, 2026
Verified source-defect closeout against current public main
fa79ada3266662cc678e757d816ec7fb722c3d71:495517678edbd7069fe82fa4a6ec4a8d9f8ce513; it shipped in v7.0.7 (tag commit645f74c04c2f8374006c5ba2183ba398e30ad683).runtime_client.py::_scrubbed_envstill resolves HOME throughpwd.getpwuid(os.getuid()).pw_dir, preserves SSH_CONNECTION/SSH_CLIENT/SSH_TTY, and does not forward SSH_AUTH_SOCK or credential values. Relative to v7.0.7, this file differs only in the runtime version pin; the environment regression test file is unchanged.python3 -m unittest discover -s tests -p test_runtime_client_configuration_environment.py -vpassed all 4 tests (import portability, SSH context without agent forwarding, canonical account HOME, and native configuration/catalog locations).Closing the reproduced client-environment defect as shipped. This does not claim native authentication works on every host or attribute the historical native authentication failures to HOME. The separate early Agy authentication/startup diagnostics and native sign-in work remain tracked in #233; consumed provider calls are preserved and were not replayed for this closeout.