Windows: `ocx service start` throws WindowsSchtasksError when the task is missing, and `ocx service install` aborts because the Get-ScheduledTask state probe exceeds the 1000 ms cap

Aperta
#9,038 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
28/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
bun, powershell, typescript
Ambito
cli, devops

Direzione di ricerca

Start in src/service/windows-ops.ts around startWindows() (line 859), where schtasks /run runs without checking task existence, then read src/service/windows-checked-stop.ts near line 411 and the managerState cap in src/service/windows-stop-budget.ts line 24. Done means start reports 'service not installed' for a missing task and a slow but successful state probe is no longer classified as evidence-unreadable. The UAC fallback path needs a design decision, so this is not a good first pick.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

bug cli platform service
Client or integration

Codex CLI

Area

Service lifecycle

Summary

Two related Windows bugs, both hit while installing the service without administrator rights
(Task Scheduler backend, not --native):

  1. ocx service start crashes instead of reporting "not installed". startWindows()
    (src/service/windows-ops.ts:859) runs schtasks /run /tn opencodex-proxy without first checking
    that the task exists. On a machine where a previous install was rolled back, the task is gone, so
    schtasks exits 1 and the CLI dies with WindowsSchtasksError ... reason: "other" — a dead end,
    with no hint that ocx service install is what is needed.

  2. ocx service install (scheduler backend) then aborts with
    "The installed Windows service could not be proven stopped (unknown) / the stop could not be
    verified (evidence-unreadable)". The stopped-state probe shells out to
    Get-ScheduledTask -TaskName opencodex-proxy -TaskPath '\', which on this machine takes
    944–1786 ms, above WINDOWS_STOP_CAPS.managerState = 1_000
    (src/service/windows-stop-budget.ts:24). windows-checked-stop.ts:411 maps that timeout to
    finish("unknown", "evidence-unreadable", ...), so a successful but slow query is treated as
    unreadable evidence. The run then falls into the elevated fallback, which opens a UAC prompt
    (consent.exe) that nobody answers in a non-interactive context and hangs.

Expected instead:

  • ocx service start should detect the task is absent and either install/register it or say
    service not installed — run ocx service install, never a raw schtasks exception.
  • A state probe that answers correctly but slower than 1 s should not be classified as
    evidence-unreadable (or the cap should be raised / the probe replaced by a cheaper call).
  • The elevated fallback should be opt-in or time-boxed, not entered automatically.
Reproduction

Environment: Windows 11, no admin rights, @bitkyc08/opencodex 2.100.6 installed globally with npm;
bundled Bun runtime (Bun 1.4.4). No prior service installed (previous install was rolled back, so
~/.opencodex/service-state.json is absent and the task does not exist).

  1. Confirm the task is gone:

    schtasks /query /tn opencodex-proxy

    ERROR: The system cannot find the file specified.

  2. Try to install the service as a normal user:

    ocx service install

    → "The installed Windows service could not be proven stopped (unknown)"

    → "The Windows service or process state could not be read (the stop could not be verified)"

    → internal elevated retry spawns a UAC prompt (consent.exe) that never completes.

  3. Try to start it:

    ocx service start

    → WindowsSchtasksError: Task Scheduler command failed (exit code 1): schtasks /run /tn opencodex-proxy

    operation: "run", reason: "other", code: "WINDOWS_SCHTASKS_ERROR"

  4. Measure the probe that feeds the 1000 ms cap:

    powershell -NoProfile -Command "(Measure-Command { Get-ScheduledTask -TaskName 'opencodex-proxy' -TaskPath '' }).TotalMilliseconds"

    1786 / 944 / 979 ms across three runs

    For comparison, the process snapshot the same path uses is fast:

    powershell -NoProfile -Command "(Measure-Command { Get-CimInstance Win32_Process }).TotalMilliseconds"

    489 ms

Consistency: reproducible every time on this machine while the task is absent. Creating and running a
scheduled task itself works fine without elevation (schtasks /create ... : exit 0,
schtasks /run ... : exit 0), so it is not a permissions problem on this box.

