Skip to content

Guard long-running local commands with explicit deadlines #96

Description

@devantler

🤖 Generated by the Agentic Engineer

Objective

Stop repeat Agentic Engineer tool timeouts caused by expected-to-run-long local test commands inheriting a runtime tool's generic execution deadline.

Details

A seven-day Agent Improver window observed 19 timeout signatures across 117 local Claude sessions. The recurrence is concentrated in test commands: 7 of 877 default-deadline test calls timed out, while 0 of 154 explicitly bounded test calls did. Go tests timed out 3 of 123 times with the default and 0 of 49 with an explicit deadline; Godot tests timed out 2 of 101 times with the default and 0 of 42 with an explicit deadline.

This is distinct from remote polling: extending a remote foreground wait would preserve the wrong behavior. The generic Agentic Engineer definition should require an explicit, measured execution deadline only for expected-to-run-long local test, build, and render commands, with repository/CI timing plus bounded headroom.

Checklist

  • Add a failing delivery-contract fixture for the missing local-command deadline guard
  • Add the smallest tool-neutral guard to the Agentic Engineer entrypoint
  • Preserve the existing prohibition on foreground remote waiting
  • Validate the manifest contract and all bundled skills

Dependencies

None. No open issue, PR, or codex/* branch currently covers this behavior.

Notes

Telemetry is aggregate and value-minimized; no session content or credential-like value is included.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions