Evidence record / omnigent
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-omnigent-sub-agent-approval-notifications-now-accept-resolutions-only-from-their-originating-conver
Sub-agent approval notifications now accept resolutions only from their originating conversation. v0.18.0 binds each armed sub-agent approval notification to its originating conversation. A resolution event from another conversation is ignored instead of clearing the notification and signaling its waiter. This is coordination and approval hardening in the same bundle as the security fixes. It does not change the Edit approval threshold or establish a separately exploitable authorization defect.
Channel: tagged-release. Half: both. Date: 2026-10-13T06:42:07Z merged; stable 2026-10-13.
Operator consequence: Use v0.18.0 for the repaired notification bookkeeping as well as the advisories. In multi-session workflows verify that the intended waiting conversation resumes; do not report a new CVE or permission boundary from this diff alone.
Receipt
Finding metadata
Run: 2026-10-13-profile-refresh-2026-09-21_2026-10-13-frontier-v0
Finding ID: 2026-10-13-omnigent-sub-agent-approval-notifications-now-accept-resolutions-only-from-their-originating-conver
Source links
Primary links, including exact changelog lines when available.
- commit2026-10-13-omnigent-sub-agent-approval-notifications-now-accept-resolutions-only-from-their-originating-convergithub.com/omnigent-ai/omnigent/commit/d2e077a1e3d502748ec0d792dfdede7319ccb968tagged commit file2026-10-13-omnigent-sub-agent-approval-notifications-now-accept-resolutions-only-from-their-originating-converomnigent-ai/omnigent / omnigent/runtime/subagent_block_notifier.py#L160-L190
Versioned source: run artifact