Workaround that got it working locally (uses the package's own code, no patches to node_modules):
generate the assets with writeWindowsSchedulerAssets(runtime) + writeServiceInstallState("scheduler", ...),
register the generated opencodex-service-task.xml with schtasks /create /xml, then ocx service start.
After that, ocx service status and ocx service start both work.

Version

2.100.6 (npm global: @bitkyc08/opencodex)

Operating system

Windows 11, build 10.0.26200.9974 (x64), standard user (no administrator rights), Bun 1.4.4 bundled

Provider and model

N/A — not provider-specific. The failure happens in service management before any model request is made.

Logs or error output
C:\Users\javie>ocx service start
456 |   if (error instanceof WindowsSchtasksError) return error;
457 |   const operation = schtasksOperationFromArgs(args);
458 |   const reason: WindowsSchtasksFailureReason = isWindowsSchtasksAccessDeniedError(error, args, taskPresent)
459 |     ? "access-denied"
460 |     : "other";
461 |   return new WindowsSchtasksError(operation, reason, formatWindowsSchtasksError(error, args, taskPresent));
               ^
WindowsSchtasksError: Task Scheduler command failed (exit code 1): schtasks /run /tn opencodex-proxy
 operation: "run",
    reason: "other",
      code: "WINDOWS_SCHTASKS_ERROR"

      at toWindowsSchtasksError (C:\Users\javie\AppData\Roaming\npm\node_modules\@bitkyc08\opencodex\src\lib\windows-elevation.ts:461:10)
      at schtasks (C:\Users\javie\AppData\Roaming\npm\node_modules\@bitkyc08\opencodex\src\service\windows-scheduler.ts:121:11)
      at startWindows (C:\Users\javie\AppData\Roaming\npm\node_modules\@bitkyc08\opencodex\src\service\windows-ops.ts:859:40)
      at <anonymous> (C:\Users\javie\AppData\Roaming\npm\node_modules\@bitkyc08\opencodex\src\service\cli.ts:396:11)
      at withWindowsServiceMutationLock (C:\Users\javie\AppData\Roaming\npm\node_modules\@bitkyc08\opencodex\src\lib\windows-service-mutation-lock.ts:110:22)
      at serviceCommand (C:\Users\javie\AppData\Roaming\npm\node_modules\@bitkyc08\opencodex\src\service\cli.ts:555:11)
      at <anonymous> (C:\Users\javie\AppData\Roaming\npm\node_modules\@bitkyc08\opencodex\src\cli\dispatch.ts:598:16)
      at dispatchCommand (C:\Users\javie\AppData\Roaming\npm\node_modules\@bitkyc08\opencodex\src\cli\dispatch.ts:1155:16)
      at C:\Users\javie\AppData\Roaming\npm\node_modules\@bitkyc08\opencodex\src\cli\index.ts:1960:20

Bun v1.4.4 (Windows x64)

--- install-time failure (retyped from console output, no task existed at that point) ---
The installed Windows service could not be proven stopped (unknown)
The Windows service or process state could not be read (the stop could not be verified)

--- evidence for the 1000 ms cap ---
src/service/windows-stop-budget.ts:24:  managerState: 1_000,
src/service/windows-checked-stop.ts:411: if (unreadable) return finish("unknown", "evidence-unreadable", "the stop could not be verified")
Get-ScheduledTask -TaskName 'opencodex-proxy' -TaskPath '\'  ->  1786 ms / 944 ms / 979 ms
Screenshots and supporting files

No response

Redacted configuration
No provider or routing configuration is involved. Relevant on-disk state only:

- `~/.opencodex/service-state.json` is **absent** after the failed install, which is why
  `ocx service status` reports "not installed" even when the Task Scheduler entry still exists.
- Backend requested: Task Scheduler (default). Runtime: bundled Bun (`durableBunRuntime()`).
- Generated task (registered manually as a workaround) contains:
  - `LogonTrigger` + `SessionStateChangeTrigger` (RemoteConnect, SessionUnlock, ConsoleConnect), `Enabled=true`
  - `ExecutionTimeLimit=PT0S`
  - action: `wscript.exe /b /nologo "<home>\.opencodex\opencodex-service-launcher.vbs"`
- No tokens, account identifiers or request credentials are included in this report.
Checks
  • I searched existing issues and documentation.
  • I removed secrets, tokens, account details, request credentials, and personal data.
Lingua principale
TypeScript
Stelle
16.9k
Fork
1.3k
Merge medio
1g 2h
PR unite (30g)
844

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di lidge-jun/opencodex

Tutte le issue di lidge-jun/opencodex

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.