Skip to content

agy-cli 0.1.114: agy's silence is cut at 15 minutes, not 5 (#1319) - #1465

Open
wangbingnan136 wants to merge 2 commits into
magpie-community:mainfrom
wangbingnan136:codex/agy-cli-turn-timeout
Open

wangbingnan136 wants to merge 2 commits into
magpie-community:mainfrom
wangbingnan136:codex/agy-cli-turn-timeout

Conversation

@wangbingnan136

Copy link
Copy Markdown

Refs #1319 (its first problem: a silent long generation cut at TURN_TIMEOUT_MS).

Summary

-const TURN_TIMEOUT_MS = positiveTimeout(process.env.AGY_BRIDGE_TURN_TIMEOUT_MS, 5 * 60 * 1000)
+const TURN_TIMEOUT_MS = positiveTimeout(process.env.AGY_BRIDGE_TURN_TIMEOUT_MS, 15 * 60 * 1000)

agy is silent while the model writes a large tool call, and before a first token it retries upstream on its own (⚠ API error (attempt N) lines). A 5-minute cut lost a 7,332-token call and its session (#1319). agy ends a failing turn itself, so the bridge's watchdog only has to catch a wedged agy.

Evidence

On one macOS machine running with AGY_BRIDGE_TURN_TIMEOUT_MS=900000 (the workaround in #1319), the bridge's prompt events (33 so far) include two first tokens after 5 minutes: ttft_ms 397608 and 575747. With the stock default, both turns would have been cut. Since the workaround, the log has no timed out reading agy output.

  • bun test ./agy-cli.test.mjs: pass (smoke still sets its own 5 s timeout)
  • bun scripts/check.mjs, bun scripts/bumped.mjs upstream/main: pass

Merge Danger

Door: two-way. It's one constant, and AGY_BRIDGE_TURN_TIMEOUT_MS still overrides it.

Blast Radius: small. A truly wedged agy is cut after 15 minutes instead of 5. The tool-result wait (AGY_BRIDGE_TOOL_TIMEOUT_MS, 30 min) is unchanged.

Version: 0.1.113 → 0.1.114.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants