[Bug]: worker-start --agent omp fails at agent_readiness: OMP 18.4 idle title "π > dir" is not recognised as idle #24068

Activity

1. drakeo338

   added a commit that references this issue on Oct 2, 2026

   fix(runtime): treat Pi/OMP state-marker idle title as idle for termin…

   ...

   This issue will close once commit c772f96 is merged into the 'main' branch.

   c772f96
2. ElvezPelvez commented on Oct 2, 2026

   

   ElvezPelvez

   on Oct 2, 2026

   More actions

   Additional measurements on macOS (Orca 1.4.218, OMP 18.4.12), in case they help #24111 / #24113 / #24196.

   1. Startup readiness has no hook signal, only the title. In the managed extension that Orca 1.4.218 ships (orca-agent-status.ts), the status session_start handler is empty (onStatus('session_start', () => {})). The second session_start handler only applies ORCA_OMP_PREFILL. So a freshly started OMP posts nothing until its first agent_start, and terminal wait --for tui-idle depends on the title alone. With OMP 18.4's π > <dir> / OMP > <dir> idle title it never settles:

   orca terminal create --worktree active --command "omp" --json      # idle at its prompt within seconds
   orca terminal wait --terminal <h> --for tui-idle --timeout-ms 60000 --json
   # -> timeout after 61 s, same with `omp --profile <p>`
   

   2. After a prompt, hook status mostly arrives, but not in every worktree. Loop: create an OMP terminal in a worktree, send Reply with exactly: ok, wait 20 s, then look for an agents[] entry whose paneKey starts with the terminal's tabId in orca worktree ps --json.

   worktree	result
   main checkout (two repos), plain omp and omp --profile <p>	entry present (omp, done)
   fresh linked worktrees: --no-parent, --parent-worktree, and --issue N --parent-worktree	entry present
   linked worktree with an orchestration-dispatched OMP worker already running	entry present
   another linked worktree with a dispatched OMP worker that had finished its work	no entry, 2/2 runs

   In the failing worktree the probe's OMP status line showed (sub), and it did process the prompt. Separately, the dispatched OMP workers' own panes (started via terminal create --command "omp --profile <p> …", so --extension …/orca-agent-status.ts is injected, as ps confirms) never appear in agents[] while working, although the worktree's status reads working. If OMP treats those sessions as child sessions, the "exclude child extensions from root status reporting" part of #24196 may be the relevant change. That is an inference; we did not instrument the extension.
3. brennanb2025

   closed this as completedin #24295on Oct 2, 2026
4. YosukeIida

   added a commit that references this issue on Oct 15, 2026

   chore(homebrew): omp の 18.3.4 pin を外す（gpt-6.1-sol を使うため）

   ...

   01cd52d