Repository navigation
Gemini exits before first turn in ~1.7s with ambiguous authentication/startup error (7.0.8 / runtime 5.0.9) #233
Description
Observed failure
One authorized read-only review.repository invocation explicitly targeting Gemini returned provider_error before its first model turn.
- Installed plugin: 7.0.8; signed runtime: 5.0.9, macOS x86_64.
- Selected carrier:
gemini/advisory.repository. - Native process duration: 1,723 ms; aggregate duration: 1,754 ms.
- Native exit code: 1, cleanup confirmed.
- Native result:
ERROR,authentication failed or timed out, empty conversation ID, zero reported turns/input/output tokens. - Request ID:
f5c1c102-21cd-4c8b-9da3-6dd02396fac0. - Installed manifest matches the result's manifest digest. No review verdict or response-scoped model identity was returned.
The private review payload, application identity, credentials and runtime data are deliberately omitted.
Investigation result
The caller used the normal installed coordinator, EOF-delimited JSON, non-PTY stdin and no outer timeout. Its initial 1,000 ms execution-tool yield did not cancel the process; the caller later collected completion. Runtime remaining deadline was 86,397,999 ms. The client transported the complete native error successfully; its outer status=ok is not a successful review.
Checked installed package source:
coordinator.py:374-393: EOF request framing;:438-442: synchronous client call before response.runtime_client.py:42,1144-1184: 24-hour default and remaining deadline forwarding.runtime_client.py:995-998: collector waits while streams are open or process is alive.runtime_client.py:1023-1035: progress-pipe EOF retains the existing lease while the response drains.runtime_client.py:1238-1242: waits for process completion with the remaining deadline.runtime_client.py:829-866: canonical OS-account HOME and native SSH context are preserved.
Supported conclusion: early native startup/authentication failure with insufficient phase diagnostics. Not established: missing credentials, caller timeout, or a confirmed startup race. The operator suspects Agy was not given sufficient startup time. That remains a plausible hypothesis for the native readiness/authentication boundary, rather than evidence that the caller stopped at its first yield.
The native adapter/authentication implementation is inside the installed compiled runtime bundle, so this bounded inspection could not distinguish terminal auth denial from transient startup readiness or identify the internal phase budget.
Related history: #214 (older HOME/SSH projection issue) and #164 (PTY noncanonical-readiness race). Neither is established as this failure: this call preserved HOME/SSH and used closed non-PTY stdin.
Requested correction and qualification
Inspect the native startup/authentication boundary. Emit bounded, nonsecret diagnostics distinguishing startup-not-ready, terminal authentication rejection and elapsed authentication timeout, including phase, elapsed time and applicable budget.
Any readiness wait should occur before prompt submission, within the original invocation. Preserve native owner/profile context, confirmed cleanup and the single-attempt/no-replay contract; do not add blind retries or copied authentication profiles.
Qualify delayed startup, terminal auth rejection and startup timeout separately. Delayed readiness must not become an immediate false authentication failure, and no model request may be replayed.
No provider replay, raw CLI workaround, credential inspection, runtime modification or live recovery test was performed during this investigation.
Activity
sumitake commentedon Oct 16, 2026
Additional investigation — October 15, 2026 (Pacific)
A separate occurrence on plugin 7.0.8, signed runtime 5.0.9, and installed agy 1.3.6 now has native-log evidence. It narrows the cause of this occurrence; it does not retroactively establish the cause of the original 1.7-second report.
Observed result
b6f8cdee-61bc-4a81-a81f-915d61358814; carriergemini/advisory.repository.authentication failed or timed out.status=okdid not mean the review succeeded.Native timeline (sanitized)
lookup oauth2.googleapis.com: no such host.A later existing native log on the same host records silent authentication starting at 23:48:42.276428 and succeeding at 23:48:50.888029 (8.612 seconds). This investigation did not initiate that invocation or replay the failed review. This proves later authentication success, not review completion. DNS resolution of the OAuth and GitHub hosts also succeeded during the subsequent read-only inspection.
Supported conclusion: this 27-second occurrence was a native token-refresh network/DNS failure, followed by native shutdown delay. It is not evidence of revoked credentials, a caller-imposed 27-second deadline, or a still-running authentication operation that the caller abandoned. Whether the earlier 1.7-second occurrence has the same cause remains unknown.
Recommended bounded correction
not authenticated/login/refresh messages as terminal while the process is alive. Use documented native timeout/readiness controls if available; the installed help exposes no separate authentication-timeout option. Increasing the overall review deadline alone does not repair this observed DNS failure.The native implementation correction belongs in the private producer and must reach this plugin through a rebuilt signed runtime release. Caller guidance and privacy-safe diagnostics can be tracked here. No runtime/source, authentication, network configuration or parent-task workspace was modified by this investigation.
sumitake commentedon Oct 19, 2026
Additional recurrence during an authorized issue-fix/release task on 2026-10-19 UTC:
f2131b3870244b9be2016cf839886deaf6c9470ff8c0d3b6b8e19a81a455b405.f5ba203b-c091-4879-b252-89e0bfa61c91, actioncontext.documents.intent, ordinary untargeted routing selectedgemini/context.documents.quality_profile=standard,effort_class=standard,max_parallel=1,dispatch_requested=true, one work unit containing a bounded document comparison. No repository restrictions or outer timeout; EOF-delimited JSON, non-PTY stdin.authentication failed or timed out.status=okdid not establish task success. Optional observation persistence also reportedobservation_write_failed/PermissionErrorunder the caller sandbox; it did not remove the native content.This is another early native authentication/startup failure with no substantive intent assessment. It does not establish credential revocation, provider outage, a short caller timeout, or the exact underlying cause. No replay, provider fallback, credential inspection, or runtime modification was performed. The raw result is retained privately; the payload is omitted here.
sumitake commentedon Oct 23, 2026
The bounded diagnostic correction is shipped: optional sanitized Agy startup/authentication/network/timeout hints preserve the original status, content, lifecycle and single-attempt behavior. Fixture regressions cover delayed success, rejection, DNS evidence, supervisor timeout and missing diagnostics; fresh staged and installed Google checks also succeeded. This closes the diagnostic correction only: the original 1.7-second event remains unexplained, and this does not claim to cure external authentication/DNS failures or authorize replay.
Published and verified: agent-collab 7.0.9, signed runtime 5.0.12. Distribution #235 and merged closeout #239 record the released scope. All 184 released files match the observed installations; bounded native checks do not guarantee future provider availability.