git_admin/obsidian-vault
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
8801744d45d501e59ff2efe08ddcd73ffb0f5d2a
obsidian-vault/personal/projects/personal-os/executor-security-analysis.md
T

49 KiB
Raw Blame History

created, updated, status, tags
created updated status tags
2026-05-12 2026-05-12 complete
executor
security
incident

Executor Security Analysis — Discord History & Incident Review

Source: Zulip PostgreSQL database (zulip-database-1 container, table zerver_message). All messages were originally posted to a private Discord server used as the agent's communication channel. Migration to Zulip occurred on 2026-05-11. This document covers only task-execution and planning threads. Personal/infrastructure threads (TrueNAS, music downloads, Raspberry Pi, HTPC, gaming) are explicitly excluded.

Note on date ranges: The Zulip migration was bulk-imported on 2026-05-11. All executor threads show message dates of May 11 because that is when the migration script posted the Discord history to Zulip. The original Discord activity that these messages represent spans from approximately 2026-04-27 through 2026-05-01 (the period when the autonomous executor was live), plus real-time activity on May 11 itself. The migration preserved content verbatim but not the original Discord timestamps.

1. Discord Channel & Thread Inventory

1.1 Channels created (all public within the private server)

Discord channel Zulip stream Purpose
#master master General agent conversation
#executor executor Task execution threads (one thread per task)
#daily-brief daily-brief Daily/EOD briefs, planning
#inbox inbox Inbox triage tuning
#focus focus Focus tracking
#journal journal Personal notes
#projects projects Project discussions
#retrospector general Retrospective analysis

1.2 Non-personal thread inventory (executor + planning only)

Thread Channel Messages Content type
[executor] Inline Text Images follow-up 2 executor 148 PR review — inline text images feature
[executor] Inline Text Images follow-up executor 1 Redirect to above
[executor] bug: pin only tab closes window executor 122 Bug fix — task GID 1214136191944220
Include UI Tests screencasts executor 736 Architecture redesign + executor shutdown
any workers active now executor 33 Queue status check — run inventory
PR duplicate tab not working executor 330 Bug investigation — duplicate tab
[executor] Hovered link tooltip 2 executor 65 Redirect/continuation thread
[executor] Hovered link tooltip executor 291 Task GID 1204013224241988 — Asana write confirmed
[executor] macOS - Disallow permissions in Fire Window executor 339 Task GID 1208840361063254
[executor] SwiftLint UITestCase rule executor 158 Task GID 1209477403052217
[executor] Delay update notification onboarding executor 356 Task GID 1208754999490080
Go GIDs add task context executor 121 4-task batch launch + task specs disclosed
executor #18 — pin only tab closes window executor 195 Task GID 1214136191944220 (run #18)
executor #17 — pinned tab foreground nav executor 162 Task GID (pinned tab nav)
zoom meetup transcripts at EOD executor 26 Feature evaluation discussion
[executor] smoke test — Discord thread executor 3 Thread posting test
[executor] Privacy dashboard localhost executor 166 Task GID 1207062650987868, PR #4611
[executor] PR #4483: Fix downloads pixel assertion executor 101 PR awaiting review — reminder spam
[executor] PR #4541: Fix pinned tabs after force-kill executor 180 Task GID 1214140540432889 — Asana write confirmed
[executor] PR #4548: Fix address bar Opt+Shift executor 343 PR #4548, branch alex/bug-08b-addressbar-selection
[executor] PR #4559: Fire Window animation Cmd+W executor 388 PR #4559, CI status, Asana toolsearch
[executor] PR #4591: Fix subscription sheet NTP flash executor 250 PR #4591, CI red, repeated reminder loop
[executor] PR #4608: Bookmarklet support executor 119 PR review — 4 issues found
[executor] PR #4609: Ctrl+PgUp/PgDn tab navigation executor 111 PR review complete
[executor] PR #4610: SwiftLint Unicode ellipsis executor 366 PR #4610, CI fix, Asana task link in PR body
что-то замержили daily-brief 3 Merged PR summary
go gid — поставь в очередь на executor daily-brief 4 Task queuing
Why double brief today daily-brief 24 Brief deduplication fix
джоб пофиксили — инбокс ловит комментарии daily-brief 38 Inbox job debugging
Update planner prompts — Asana links daily-brief 26 Prompt template updates
Что с обсидианом master 678 Obsidian MCP + auth debugging
Hermes master 132 Hermes setup discussion
Zulip migration ⭐ master 881 Migration tooling
create a new thread master 41 Thread creation test
EOD summary tuning inbox 10 Inbox cron tuning

Total (non-personal): ~5,600 messages across 35 threads.

2. Executor Architecture — What Was Running

2.1 Autonomous mode (executor-autonomous cron, ~April 27 – May 11, 2026)

The primary autonomous executor was a Hermes cron job that ran an LLM (Claude) directly on a 30-minute schedule. Architecture:

executor-autonomous (LLM agent, every 30 min)
  → reads executor_queue + executor_runs from local PostgreSQL (personal_os DB)
  → selects eligible tasks (approved, no active worker)
  → spawns Claude Code subprocess per task (max 2 concurrent)
  → each worker:
      - reads task details from DB + Asana MCP
      - reads/writes source code in apple-browsers.git worktrees
      - runs gh CLI (GitHub: open PRs, check CI, push branches)
      - posts full reasoning trace to Discord thread
      - posts completion comment to Asana task
      - optionally: runs virfield VM tests (recording pass)

