agent-modules/mcp: give subagent daemon a longer default bash timeout
A subagent's backgrounded bash child is reaped along with the rest of its process tree at turn end, which silently orphans anything still running past the CLI's default 2-minute timeout — the run reports normally but the log file is empty or truncated. Raise the default on hive-subagent-daemon's own unit rather than in managed-settings, since managed-settings is also read by the main agent's session and the operator's ruling is explicit that the main agent's environment stays as is.
This commit is contained in:
parent
8ea1f7daee
commit
aaedff20a9
1 changed files with 9 additions and 0 deletions
|
|
@ -408,6 +408,15 @@ in
|
|||
# HYPERHIVE_HARNESS_DIR / HYPERHIVE_STATE_DIR: see
|
||||
# `hive-bash-daemon`'s own comment above — same global injection,
|
||||
# same reasoning.
|
||||
# A subagent's backgrounded bash child is reaped with the rest of
|
||||
# its process tree at turn end, which orphans anything still
|
||||
# running past the CLI's default 2-minute timeout with a silent
|
||||
# truncated/empty log rather than a reported failure. Raising the
|
||||
# default here (not in managed-settings, which the main agent's
|
||||
# session also reads) scopes the longer timeout to subagent turns
|
||||
# only — the operator's ruling was explicit that the main agent's
|
||||
# environment stays as is.
|
||||
BASH_DEFAULT_TIMEOUT_MS = "1800000"; # 30 minutes
|
||||
};
|
||||
serviceConfig = {
|
||||
ExecStart = "${config.services.hyperhive.agent.packages.hive-subagent-daemon}/bin/hive-subagent-daemon --http 127.0.0.1:${toString config.services.hyperhive.agent.mcp.subagentHttpPort}";
|
||||
|
|
|
|||
Loading…
Reference in a new issue