Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

🤖 Goal continuations fall back to exec when the selected agent no longer resolves

Closed
#5,402 0 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@ThomasK33 is already working on this.

Since Oct 1, 2026.

Assessment

This issue has not been assessed yet.

Description

Problem

When a workspace's selected agent no longer resolves (its definition was deleted, or the agent was disabled), automatic goal turns fall back to exec. This covers the kickoff, restart recovery and the budget wrap-up. getGoalContinuationKickoffSendOptions() returns the selected agent ID without strictAgentResolution, and resolveAgentForStream() then falls back to exec (agentResolution.ts, non-strict path).

For a goal created under a read-only agent, this means the automatic continuation can gain editing tools.

Scope

This already happens on main for user-created goals: /goal with a read-only custom agent selected, then delete or disable that agent. #5383 (stack #5394) lets read-only agents set goals themselves, which makes the case more common. Found by Codex on #5383 (thread PRRT_kwDOPxxmWM6n90Z7).

Possible fix

Automatic goal turns should fail closed when the selected agent cannot be resolved, instead of falling back to exec. One caveat: strict top-level resolution also rejects hidden agents (explore can be the saved selection). The fix therefore needs an internal automatic-goal-turn path that skips only the selectability check, not the public strictAgentResolution flag.


Generated with xum • Model: anthropic:claude-opus-5-5 • Thinking: high • Cost: $57.88

Dominant language
TypeScript
Stars
2k
Forks
140
Avg merge
3h 48m
Merged PRs (30d)
902

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from coder/xum

All issues in coder/xum

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.