Agent terminal never executes commands — shell integration (cmdCap) never activates in sandbox-wrapped temporary terminals (Linux/Fedora)

Bug Reports
, ,
1

Environment: Qoder 1.21.2 (VSCode 1.106.3), Linux x64, Fedora 44 (kernel 7.1.5), bubblewrap 0.11.0, bash.

Symptom: Every agent run_in_terminal call fails with Timed out waiting for (a new) terminal prompt after interrupting residual/existing input (5000ms). No command ever executes — verified with a file-creation probe that never appears. User-spawned integrated terminals work normally.

Log evidence (~/.config/Qoder/logs/<session>/window1/agent.*.log):

  • [Terminal] Creating terminal with resolved context: ... shell=/usr/bin/bash — PTY spawns cleanly (ptyhost: all exits exitCode: 0)
  • [Terminal] Waiting for cmdCap: isRemote=false, processReadyTimeout=5000ms, capabilityTimeout=5000ms — never resolves, no capability-arrived line anywhere in the session
  • [RichExecuteStrategy] Executing command line: ... — command text is sent, but without cmdCap completion is never detected; terminal is disposed with reason=execution-strategy-error
  • Zero successful executions across the whole session, from the very first call — this is not state poisoning
  • [LinuxSandbox] bwrap is available / [Terminal] Sandbox wrapper initialized for platform: 3 — agent terminals are spawned through the sandbox wrapper; standalone bwrap --bind / / --dev /dev --proc /proc /bin/echo sandbox-ok works fine

Already ruled out: terminal-state poisoning (fresh terminals), shell theme/prompt (plain --norc profile), stale handles (window reloads), terminal.integrated.shellIntegration.enabled (on), bwrap itself (works standalone).

Hypothesis: the LinuxSandbox wrapper’s spawn prevents VSCode shell-integration injection from loading in temporary agent terminals, so cmdCap never arrives. Request: an option to disable the terminal sandbox, or a fix to the injection path under the wrapper.