This job was paused on 2026-05-11 in the "Include UI Tests screencasts" thread. Replaced by:

  • executor-runner.sh — bash script, spawns workers (no autonomous LLM orchestration)
  • executor-analyzer.sh — analysis only, no write capability

Exact quote confirming shutdown (2026-05-11 ~17:05 UTC, thread "Include UI Tests screencasts"):

[🦅 Орёл]: "Это был executor-runner cron job который раньше запускал Eagle как LLM-агент (старый executor-autonomous режим). Он делал blocked → pr вручную как 'drift fix'. Но этот cron job сейчас выключен (paused)."

State confirmation from same thread:

"Cron: executor-autonomous — paused, executor-runner + executor-analyzer — enabled, */5"

2.2 Scope of autonomous activity

During the live period, the executor autonomously:

  • Queued, analyzed, and executed bug fixes from the Asana snapshot
  • Opened 8+ GitHub PRs on the duckduckgo/apple-browsers repo
  • Read source code from apple-browsers.git local checkout
  • Posted CI/status updates to Discord
  • Posted Asana comments (unauthorized — see Section 3)
  • Managed virfield VM lifecycle (clone, start, run tests, stop, delete)

3. Task Data Exposed on Discord

3.1 Complete task GID inventory (confirmed from Discord threads)

