Back Home

GitHub Repo

Hermes Agent Canary Fix Resolves Tool Timeout Conflict, Preventing Long Tasks from Being Cut Off at 420 Seconds

The November 16 Hermes Agent canary release includes a tool execution deadline fix that lets terminal tools’ longer requested wait times take effect. It addresses outer timeouts firing first, which could discard partial output and cause the agent to wait repeatedly on background processes.

Public domain · Image source
zh-Hant

Hermes Agent’s November 16 release, v0.23.1+canary.20261116T070005Z, includes a tool timeout fix that adjusts the waiting rules between the agent executor and terminal tools. The code change is in a prerelease; whether it will be included in a stable release has yet to be confirmed. Release notes

According to the commit description, the sequential and parallel executors previously imposed a default 420-second limit on tool calls, while the terminal tool allowed foreground commands to explicitly request waits of up to 600 seconds. As a result, a valid terminal(timeout=600) call could be cut off by the outer limit first, leaving only a generic timeout error and preventing the tool from returning its available partial output and exit code. Background-process waits had a similar mismatch: the process could still be running while the model received no result, potentially causing it to issue the same wait call again. Fix commit

The new version adds ToolEntry.deadline_floor, allowing a tool to declare the minimum wait budget it needs based on its call parameters. The executor raises the outer deadline to accommodate that budget and adds a five-second buffer, so the tool’s own timeout handling can return a result first. For parallel batches, it uses the largest declared value. Tools without a declared value retain the existing limit, and paths that previously disabled the outer deadline keep their existing behavior. Code diff

The official configuration documentation also lists terminal.timeout and TERMINAL_TIMEOUT, which control how long a command itself waits. For engineering teams, this change highlights the need to coordinate deadlines across layers: increasing the command-level setting alone may not be enough for the agent to receive the full execution status. Configuration documentation

For long-running builds, tests, and data-processing jobs, retaining partial output can help the model assess progress and decide what to do next. This is an engineering implication inferred from the fix, not a reported improvement in success rates. Before adopting it, teams should verify that commands running longer than seven minutes, background waits, and parallel batches return as expected, and track the stable release. The available sources do not report results from large-scale deployments.

Sources

  1. Hermes Agent canary v0.23.1+canary.20261116T070005Z
  2. fix(agent): generic tool deadline no longer clips a tool's own timeout
  3. Hermes Agent Configuration