mirror of
https://github.com/NousResearch/hermes-agent.git
synced 2026-07-21 16:18:55 +00:00
- Nudge text now warns that repeated protocol violations will block the task and require manual intervention, so the model understands the consequence of ignoring the nudge. - Kanban docs restructured to clearly separate the two defense layers: agent-side prevention (nudge, from #64350) and dispatcher-side recovery (bounded retry, from this PR). - Two new integration tests verifying the nudge mentions blocking and that the agent-side and dispatcher-side budgets are independent.
133 lines
5 KiB
Python
133 lines
5 KiB
Python
"""Tests for the kanban worker turn-end stop guard."""
|
|
|
|
from __future__ import annotations
|
|
|
|
import pytest
|
|
|
|
from agent.kanban_stop import (
|
|
build_kanban_stop_nudge,
|
|
kanban_stop_nudge_enabled,
|
|
session_called_kanban_terminal,
|
|
)
|
|
|
|
|
|
@pytest.fixture
|
|
def clear_kanban_env(monkeypatch):
|
|
for var in ("HERMES_KANBAN_TASK", "HERMES_KANBAN_STOP_NUDGE"):
|
|
monkeypatch.delenv(var, raising=False)
|
|
return monkeypatch
|
|
|
|
|
|
def test_disabled_without_kanban_task(clear_kanban_env):
|
|
assert kanban_stop_nudge_enabled() is False
|
|
assert build_kanban_stop_nudge(messages=[]) is None
|
|
|
|
|
|
def test_enabled_with_kanban_task(clear_kanban_env):
|
|
clear_kanban_env.setenv("HERMES_KANBAN_TASK", "t_abc")
|
|
assert kanban_stop_nudge_enabled() is True
|
|
|
|
|
|
def test_env_can_disable(clear_kanban_env):
|
|
clear_kanban_env.setenv("HERMES_KANBAN_TASK", "t_abc")
|
|
clear_kanban_env.setenv("HERMES_KANBAN_STOP_NUDGE", "0")
|
|
assert kanban_stop_nudge_enabled() is False
|
|
assert build_kanban_stop_nudge(messages=[]) is None
|
|
|
|
|
|
def test_nudge_when_no_terminal_tool(clear_kanban_env):
|
|
clear_kanban_env.setenv("HERMES_KANBAN_TASK", "t_46be8aa5")
|
|
messages = [
|
|
{"role": "user", "content": "work kanban task"},
|
|
{
|
|
"role": "assistant",
|
|
"content": "Let me write the comprehensive recipe.",
|
|
"tool_calls": [
|
|
{
|
|
"id": "1",
|
|
"type": "function",
|
|
"function": {"name": "kanban_heartbeat", "arguments": "{}"},
|
|
}
|
|
],
|
|
},
|
|
{"role": "tool", "name": "kanban_heartbeat", "tool_call_id": "1", "content": "ok"},
|
|
]
|
|
nudge = build_kanban_stop_nudge(messages=messages, attempts=0)
|
|
assert nudge is not None
|
|
assert "kanban_complete" in nudge
|
|
assert "kanban_block" in nudge
|
|
assert "t_46be8aa5" in nudge
|
|
assert "protocol violation" in nudge.lower() or "protocol" in nudge.lower()
|
|
|
|
|
|
def test_no_nudge_after_kanban_complete(clear_kanban_env):
|
|
clear_kanban_env.setenv("HERMES_KANBAN_TASK", "t_abc")
|
|
messages = [
|
|
{
|
|
"role": "assistant",
|
|
"content": "",
|
|
"tool_calls": [
|
|
{
|
|
"id": "1",
|
|
"type": "function",
|
|
"function": {"name": "kanban_complete", "arguments": "{}"},
|
|
}
|
|
],
|
|
},
|
|
{"role": "tool", "name": "kanban_complete", "tool_call_id": "1", "content": "done"},
|
|
]
|
|
assert session_called_kanban_terminal(messages) is True
|
|
assert build_kanban_stop_nudge(messages=messages) is None
|
|
|
|
|
|
def test_no_nudge_after_kanban_block(clear_kanban_env):
|
|
clear_kanban_env.setenv("HERMES_KANBAN_TASK", "t_abc")
|
|
messages = [
|
|
{"role": "tool", "name": "kanban_block", "tool_call_id": "1", "content": "blocked"},
|
|
]
|
|
assert build_kanban_stop_nudge(messages=messages) is None
|
|
|
|
|
|
def test_nudge_budget_exhausted(clear_kanban_env):
|
|
clear_kanban_env.setenv("HERMES_KANBAN_TASK", "t_abc")
|
|
assert build_kanban_stop_nudge(messages=[], attempts=2) is None
|
|
assert build_kanban_stop_nudge(messages=[], attempts=1, max_attempts=1) is None
|
|
assert build_kanban_stop_nudge(messages=[], attempts=0, max_attempts=1) is not None
|
|
|
|
|
|
# ── Integration: agent nudge + dispatcher bounded retry ──────────────
|
|
# These tests verify the two layers compose correctly: the agent-side
|
|
# nudge fires first (up to 2 attempts), and if the worker still exits
|
|
# without a terminal call, the dispatcher's bounded retry (streak of 3)
|
|
# handles it. See also tests/hermes_cli/test_kanban_core_functionality.py
|
|
# for the dispatcher-side streak tests.
|
|
|
|
|
|
def test_nudge_text_warns_about_blocking(clear_kanban_env):
|
|
"""The nudge should warn that repeated violations will block the task."""
|
|
clear_kanban_env.setenv("HERMES_KANBAN_TASK", "t_abc")
|
|
nudge = build_kanban_stop_nudge(messages=[], attempts=0)
|
|
assert nudge is not None
|
|
assert "block" in nudge.lower(), (
|
|
"nudge should warn that repeated violations will block the task"
|
|
)
|
|
|
|
|
|
def test_nudge_and_dispatcher_budgets_are_independent(clear_kanban_env):
|
|
"""Agent-side nudge budget (2) and dispatcher-side streak (3) are
|
|
separate budgets — the nudge counter does not affect the dispatcher's
|
|
violation streak, and vice versa.
|
|
|
|
This is a source-level invariant check: the nudge counter
|
|
(``_kanban_stop_nudges``) lives on the AIAgent instance and resets
|
|
per session, while the dispatcher streak lives in the task_runs DB
|
|
table and persists across worker respawns.
|
|
"""
|
|
clear_kanban_env.setenv("HERMES_KANBAN_TASK", "t_abc")
|
|
# Agent-side: 2 nudge attempts per session
|
|
assert build_kanban_stop_nudge(messages=[], attempts=0) is not None
|
|
assert build_kanban_stop_nudge(messages=[], attempts=1) is not None
|
|
assert build_kanban_stop_nudge(messages=[], attempts=2) is None
|
|
# Dispatcher-side streak is tracked in the DB, not in the nudge module —
|
|
# the nudge module has no knowledge of the streak counter.
|
|
assert not hasattr(build_kanban_stop_nudge, "_streak")
|