fix: name adoption in two refusals an adopted session gets (release review)

The Edit history panel told an adopted session it needed to be a Claude
session outside Docker, and a stop wait blamed the missing Claude Code hooks
on the mode. Both refusals are right, only the words misled. Each now says
Codeman did not start the session, with a zh-CN entry for the panel.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Codeman maintainer committed 2026-11-06 07:45:30 +01:00
1 parent e7c68f1340
commit ea5f6615c8
4 files changed
+24 -3

No files matched your search

+7 -1
View File
@@ -358,7 +358,13 @@ Object.assign(CodemanApp.prototype, {
const data = h.data;
if (data.state === 'unsupported') {
body.append(
el('div', 'edit-history-empty', t('Edit history is only available for Claude sessions outside Docker.'))
el(
'div',
'edit-history-empty',
data.reason === 'adopted'
? t('Edit history is not available for a tmux session opened outside Codeman.')
: t('Edit history is only available for Claude sessions outside Docker.')
)
);
return;
}
+2
View File
@@ -567,6 +567,8 @@
'Could not read the edit history.': '无法读取编辑历史。',
'Edit history is only available for Claude sessions outside Docker.':
'编辑历史仅适用于 Docker 之外的 Claude 会话。',
'Edit history is not available for a tmux session opened outside Codeman.':
'在 Codeman 之外打开的 tmux 会话无法使用编辑历史。',
'Showing saved entries only: {reason}': '仅显示已保存的条目:{reason}',
'No transcript found for this session yet. It is picked up with the next prompt; until then a CLAUDE_CONFIG_DIR set outside Codeman cannot be found.':
'尚未找到此会话的记录。它会在下一次提示时被识别;在此之前,在 Codeman 之外设置的 CLAUDE_CONFIG_DIR 无法被找到。',
+4 -2
View File
@@ -359,8 +359,10 @@ export function resolveWaitSignals(
// A dsh session is the one case where the mode is capable and THIS session
// is not, so saying "never fire for deepseek sessions" would send the
// caller looking for a bug that is really a setting they chose.
error:
options.mode === 'deepseek'
error: options.adopted
? `Signal(s) ${rejected.join(', ')} never fire for an adopted session: Codeman did not start it, so it ` +
`installed no hooks there. Use ${unsupported.has('blocked') ? 'idle or exit' : 'idle, blocked or exit'}.`
: options.mode === 'deepseek'
? options.deepSeekBridgeUnreachable
? `Signal(s) ${rejected.join(', ')} never fire for this deepseek session: it runs in a container or on ` +
`a remote host, where the local status bridge cannot reach the harness. Use idle or exit.`