# NousResearch/hermes-agent · Goal judge timeout config ignored, fix proposed

## Open now

- Nothing open on GitHub.

These items identify a bug where the goal judge ignores the configured auxiliary.goal_judge.timeout and instead applies a hardcoded 30-second cap. Multiple related fix attempts address honoring the user-configured timeout value.

## TL;DR

- 4 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 1 merged PR(s), 2 PR(s) closed without merging.
- A fix was merged to main in PR #91025. Verify it addresses your case.
- **Recommended:** read PR #91025 (and any competing PRs below) before filing. Confirm the merged change covers your symptom.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `resolved` · deciding PR(s): `pr-91025`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.50`: the share of member pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. `1.00` means every pair is linked.

## Closed / duplicate issues

- #91022: goal judge ignores auxiliary.goal_judge.timeout; hardcoded 30s cap auto-pauses /goal loops

## Prior & competing PRs

- **#91025: fix(goals): honor auxiliary.goal_judge.timeout instead of a hardcoded 30s cap**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `hermes_cli/goals.py`, `tests/hermes_cli/test_goal_judge_timeout_config.py`
- **#91096: fix(goal): honor auxiliary.goal_judge.timeout (#91022)**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `#91025`
- **#91163: fix(goals): honor auxiliary.goal_judge.timeout in the /goal judge**. closed without merge
  - maintainer direction: category `duplicate_of`; implication `duplicate`; refs `#91025`, `#91022`

## Fix status

- Merged to main in PR #91025 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-08-20`.