Skip to content

Clarify blocked-only wait when an Agent Vision baseline is missing #8572

Open

Description

@xiaobaifly7

Product boundary to decide

An Agent with one blocked advancement Todo and zero executable Todos can still receive should_run=true / run_now because a retained Vision checkpoint reports a missing per-Agent baseline. The quota is positive and not exhausted: 12 allowed, 1 spent. Please define the intended entry into blocked-only wait when this independent baseline obligation exists.

This is a reproduced decision-policy boundary, not a Windows-specific failure or a claim that a host has already entered an infinite loop. Confirmed on main beff0f3e55d1f70eceebbd8e78c11f1cff34643b; the same packet shape was observed on release 2.3.0.

Minimal counts-only reproduction

  1. In a disposable active Goal, register one Agent with one blocked advancement Todo, zero executable Todos, no due monitor and no owed prior settlement.
  2. Retain a Vision checkpoint marked missing_baseline=true, using the existing public fixture shape in examples/control_plane/quota-replan-decision-plane-smoke.py. Mere absence of a baseline is not asserted to be sufficient; the retained missing-checkpoint fact is part of the reproduction.
  3. Keep compute positive, allowed slots 12, spent slots 1.
  4. Build one fresh quota decision with explicit generic_cli scheduler context.
Result Value
Registered Agents 1
Blocked / executable Todos 1 / 0
Allowed / spent slots 12 / 1
Quota state eligible
Replan trigger vision_checkpoint_missing
Effective action autonomous_replan_required
should_run true
Agent delivery allowed false
Quiet no-op allowed false
Scheduler action / cadence run_now / active_work

One source decision was evaluated for this case. No replan was executed, no settlement was manufactured and no host/model loop or future repeated-wakeup count is claimed.

Ownership and duplication check

The missing-checkpoint frontier projection requests a bounded Vision patch or explicit frontier retirement. The existing typed quota run decision selects that independent obligation before lane waiting.

#8511 explicitly waits only with no higher-priority obligation and preserves replan priority; it does not decide whether a missing baseline should postpone blocked-only wait or how that repair should become a finite, clearly visible duty. Closed #4667 concerns long-chain replan ACK/checkpoint rearming after accepted work, and #7403 concerns a behavior-portfolio contrast's delivery relation. Neither reports this one-blocked/zero-executable baseline-entry case. Existing searches for the exact trigger and blocked/Vision/baseline combination found no specific issue.

The exhausted-budget variant is tracked separately in #8571; this case keeps ample quota to isolate the blocked-frontier question.

Requested maintainer outcome

Decide whether baseline initialization is a prerequisite to entering blocked-only wait, and specify its durable closeout/re-entry rule. If the replan attempt is required, expose the concrete baseline duty and a bounded outcome instead of leaving callers to interpret active_work as executable task progress. If wait should win, retain the missing baseline as explicit pending work without authorizing blocked delivery. Preserve real independent work, exact resume proofs, legal no-debit closeouts and owner Stop.

Activity

  1. BigDataDZ commented on Nov 14, 2026

    @BigDataDZ
    Contributor

    独立代码勘察与提案(供维护者决策参考)

    现状代码事实(main 1cdd9bbef):

    • loopx/control_plane/goals/goal_frontier/outcome_continuity.py:181-219 将 missing_baseline=true 的 checkpoint 投影为 vision_checkpoint_missing frontier gap,要求的收尾是"有界 Vision patch 或显式 frontier 退休"。
    • loopx/control_plane/quota/run_decision.ts:140-160 的 applyGoalOverrides 在 replan_decision_allowed 成立时无条件 should_run=true + AUTONOMOUS_REPLAN_REQUIRED,注释明确写着 "autonomous replan obligation is selected before monitor quiet or agent-scope wait classification"——即当前排序是有意的,fix(quota): wait when the only scoped work is blocked #8511 的 lane 等待只在无更高优先义务时生效。

    两个可选方向的后果:

    • 等待优先(baseline 缺失即进入 blocked-only wait):语义最保守,但缺失的 baseline 没有任何授权路径去初始化——pending 义务持续可见却无人唤醒,形成可见的活锁;且与 fix(quota): wait when the only scoped work is blocked #8511 "保留 replan 优先级" 的既有决策相悖。
    • 维持 replan 优先、修正呈现(我推荐):保留唤醒,但 ① 为 missing-baseline 单独分类 effective_action(如 baseline_repair),与普通 autonomous_replan_required 区分,调用方不再把它误读为可执行任务进展;② 给修复一个有界收尾——一次 no-debit 的 unchanged-reason patch 或显式退休,配退避,不能无限重入;③ blocked-only wait 的进入条件保持"无更高优先义务"不变。

    建议的验收形状:

    1. one blocked / zero executable / missing baseline → should_run=true 但 effective_action 为独立分类,reason 指名 baseline 义务;
    2. 同一场景配额耗尽(Clarify replan admission after compute quota is exhausted #8571 变体)→ 不再 run_now,进入 blocked-only wait,baseline 义务作为显式 pending 保留;
    3. 一次成功 patch 后同场景 → blocked-only wait,无重复唤醒。
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions