Repository navigation
session: location inactivity interrupt aborts pending question with "Tool execution interrupted" #54404
Description
Activity
Thanks for the detailed write-up and the code pointers! I think this is a duplicate of #51343, which reports the same thing: the 60-minute location inactivity sweep interrupts a turn waiting on the
questiontool, and the TTL can't be configured.Possible duplicates and closely related issues/PRs, ordered by likelihood:
- core: 60m idle location eviction interrupts a running session and rejects pending questions #51343: the same problem. Waiting on
question(or a plugin form) gets interrupted when the hardcoded 60-minuteLocationActivityTTL expires. Others there confirm it on versions up to 2.0.24, and maintainers are discussing how to handle eviction. - fix(core): preserve pending human waits during idle cleanup #50499: open PR to keep the location alive while a form or permission request is pending.
- fix(core): preserve progressing sessions during location cleanup #51583 / fix(core): preserve active sessions during idle cleanup #53238: open PRs to keep sessions that are still making progress or active from being cleaned up as idle.
- core: tool failure message loses the reason when the 60m idle eviction interrupts a run #52597 / fix(core): report inactivity eviction in interrupted work #52587: the interruption message doesn't say the cause was inactivity eviction (issue and PR).
- Terminals are killed when their location is evicted after 60 minutes of chat inactivity #48691 / [Bug] Location inactivity eviction SIGTERMs live background shells after 60 minutes #51828: the same 60-minute eviction killing terminals and background shells.
The bot will close this issue as a duplicate in 1 day unless you reply explaining how your problem is different. Any extra details or repro notes are welcome on #51343.
- core: 60m idle location eviction interrupts a running session and rejects pending questions #51343: the same problem. Waiting on
Closing this as a duplicate of #51343. There's been no reply in the past day saying how this differs. #51343 covers the same problem: the 60-minute location inactivity sweep interrupts a turn waiting on the
questiontool, and the TTL can't be configured. Please follow that issue and the related PRs (#50499, #51583, #53238) for updates. If your case turns out to be different, reply here and we can reopen. Thanks again for the clear write-up!
Description
A session parked on a pending
questiontool call is interrupted by the location inactivity sweeper after ~60 minutes. The question becomes unanswerable and the turn dies:The agent does not continue the conversation after the interrupt.
Verified in source (dev @ 7b3d4ce):
questionblocks onforms.ask(...)with no deadline (packages/core/src/tool/plugin/question.ts), and pending forms are kept alive indefinitely (packages/core/src/form.ts: pending-form cache TTL isDuration.infinity).packages/core/src/location-activity.ts(options.timeToLive ?? "60 minutes").reason: "inactivity", andpackages/core/src/session/runner/step.tsfails every unsettled tool call withTOOLS_INTERRUPTED("Tool execution interrupted").There is currently no way to configure this: the 60-minute TTL is hardcoded (
LocationActivity.nodewireslayer()without options) and thequestiontool has no built-in timeout.Expected: a turn that is waiting on user input should not be treated as an inactive session. The pending question should remain answerable, or at minimum the interrupt should not abort it. Possible directions: exempt sessions with pending user-facing forms from the inactivity interrupt, refresh the TTL while a form is pending, or make the TTL configurable.
Plugins
@prevalentware/opencode-goal-plugin
OpenCode version
v2.0.24
Steps to reproduce
Observed once in normal use (question left unanswered for a long time); the code path above explains the mechanism.
Screenshot and/or share link
N/A
Operating System
Linux x86_64 (kernel 6.17.13)
Terminal
tmux (
TERM=screen-256color), shell: zsh