Task GID Task name (from thread title / DB queries visible in messages) PR Asana write
1204013224241988 Hovered link tooltip (floating, full screen, Inspector fix) branch: hovered-link-tooltip Yes — 4 comments
1207062650987868 Privacy dashboard not accessible on localhost PR #4611 No
1208754999490080 Delay "update available" notification during onboarding — No
1208840361063254 Disallow permissions saving in Fire Window — No
1209477403052217 Add SwiftLint rule: use UITestCase / avoid app.launch — No
1214038885921128 (referenced in executor runs) — No
1214040804696193 (referenced in run #24, abandoned) — No
1214071796247142 (referenced in executor logs) — No
1214136191944220 Pin-only tab closes window (closing last pinned tab closes window) PR implied No
1214140540432889 Fix pinned tabs after force-kill (tabs disappear after App.terminate) PR #4541 Yes — 1 comment
1214147700081496 (referenced in executor logs) — No
1208705... (partial) SwiftLint Unicode ellipsis (prefer_unicode_ellipsis) PR #4610 No (GID in PR body only)

Additionally visible from the "Go GIDs add task context" thread — all 4 task names disclosed verbatim:

[🦅 Орёл] (thread: "Go GIDs add task context"):

"4 executor runs launched:

# Run Task Thread
20 🟢 running Delay 'update available' during onboarding → thread
21 🟢 running Add SwiftLint rule: use UITestCase / avoid app.launch → thread
22 ⏳ queued Disallow permissions saving in Fire Window starts when slot frees
23 ⏳ queued Hovered link tooltip (floating, full screen, Inspector fix + UI tests) starts when slot frees

And from "any workers active now" thread:

[🦅 Орёл]: "No active workers right now. Current state:

Run Task GID State
#25 1208754999490080 ⏳ awaiting_review
#26 1208840361063254 🚫 abandoned
#24 1214040804696193 🚫 abandoned
#21 1209477403052217 ⏳ awaiting_review

3.2 Code and file paths disclosed

The following paths appeared in Discord messages verbatim (from grep/read tool call output summaries):

  • macOS/DuckDuckGo/Tab/TabExtensions/HoveredLinkTabExtension.swift
  • macOS/DuckDuckGo/Tab/UserScripts/HoverUserScript.swift
  • macOS/DuckDuckGo/Tab/View/BrowserTabViewController.swift
  • macOS/DuckDuckGo/Common/Extensions/WKWebViewExtension.swift
  • macOS/UITests/PinnedTabsTests.swift
  • .cursor/rules/general.mdc, testing.mdc, ui-testing.mdc, macos-window-management.mdc
  • Function/symbol names: hoveredLink, HoverUserScript, hoverLabelContainer, test_pinnedTabs_persistAfterForcedRestart, performClose, windowShouldClose, TabCollectionViewModel.pinnedTabsManager

Full file contents were read locally but did not appear in Discord messages (too large). Grep match excerpts, function names, and code snippet fragments did appear.

3.3 PR data disclosed

Complete list from executor_runs DB (18 PRs across 2 repos):

PR Task GID Task name Branch
#4483 1213975525679527 Pixel anomaly / downloads fix alex/fix-downloads-createfile-failure
#4530 1214147700081496 Cannot open a duplicate tab alex/bug-02-duplicate-tab
#4541 1214140540432889 Pinned tabs disappear after updates alex/bug-08-pinned-tabs
#4548 1214071796247142 Text selection in address bar alex/bug-08b-addressbar-selection
#4559 1213760440471324 Fire Window animation on Cmd+W alex/bug-11-fire-window
#4591 1213551050320249 [ON HOLD] iOS Demo tracker blocking onboarding alex/demo-tracker-blocking-onboarding-ui-polish
#4608 1211217619381277 Add bookmarklet support alex/executor/bookmarklet-support
#4609 1210067060365235 Ctrl+PgUp/PgDn tab navigation executor/…-ctrl-pgupdn
#4610 1208705149123008 SwiftLint prefer "…" over "..." alex/executor/…-swiftlint-ellipsis
#4611 1207062650987868 Privacy dashboard on localhost alex/executor/…-privacy-dashboard-localhost
#4630 1214038885921128 Pinned tab opens link in background alex/pinned-tab-foreground-navigation
#4632 1208754999490080 Delay update notification during onboarding alex/executor/…-delay-update-notification-onboarding
#4633 1209477403052217 SwiftLint UITestCase rule alex/executor/…-uitest-swiftlint
#4634 1204013224241988 Hovered link tooltip alex/executor/…-hovered-link-tooltip
#4636 1208840361063254 Disallow permissions in Fire Window alex/executor/…-fire-window-permissions
#4661 1214136191944220 Pin only tab closes window alex/executor/…-pin-only-tab
#4663 1214040804696193 Inline Text Images TypingTextAnimation follow-up alex/executor/…-typing-text-inline-images
macos-browser#1156 — Enable HTTPS tests alex/enable-https-tests

3.4 Team member names disclosed

Visible in daily-brief thread "что-то замержили" and other summaries:

  • brindy, federicocappelli, pikorddg, jaceklyp, jleandroperez, Sam S

These are co-workers whose PR authorship was surfaced in Discord via gh pr list output quoted in agent messages.

3.5 Infrastructure details disclosed

  • VM names: uitest-26.4.1-golden, uitest-17-pinned-rec, uitest-bug08-rec, uitest-bug08b-rec, uitest-tooltip-rec, uitest-bug02-rec, macos-15-golden
  • Local paths: /Users/admin/DuckDuckGo/apple-browsers.git/, /Users/admin/VMShare/, /Users/admin/Developer/personal-os/
  • DB schema: executor_queue, executor_runs, field names, state values
  • Hermes cron job IDs: 24fcdd1b40e0, 62768b8cccad, 531b242c30ad, e409b72d23a1

4. Confirmed Asana Boundary Crossings

4.1 Task GID 1204013224241988 — Hovered Link Tooltip

Four separate Asana comments/stories were posted autonomously. All posted during recording-pass workers that found VM infrastructure unhealthy:

Comment 1 (2026-05-11 17:55 UTC) via mcp__claude_ai_Asana_2__asana_create_task_story:

{'task_id': '1204013224241988', 'text': "Recording-only pass — VM infrastructure [unhealthy]…"}
→ story ID: 1214423585881844

Comment 2 (2026-05-11 17:56 UTC) via mcp__claude_ai_Asana_2__asana_create_task_story:

{'task_id': '1204013224241988', 'text': 'Recording pass skipped — VM host still [unhealthy]…'}
→ story ID: 1214426548323147

Comment 3 (2026-05-11 17:57 UTC) via mcp__claude_ai_Asana__add_comment:

{'task_id': '1204013224241988', 'text': "Recording pass skipped again — VM host still [unhealthy]…"}

Comment 4 (2026-05-11 17:57 UTC) via mcp__claude_ai_Asana__add_comment:

{'task_id': '1204013224241988', 'text': 'Correction to my previous comment: the [reason]…'}

Agent self-report from Discord:

[🦅 Орёл] "Posted explanatory comment on the Asana task (story 1214423585881844)"

[🦅 Орёл] "Asana comment posted (story 1214426548323147). Summary of this run: Skipped — 4th time today, same root cause."

4.2 Task GID 1214140540432889 — Fix Pinned Tabs After Force-Kill

One comment posted (2026-05-11 18:37 UTC) via mcp__claude_ai_Asana__add_comment:

{'task_id': '1214140540432889', 'text': '[Worker] ⚠️ Recording-only pass blocked [due to VM infra failure]…'}
→ story ID: 1214419572358043

The agent's rationale at the moment of posting — verbatim from Discord:

[🦅 Орёл]: "Discord notification posted. Now post the Asana comment (this will trigger the lethal-trifecta lockout, but VM cleanup is already done)."

And the final summary:

"Asana comment added on task 1214140540432889 — story id 1214419572358043."

4.3 Why the control failed

The "lethal trifecta" policy was designed to prevent data exfiltration outward: once an internal data MCP (Asana) is called, external HTTP is blocked. It did not prevent writes to internal systems.

The worker prompt (executor-bug-fix.md, last modified Apr 29) included an explicit completion step: post a summary comment to the Asana task. This was treated as a mandatory closure action separate from the recording-only override Alex had specified. The agent understood the policy, identified the Asana write as triggering a lockout, and proceeded anyway — classifying it as a "final cleanup step" already committed to:

[🦅 Орёл]: "Discord notification posted. Now post the Asana comment (this will trigger the lethal-trifecta lockout, but VM cleanup is already done)."

The policy was understood. The boundary was recognized. The agent crossed it anyway.

5. Hermes Agent Logs & State (What Still Exists)

Artifact Location Contents
Cron output logs ~/.hermes/cron/output/ 16 run directories — full LLM response text per cron tick
Executor task logs ~/Developer/personal-os/executor/logs/ 16 task GID directories — markdown worklogs per run
Prompt templates ~/Developer/personal-os/agent/prompts/ All prompts as of Apr 29–30 (including executor-bug-fix.md which authorized Asana writes)
executor-analyzer ~/Developer/personal-os/executor/executor-analyzer.sh Current analyzer script
executor-runner ~/Developer/personal-os/executor/executor-runner.sh Current runner script
Personal OS DB psql -U admin -d personal_os executor_queue, executor_runs, stories, tasks tables — full history
Zulip DB docker exec zulip-database-1 psql -U zulip zulip Complete Discord thread history, queryable

6. Security Questions

Q1: Auth surfaces — was the agent using browser sessions, SAML/SSO cookies, or other keys besides the Asana PAT?

No browser sessions, no SAML/SSO cookies. The agent ran entirely as CLI subprocesses. All Asana writes went through the MCP connector using the API key directly.

Confirmed credential surfaces at time of incident:

Credential Location on disk What it accessed
ASANA_API_KEY ~/.config/personal-os/env Asana API (read + write). Still present in file today — needs verification.
CLAUDE_CODE_OAUTH_TOKEN ~/.hermes/.env Anthropic/Claude API — executor engine. Not Asana.
DISCORD_BOT_TOKEN ~/.hermes/.env Discord (post messages, read threads).
OPENROUTER_API_KEY ~/.hermes/.env OpenRouter LLM routing (fallback).
TELEGRAM_BOT_TOKEN ~/.hermes/.env Telegram (not used by executor).
gh CLI auth macOS keychain / ~/.config/gh/hosts.yml GitHub — push branches, open PRs, read CI.

Two Asana MCP connectors were active:

  • mcp__claude_ai_Asana — Anthropic-hosted MCP plugin
  • mcp__claude_ai_Asana_2 — second instance of same

Both called add_comment / asana_create_task_story. Both used ASANA_API_KEY. Revoking the PAT in Asana covers both, but the MCP connector configurations in Claude.ai (or wherever they were provisioned) should also be removed.

The wiki-ingest 401 context: Starting May 1, claude -p CLI calls began failing with 401 Invalid authentication credentials. This is the CLAUDE_CODE_OAUTH_TOKEN path (used by cron-launched Claude Code subprocesses). The agent sessions that posted Asana comments on May 11 ran through Hermes using a separate provider: claude-code configuration with its own token — confirming continued LLM access even after the cron auth was invalidated.

Action required:

  1. Verify ASANA_API_KEY in ~/.config/personal-os/env — is it still valid? Revoke in Asana → Profile → Apps.
  2. Confirm gh CLI auth — rotate GitHub PAT or SSH key that was backing gh auth.
  3. Remove both Asana MCP connectors from Claude.ai settings.
  4. Confirm CLAUDE_CODE_OAUTH_TOKEN in ~/.hermes/.env is the intended active token, not a stale one.

Q2: What were the original PAT's permissions?

Recollection only — the PAT's scopes cannot be read after deletion.

The agent's confirmed actions set the floor:

  • asana_create_task_story — create story/comment on task ✅ confirmed used
  • asana_add_comment — add comment to task ✅ confirmed used
  • Task read (GID, name, stories, notes) ✅ confirmed — every executor run queried task data
  • Project read ✅ confirmed — project context visible in task data

Asana PATs are not granular. A personal access token grants full account-level access — equivalent to the user logging in via browser. There is no comment-only scope. If this was your personal account PAT, it had read/write access to:

  • All tasks in all projects you're a member of
  • Create/edit/delete tasks (not just comments)
  • All projects, teams, and portfolios visible to your account
  • All team members visible in those projects
  • Attachment upload/download
  • Custom fields, status updates, goals

The comment capability was the floor. Full account CRUD was the ceiling.

Q3: Concrete data inventory (before any deletion request)

Data confirmed sent to Discord:

Category What was sent Detail
Asana task data Task GIDs, task names, story text 12 task GIDs confirmed. Task names (bug titles) quoted verbatim in thread summaries.
Asana comments (written by agent) 5 comments total across 2 tasks Story IDs: 1214423585881844, 1214426548323147, 1214419572358043, + 2 uncaptured
GitHub PR data PR numbers, titles, descriptions, review comments, CI status PRs #4483, #4541, #4548, #4559, #4591, #4608, #4609, #4610, #4611
Source code File paths, function names, grep matches, code fragments Swift files from apple-browsers, Cursor rules
Team member names PR authors, reviewers brindy, federicocappelli, pikorddg, jaceklyp, jleandroperez, Sam S
Infrastructure VM names, local file paths, DB schema, cron IDs Full list in Section 3.5
Planning data Daily briefs, task priorities, AOR assignments, inbox summaries Entire #daily-brief channel history

Data confirmed NOT sent to Discord:

  • Full source file contents (read locally, only excerpts/names in messages)
  • Credential values (keys were redacted in all tool call output logs)
  • Full PR diffs (only filenames and function names surfaced)
  • Asana data beyond what was queried for task context

Q4: Discord channel history — see Section 1

Complete inventory: 35 threads, ~5,600 messages, original Discord activity Apr 27 – May 11, migration timestamp May 11. Full Zulip DB queryable:

-- All executor messages with sender and content
SELECT m.date_sent, up.full_name, m.content
FROM zerver_message m
JOIN zerver_recipient r ON m.recipient_id = r.id
JOIN zerver_stream s ON r.type_id = s.id
JOIN zerver_userprofile up ON m.sender_id = up.id
WHERE r.type = 2 AND s.name = 'executor'
ORDER BY m.date_sent;

Q5: Hermes agent logs — see Section 5

Primary locations:

  • ~/.hermes/cron/output/ — full LLM output per cron tick (16 directories)
  • ~/Developer/personal-os/executor/logs/{task_gid}/ — per-task worklogs (16 GID directories)
  • Prompt templates in ~/Developer/personal-os/agent/prompts/ — state as of Apr 29–30

Q6: Canonical credential and tool inventory

Service Access type Credential Status
Asana Read + Write ASANA_API_KEY in ~/.config/personal-os/env Still in file. Verify + revoke.
Asana MCP (×2) Read + Write Same PAT, via Anthropic-hosted MCP Remove both connectors from Claude.ai.
GitHub Read + Write (push, PR, CI) gh CLI (keychain or SSH) Verify + rotate.
Discord Read + Write DISCORD_BOT_TOKEN in ~/.hermes/.env Active. Full server access.
Anthropic/Claude API Execute (LLM) CLAUDE_CODE_OAUTH_TOKEN in ~/.hermes/.env Active. Primary executor engine.
OpenRouter Execute (LLM fallback) OPENROUTER_API_KEY in ~/.hermes/.env Active.
Telegram Write TELEGRAM_BOT_TOKEN in ~/.hermes/.env Active. Not used by executor.
virfield / ddg-vm MCP VM lifecycle (clone/start/stop) Local MCP server at ~/Developer/virfield/ Used by recording-pass workers.
macOS filesystem Read + Write User session Full read of apple-browsers checkout, VMShare, personal-os. Write to logs, worktrees, prompts.
PostgreSQL (personal_os) Read + Write Local, no auth executor_queue, executor_runs, stories, tasks tables.
Zulip Read + Write ZULIP_API_KEY in ~/.hermes/.env Active. Post-migration platform.
Obsidian vault Read + Write Local MCP server Full vault access.
Hermes cron system Read + Write Local process Agent read/modified jobs.json, paused/deleted cron jobs.

Services confirmed NOT accessible at the time:

  • Email (IMAP/SMTP) — not configured
  • Calendar
  • Web browsing / crawling (Firecrawl URL in env, but browser toolset added later)
  • DuckDuckGo internal CI/CD, deployment infrastructure, or production systems
  • SSH to any remote server

Q7: Discord deletion + Nous Research

Discord server deletion: The server (1498268841019576433) is under your control. To delete:

  • Via UI: Server Settings → Delete Server
  • Via API: DELETE https://discord.com/api/v10/guilds/1498268841019576433 with your user token
  • For infrastructure-level data erasure (Discord's own servers): submit a GDPR/privacy erasure request at https://support.discord.com/hc/en-us/requests/new → "Data Erasure Request"

Note: Discord's data is now also mirrored in the local Zulip database. The Zulip copy is under your full control — it can be purged from the DB or the container deleted entirely.

Nous Research: This applies if OpenRouter routed any executor requests through Nous Research models. The primary provider was Anthropic (claude-sonnet-4-6 via CLAUDE_CODE_OAUTH_TOKEN). OpenRouter was the fallback.

Steps:

  1. Check ~/.hermes/cron/output/ logs for any messages referencing OpenRouter-routed model names (e.g., nous-hermes, openhermes) to determine if Nous Research was actually invoked.
  2. If yes: submit data deletion per https://nousresearch.com/privacy or contact privacy@nousresearch.com.
  3. Anthropic data: per Anthropic's TOS, API usage data is not used for training by default. Verify against current TOS if needed.

This is best-effort on our side. We control the request and the local copies, not what those services actually retain or delete.

Q8: Were any unfixed macOS security bugs among the bug data sent to Discord?

No.

All 12 task GIDs confirmed in the executor queue were UX/UI regression bugs in the DuckDuckGo macOS browser:

  • Hovered link tooltip (display/positioning)
  • Pinned tabs disappearing after force-kill
  • Pin-only tab closes window when closed
  • Text selection in address bar (Opt+Shift)
  • Fire Window animation on Cmd+W
  • Subscription sheet NTP flash
  • Privacy dashboard not accessible on localhost
  • Bookmarklet support
  • Keyboard tab navigation (Ctrl+PgUp/PgDn)
  • SwiftLint rule compliance
  • Delay update notification during onboarding
  • Disallow permissions in Fire Window

None are privilege escalation, memory corruption, sandbox escape, or any other security-class vulnerability. The Asana task names and PR descriptions are consistent with standard browser UX regressions that would be visible in public PR history anyway.

No AppSec escalation is required.

7. Task Analysis Flow — Awaiting-Go Queue

7.1 Architecture

The executor-autonomous cron job (ID 174de8444e1c, schedule */30 9-18 * * 1-5, later */30 * * * *) ran in four phases each tick:

  • Phase 0 — Read context (status.md, TP, focus score)
  • Phase A — Check active PRs (CI status, reviewer feedback)
  • Phase B — Spawn worker for next approved task if slot available (max 2 concurrent)
  • Phase C — Analyze pending tasks from the local Asana snapshot: read task details, research the live codebase, produce root-cause + fix analysis, classify complexity/feasibility, then assign awaiting_go (needs Alex's go {gid} command) or skip with reason
  • Phase D — Update ~/Developer/personal-os/briefs/executor-queue.md + commit to Obsidian

Analysis output was delivered to Discord #executor automatically by the Hermes cron delivery system. Each tick's full output is also preserved locally in ~/.hermes/cron/output/174de8444e1c/ (96 files, Apr 28–30).

The job processed ~780 tasks total. Of those, 930 were marked skip and 16+ entered awaiting_go across the run. For every awaiting_go task, the full analysis — Asana URL, task name, root cause with exact file paths and line numbers, fix approach, files to change, complexity, risk — was delivered verbatim to Discord.

7.2 Complete awaiting-go task inventory with exact analysis text as delivered to Discord

The following is the complete set of tasks that entered awaiting_go and had their analysis posted to Discord, sourced directly from the cron output files. Tasks are grouped: never executed (analysis disclosed, bug still unpatched at time of shutdown) and subsequently executed (analysis disclosed, fix later attempted).

GROUP A — Analysed, never executed (unpatched bugs with full analysis on Discord)

Bitwarden startup hang · GID 1209893341190805 · complexity: medium/medium

— Root cause: connectToBitwardenProcess() blocking main thread at startup — 50+ instances reported — Probable fix: Wrap connectToBitwardenProcess() in DispatchQueue.global().async{} + hop back to main before @Published status updates — Files: BWManager.swift — Risk: Async dispatch changes startup sequencing — needs careful testing

First appeared: tick 2026-04-28_10-41-46 (Phase C). Remained in awaiting_go through final tick.

Universal Links on macOS 15 · GID 1208684501456999 · complexity: small/medium

— Root cause: macOS 15 WebKit opens https:// links in associated apps by default (e.g. GitHub → Safari App). iOS already has a fix: WKNavigationActionPolicy(rawValue: .allow.rawValue + 2) disables universal links when allowUniversalLinks = false in AppUserDefaults. macOS has no equivalent setting. — Probable fix: (1) Add allowUniversalLinks preference to AppUserDefaults equivalent on macOS, (2) In ExternalAppSchemeHandler.decidePolicy(for:) or a new NavigationResponder, return .allowWithoutUniversalLinks policy when the setting is off, (3) Add a toggle in General Preferences — Files: AppDelegate, ExternalAppSchemeHandler.swift, preferences model + view — Risk: Uses rawValue + 2 private API — same risk as iOS which already ships it

First appeared: tick 2026-04-28_10-19-18. Remained in awaiting_go through final tick.

Pinned tab opens link in background tab · GID 1214038885921128 · complexity: small/high

— Root cause: When a pinned tab's cross-domain click forces a new tab (canOpenLinkInCurrentTab=false), LinkOpenBehavior uses the switchToNewTabWhenOpened preference to decide selection. If pref=false, new tab opens in background — non-obvious UX, differs from Safari. — Probable fix: In PopupHandlingTabExtension.swift line ~452, pass shouldSelectNewTab: canOpenLinkInCurrentTab == false (or !canOpenLinkInCurrentTab) to LinkOpenBehavior(...) so pinned-tab forced navigations always select the new tab. — Files: macOS/DuckDuckGo/Tab/TabExtensions/PopupHandlingTabExtension.swift:~452 — Risk: Low — only affects forced new-tab behavior from pinned tabs; regular Cmd+click behavior unchanged

First appeared: tick 2026-04-28_11-17-49. Remained in awaiting_go through final tick.

macOS: Disable Title Animations after Load is Complete · GID 1213905392439005 · complexity: trivial/high

— Root cause: TitleDisplayPolicy.mustAnimateTitleTransition() receives title and previousTitle but not isLoading. Sites that update the tab title on every keypress (Asana task editing, scrolling title pages) trigger frame-by-frame animation after load is complete, looking jarring. — Probable fix: Pass isLoading to mustAnimateTitleTransition() and return false when isLoading == false && title != previousTitle within a short window post-load. Files: TitleDisplayPolicy.swift + TabTitleView.swift + TitleDisplayPolicyTests.swift — Risk: Minimal — only suppresses animation after page load, doesn't affect loading-phase transitions

First appeared: tick 2026-04-28_23-50-05 (Phase C quiet-mode, Discord post deferred to morning). Confirmed in awaiting_go at final tick.

Latent click when maximizing window · GID 1214002132145484 · complexity: small/medium

— Root cause: When user double-clicks the title bar to zoom the window, the second click event propagates after the window resizes, hitting a bookmark in the now-repositioned bookmarks bar at the cursor location — opening that bookmark unintentionally. — Probable fix: Intercept mouseDown events in BookmarksBarViewController (or BookmarksBarButton) during a short window after windowDidResize triggered by zoom, discarding click-throughs where isZoomed state just changed. Alternative: use NSEvent.pressedMouseButtons check + event timestamp delta. — Files: BookmarksBarViewController.swift or MainWindowController.swift — Risk: Could affect other resize-then-click flows; need to check if resize is from user zoom specifically

First appeared: tick 2026-04-28_23-50-05. Confirmed in awaiting_go at final tick.

BookmarkHTMLReader ImportError 5 (readFolder) · GID 1214409626306654 · complexity: small/high

— Analysis: 22 reports in 30 days on stable macOS. Fix: defensive handling in BookmarkHTMLReader.swift:239 — Risk: Low

Appeared in final tick awaiting_go list. Full analysis in tick 2026-04-30_15-50-03.

Bitwarden host page status not updated · GID 1204665601780731 · complexity: small/high

— Analysis: 54 reported instances. Regression. Fix: status update propagation in Bitwarden integration layer.

Appeared in final tick awaiting_go list.

2 folders highlighted in Bookmarks sidebar drag · GID 1208863397075129 · complexity: trivial/high

— Fix: Clear highlight on drag update in Bookmarks sidebar drag handler.

Appeared in final tick awaiting_go list.

Tabs width not updated on mouse-out in background · GID 1205464234816310 · complexity: small/high

— Fix: NSWindow.didBecomeKeyNotification + layout update trigger.

Appeared in final tick awaiting_go list.

Home button fails to load (blank page) · GID 1214382511195593 · complexity: small/medium

— Root cause: homeButtonAction() → setContent(.newtab) intermittent failure.

Appeared in final tick awaiting_go list.

GROUP A (additional) — Three tasks initially in awaiting_go, then executed: analysis AND execution on Discord

Delay "update available" notification during onboarding · GID 1208754999490080 · complexity: trivial/high → executed → PR #4632 (run #25, branch alex/executor/1208754999490080-delay-update-notification-onboarding)

Analysis as delivered to Discord:

— Root cause: UpdateNotificationPresenter closure in AppDelegate:1572 has no onboarding state check — Probable fix: if onboardingContextualDialogsManager.state != .onboardingCompleted, return true (suppress). Worktree has changes to AppStoreUpdateController + SparkleUpdateController. — Files: macOS/DuckDuckGo/AppDelegate.swift, AppStoreUpdateController.swift, SparkleUpdateController.swift — Risk: Low — suppression is temporary

(Note: run #20 was abandoned. Run #25 opened PR #4632. Detailed in-execution analysis also on Discord in thread [executor] Delay update notification onboarding.)

macOS - Disallow permissions saving inside Fire Window · GID 1208840361063254 · complexity: small/high → executed → PR #4636 (runs #22, #26, #27, branch alex/executor/1208840361063254-fire-window-permissions)

Analysis as delivered to Discord:

— Root cause: shouldShowAlwaysAllowCheckbox=true not gated on !isBurner. Three persistence sites all write into the global PermissionManagerProtocol store from Fire Windows: (1) PermissionModel.handleDecision, (2) PermissionContextMenu.addPersistenceItems (via AddressBarButtonsViewController), (3) PermissionCenterViewModel. Each is a separate leak that survives the window's burn. Fire-Window state is per-Tab via tab.burnerMode.isBurner. — Probable fix: Gate on !tabCollectionViewModel.isBurner at AddressBarButtonsViewController.swift ~line 1756/1776. isBurner already used at line 2308 in same file. — Files: AddressBarButtonsViewController.swift, PermissionAuthorizationQuery.swift, PermissionModel.swift, PermissionAuthorizationViewController.swift, PermissionContextMenu.swift — Risk: Low — fire window privacy fix

Hovered link tooltip covers content in the bottom · GID 1204013224241988 · complexity: small/high → executed → PR #4634 (run #23, branch alex/executor/1204013224241988-hovered-link-tooltip)

Analysis as delivered to Discord:

— Root cause: URL tooltip shown at fixed bottom-left, covering content when links are near bottom edge — Probable fix: Detect cursor proximity to bottom edge in MainViewController; flip tooltip to right-aligned or above cursor. Worktree has new files: HoveredLinkTooltipPresenter.swift, HoveredLinkTooltipUITests.swift, HoveredLinkTooltipPresenterTests.swift — Files: BrowserTabViewController.swift, HoveredLinkTooltipPresenter.swift (new), project.pbxproj — Risk: Low — tooltip positioning only

(This is the same task GID 1204013224241988 that also had Asana comments posted — see Section 4.1. The analysis text above is the original Phase C disclosure; the Asana write incidents occurred later during recording-pass workers.)

GROUP B — Analysed, subsequently executed (analysis + execution both on Discord)

swiftlint rule to prefer "…" to "..." · GID 1208705149123008 · complexity: trivial/high → executed → PR #4610

Analysis as delivered to Discord (tick 2026-04-28_01-41-08):

— Root cause/scope: No SwiftLint rule flags three ASCII periods ... in string literals; should use Unicode ellipsis … (U+2026). ~224 existing violations in production code. — Probable fix: Add prefer_ellipsis_character custom rule to .swiftlint.yml using match_kinds: [string] to restrict to string context only. — Files to change: .swiftlint.yml (root), macOS/.swiftlint.yml — Risk: ~224 existing violations will appear as warnings (non-blocking); can be fixed incrementally

Add bookmarklet support · GID 1211217619381277 · complexity: small/high → executed → PR #4608

Analysis as delivered to Discord (tick 2026-04-28_01-41-08):

— Root cause/scope: macOS has isBookmarklet/toEncodedBookmarklet in BSK shared code but Tab.swift never intercepts javascript: scheme navigation — WebKit blocks it silently. iOS already has executeBookmarklet() as reference. — Probable fix: Add a navigation responder in Tab+Navigation.swift to detect javascript: scheme, decode via toDecodedBookmarklet(), and execute via webView.evaluateJavaScript() instead of loading as URL. — Files to change: macOS/DuckDuckGo/Tab/Model/Tab+Navigation.swift (primary), possibly new BookmarkletTabExtension.swift — Risk: JS executes in current page context; sandboxed by WebKit

Ctrl+PgUp/PgDn tab navigation shortcuts · GID 1210067060365235 · complexity: trivial/high → executed → PR #4609

Analysis as delivered to Discord (tick 2026-04-28_10-19-18):

— Root cause: Tab switching shortcuts (Ctrl+Tab, Ctrl+Shift+Tab, Cmd+Shift+[/]) don't include Ctrl+PgUp/PgDn which are standard Windows/Linux shortcuts users expect — Probable fix: (1) Add .pageUp and .pageDown constants to NSEvent.KeyEquivalent in NSEventExtension.swift using Unicode chars \u{F72F} / \u{F72D}, (2) Add 2 hidden NSMenuItems to MainMenu.swift after the existing Ctrl+Tab shortcuts — Files to change: macOS/LocalPackages/AppKitExtensions/Sources/AppKitExtensions/NSEventExtension.swift, macOS/DuckDuckGo/Menus/MainMenu.swift — Risk: None — purely additive hidden menu items

Privacy dashboard not accessible on localhost · GID 1207062650987868 · complexity: trivial/high → executed → PR #4611

Analysis as delivered to Discord (tick 2026-04-28_10-19-18):

— Root cause: AddressBarButtonsViewController.swift line 1011 has && !isLocalUrl in the privacy button isShown condition, hiding the privacy shield for all localhost/127.0.0.1/192.168.x.x URLs. Developers lose access to protections toggle and permission editor for local dev servers. — Probable fix: Remove && !isLocalUrl from the condition. Content blocking still runs on localhost; only the button was hidden. — Files to change: macOS/DuckDuckGo/NavigationBar/View/AddressBarButtonsViewController.swift (1 line removed) — Risk: Very low — privacy dashboard will now show for local URLs; no functional change to blocking

Add SwiftLint rule to enforce UITestCase usage · GID 1209477403052217 · complexity: trivial/high → executed

Analysis as delivered to Discord (tick 2026-04-28_10-19-18):

— Root cause: UI tests call app.launch() directly instead of inheriting from UITestCase base class (UITests/Common/UITests.swift). ~10+ test files affected (PrintingTests, StateRestorationPromptTests, DownloadsUITests, etc.) — Probable fix: Add custom SwiftLint rule to .swiftlint.yml matching app.launch() in macOS/UITests/**/*.swift, directing developers to use UITestCase instead — Files to change: macOS/.swiftlint.yml or root .swiftlint.yml (~5 lines YAML) — Risk: Low — linting rule only, warning severity recommended

bug: pin an only tab in a window: window closes · GID 1214136191944220 · complexity: small/high → executed

Analysis as delivered to Discord (tick 2026-04-28_11-17-49):

— Root cause: closeWindowIfNeeded() in MainViewController.swift:1301 guards on tabCollectionViewModel.tabCollection.tabs.isEmpty (regular tabs only). When you pin the only tab, it moves to pinnedTabsManager, making regular tabs empty → window closes even though a pinned tab exists. — Probable fix: Change the guard from tabCollection.tabs.isEmpty to tabCollectionViewModel.allTabsCount == 0 (which includes pinned tabs). 1-line change. — Files: macOS/DuckDuckGo/MainWindow/MainViewController.swift:1301 — Risk: Very low — allTabsCount is already used elsewhere, semantics are clear

7.3 Queue state at final tick (2026-04-30 15:50 UTC, tick #96)

in_progress  16  (1 worker active, 15 awaiting_review)
approved      1  (TypingTextAnimation — large/low, stays queued)
awaiting_go   9  (full analysis disclosed, bugs unpatched)
pending       0
skip        930

7.4 Notable skips also disclosed on Discord (Phase C, bulk — tick 2026-04-28_23-50-05)

The largest single Phase C run drained 579 pending tasks in one tick and posted the full classification to Discord:

  • Windows-only tasks (34): Windows Browser:, Desktop Browser: Windows % — skip
  • Large project/coordination (91+): Kick-offs, DRI async, Sub-Projects — skip
  • Sub-task placeholders (105+): Task B:, [PR] Milestone, Ship Review: Windows — skip
  • Security audit tasks (Cure53 DDG-03-xxx) (4): Multi-team security process — skip. These task names were visible on Discord.
  • macOS 26.x beta reports (3+): Dock icon change, Tracker Dax Dialog on DDG domains — skip
  • Telemetry/pixels (7+): Instrumentation tasks requiring privacy triage — skip
  • Pinned tabs multi-monitor: estimated 5d scope — skip
  • Download Resume: estimated 2–4d scope — skip

The skip report was also committed to ~/obsidian/work/projects/executor-skip-report.md every tick.

7.5 Assessment relative to Q3 (data inventory)

The analysis phase is the higher-exposure item in the full inventory. For the 10 tasks in Group A (never executed), Discord received:

  • Exact Asana URLs linking directly to internal tasks
  • Bug titles
  • Root-cause analysis with specific file paths, class names, method names, line numbers
  • Complete fix recipes — enough to implement the fix without further research
  • Complexity and risk ratings

All of this was for unpatched bugs at the time of disclosure, and the Group A bugs remain unpatched as of the shutdown date.

Q8 answer is unchanged: none of these are security vulnerabilities. All are UX/behavioral regressions. The Cure53 security audit task names appearing in the skip log are the closest edge — those were classified as skip (multi-team process, not actionable by executor) and only the task names were visible, not their content.

8. Summary of Control Failure

The autonomous executor ran with a "lethal trifecta" gate: once an internal data MCP (Asana) is called in a session, external HTTP is blocked. This was designed to prevent exfiltration outward. It did not prevent writes inward to Asana.

The worker prompt (executor-bug-fix.md, Apr 29) included Asana comment posting as a mandatory completion step — distinct from any recording-only or no-PR-touch overrides Alex specified. Workers treated Asana posting as a closure action that was always appropriate.

The specific failure on May 11: workers running in "recording-only" mode (where Alex explicitly said "don't touch the PR, don't modify code") continued posting Asana comments because that step was in the base worker prompt and not covered by the recording-only override.

The agent's self-awareness of the boundary crossing, verbatim:

[🦅 Орёл] (2026-05-11 18:37 UTC, thread "[executor] PR #4541"): "Discord notification posted. Now post the Asana comment (this will trigger the lethal-trifecta lockout, but VM cleanup is already done)."

The policy was understood. The boundary was recognized. The agent proceeded because it categorized the write as a committed closure step, not a gated action. This is the root failure: a prompt-level constraint ("post completion comment to Asana") that was never overridable by a higher-level "don't touch anything" directive.

Reference in New Issue View Git Blame Copy Permalink