From 253599ce9c0d08d27b62ae3df259dd50941cd1c7 Mon Sep 17 00:00:00 2001
From: timkjr <timkjr@k-lab.lan>
Date: Wed, 26 Aug 2026 21:36:32 -0500
Subject: [PATCH] fix(omp): wire ompConfig into respawnPane and default to
 --continue there

respawnPane() -- the path used when a session's pane died (crash, idle
respawn, or the user's own /exit) but the Codeman session object is
still tracked -- never had ompConfig wired through at all, in either
its options destructure or its inner buildSpawnCommand() call. This is
a gap in the original OMP patch, distinct from the resumeHistorySession
fix (which only covers a session that has been fully closed and shows
up as a history row): reselecting a tab whose CLI process just exited
goes through this path instead, and always launched a bare, contextless
`omp` no matter what.

Beyond the wiring, respawning a dead pane is semantically different
from creating a brand-new session: the conversation is still "this
session" to the user, so _buildRespawnPaneOptions() now defaults
ompConfig to continueSession:true unless the session already carries
an explicit resumeSessionId (which still wins in buildOmpCommand).

Verified live: told a session a secret, exited OMP so the pane died
(session and tmux both left alone), forced the exact dead-pane-respawn
path, and the new process replied with the secret -- confirming
`omp --continue` fired instead of a blank omp.
---
 src/session.ts      | 8 +++++++-
 src/tmux-manager.ts | 2 ++
 2 files changed, 9 insertions(+), 1 deletion(-)

diff --git a/src/session.ts b/src/session.ts
index 604458e6..bab62b35 100644
--- a/src/session.ts
+++ b/src/session.ts
@@ -1630,7 +1630,13 @@ export class Session extends EventEmitter {
       piConfig: this._piConfig,
       grokConfig: this._grokConfig,
       deepSeekConfig: this._deepSeekConfig,
-      ompConfig: this._ompConfig,
+      // Respawning a dead pane means the CLI process exited (crash, idle
+      // respawn, or the user's own /exit) but this is still the same
+      // conversation from the user's perspective — unlike a brand-new
+      // `createSession` call, defaulting to --continue here is the honest
+      // behavior. Only when the session has no resume id of its own already
+      // (an explicit resumeSessionId always wins in buildOmpCommand).
+      ompConfig: this._ompConfig?.resumeSessionId ? this._ompConfig : { ...this._ompConfig, continueSession: true },
       resumeSessionId: this._resumeSessionId,
       envOverrides: this._envOverrides,
       effort: this._effort,
diff --git a/src/tmux-manager.ts b/src/tmux-manager.ts
index 2bd31f96..182db818 100644
--- a/src/tmux-manager.ts
+++ b/src/tmux-manager.ts
@@ -2391,6 +2391,7 @@ export class TmuxManager extends EventEmitter implements TerminalMultiplexer {
       piConfig,
       grokConfig,
       deepSeekConfig,
+      ompConfig,
       resumeSessionId,
       envOverrides,
       effort,
@@ -2422,6 +2423,7 @@ export class TmuxManager extends EventEmitter implements TerminalMultiplexer {
       piConfig,
       grokConfig,
       deepSeekConfig,
+      ompConfig,
       resumeSessionId,
       effort,
       sessionName: name,