Bitter Frontier What coding agents just made possible, where the bottleneck moved, and what deserves attention.

Evidence record / eve

A dated record of one change, kept so the writing that cites it can be checked. Compiled from the sources listed below by the research run, not written for reading. The judgment lives in the issues that cite it, below.

2026-10-13-eve-approval-gated-workflow-tools-could-start-before-approval-until-0-69-0-and-approvals-outli

Approval-gated workflow tools could start before approval until 0.69.0, and approvals outlived cancelled turns until 0.70.0. #3983: “Workflow tools could start while awaiting approval, and automatic policy denials did not prevent deferred dispatch.” The 0.63.0 docs promised the opposite. #3954: “anyone could cancel a policy-guarded approval, so a requester-only policy … still let someone else dismiss the request”; it also closed a path where “an approval parked alongside deferred workflow calls settled without its policy” and one where ACP’s Deny was dropped instead of treated as Cancel. #4135: sign-in and approval prompts “outlived the turn that raised them” and “a later click started a fresh turn”; from 0.70.0, cancelling a turn withdraws its approval and “a later answer to it approves nothing.”

Channel: tagged-release. Half: defect. Date: 2026-10-01 (eve@0.69.0), 2026-10-02 (eve@0.70.0).

Operator consequence: Audit approval-gated blocking/deferred workflow dispatch on 0.63.0 through 0.68.0; the first affected release and exposure of every legacy background path are not established. Compare start times with approval settlement and look for calls that ran despite denial. The baseline deferred-path predicate explicitly excludes execution: "background", so this evidence cannot label every background path ungated or safe. The dispatch repair first shipped in 0.69.0 and prompt withdrawal in 0.70.0; install current stable 0.79.0, and include the later lifecycle and queued-text cases in authority tests. Write a test that a denied call never starts.

Receipt

Finding metadata

Confidence
high

Run: 2026-10-13-profile-refresh-2026-09-21_2026-10-13-frontier-v0

Finding ID: 2026-10-13-eve-approval-gated-workflow-tools-could-start-before-approval-until-0-69-0-and-approvals-outli

Profile citations

  • Eve / claim / deferred-dispatch-and-withdrawal
  • Eve / posture / governance

Source links

Primary links, including exact changelog lines when available.

  1. eve
    commit2026-10-13-eve-approval-gated-workflow-tools-could-start-before-approval-until-0-69-0-and-approvals-outligithub.com/vercel/eve/commit/bb70743186612e13bd0b05c58d37e5b024d17a76commit2026-10-13-eve-approval-gated-workflow-tools-could-start-before-approval-until-0-69-0-and-approvals-outligithub.com/vercel/eve/commit/1a5bc56e8539e0c7d555402a932a07cbd88ac4d6tagged commit file2026-10-13-eve-approval-gated-workflow-tools-could-start-before-approval-until-0-69-0-and-approvals-outlivercel/eve / packages/eve/src/harness/tool-loop.ts#L2967-L2971merged pr2026-10-13-eve-approval-gated-workflow-tools-could-start-before-approval-until-0-69-0-and-approvals-outligithub.com/vercel/eve/pull/3983merged pr2026-10-13-eve-approval-gated-workflow-tools-could-start-before-approval-until-0-69-0-and-approvals-outligithub.com/vercel/eve/pull/3954github release2026-10-13-eve-approval-gated-workflow-tools-could-start-before-approval-until-0-69-0-and-approvals-outlivercel/eve / eve%400.69.0tagged commit file2026-10-13-eve-approval-gated-workflow-tools-could-start-before-approval-until-0-69-0-and-approvals-outlivercel/eve / docs/tools/workflows.mdx#L301-L302merged pr2026-10-13-eve-approval-gated-workflow-tools-could-start-before-approval-until-0-69-0-and-approvals-outligithub.com/vercel/eve/pull/4135

Versioned source: run artifact