fix(ploeg): say which watchdog stopped an ACP Run #198

Closed
ryangr0 wants to merge 5 commits from ryangr0/ploeg-name-the-watchdog into development AGit
Owner

The ACP adapter reported "acp agent stopped responding" for both its idle watchdog and its prompt wall, so a Run like reviewer Run 209 did not say whether the agent went silent or ran out of time. A Run's summary and reason now name the watchdog, its limit and (for the idle watchdog) the protocol event count, e.g. acp idle watchdog stopped the agent: no protocol activity for 10m0s. failure_reason stays agent_error, as ADR-0043 keeps it. docs/architecture.md says so.

Ticket: https://vikunja.webgrip.dev/tasks/1595

Tests

  • New: TestBuild_NamesTheWatchdogThatStoppedTheRun, TestRun_HungAgentNamesTheWatchdogThatStoppedIt (both fail on the old code)
  • cd apps/ploeg && mise exec -- go test -count=1 ./...: ok
  • mise exec -- go vet ./...: ok
  • mise run verify: All gates passed
  • mise run docs-check: ok

Checks left to CI

None.

🤖 Generated with Claude Code

The ACP adapter reported "acp agent stopped responding" for both its idle watchdog and its prompt wall, so a Run like reviewer Run 209 did not say whether the agent went silent or ran out of time. A Run's summary and reason now name the watchdog, its limit and (for the idle watchdog) the protocol event count, e.g. `acp idle watchdog stopped the agent: no protocol activity for 10m0s`. `failure_reason` stays `agent_error`, as ADR-0043 keeps it. `docs/architecture.md` says so. Ticket: https://vikunja.webgrip.dev/tasks/1595 ## Tests - New: `TestBuild_NamesTheWatchdogThatStoppedTheRun`, `TestRun_HungAgentNamesTheWatchdogThatStoppedIt` (both fail on the old code) - `cd apps/ploeg && mise exec -- go test -count=1 ./...`: ok - `mise exec -- go vet ./...`: ok - `mise run verify`: All gates passed - `mise run docs-check`: ok ## Checks left to CI None. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
fix(ploeg): say which watchdog stopped an ACP Run
Some checks failed
[Workflow] On Pull Request / checks (pull_request) Has been cancelled
[Workflow] On Pull Request / warnings (pull_request) Has been cancelled
[Workflow] On Pull Request / release-policy (pull_request) Has been cancelled
0c217c7ec6
The ACP adapter reported "acp agent stopped responding" for both its idle
watchdog and its prompt wall, so a Run like reviewer Run 209 did not say
whether the agent went silent or ran out of time. The summary and reason now
name the watchdog, its limit and, for the idle watchdog, the protocol event
count. The failure reason stays agent_error, as ADR-0043 keeps it.

VIK-1595
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
The stuck reason now starts with exactly "no protocol activity for <idle
timeout> after <n> events" or "prompt ran past <timeout>", without the
watchdog's name, which the summary already carries.

VIK-1595
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
A Run whose summary says an ACP watchdog stopped it (the idle watchdog, the
prompt wall, or the older "acp agent stopped responding") now reads "The agent
stopped responding" instead of "The agent harness exited with an error ...
Read its log tail", and its stderr tail is shown under "Last lines it
printed". The cause comes from the summary before the failure_reason table;
other agent_error Runs keep their wording, and failure_reason stays
agent_error.

VIK-1595
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
VIK-1595
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
chore(site): re-record the demo replay for the stopped-responding cause
Some checks failed
[Workflow] On Pull Request / checks (pull_request) Has been cancelled
[Workflow] On Pull Request / warnings (pull_request) Has been cancelled
[Workflow] On Pull Request / release-policy (pull_request) Has been cancelled
75562a3d83
VIK-1595
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
ryangr0 closed this pull request 2026-10-04 08:41:35 +00:00
Some checks failed
[Workflow] On Pull Request / checks (pull_request) Has been cancelled
[Workflow] On Pull Request / warnings (pull_request) Has been cancelled
[Workflow] On Pull Request / release-policy (pull_request) Has been cancelled

Pull request closed

Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
webgrip/unfold!198
No description provided.