[teamleaderleo]

Leo-ask: ask-0ab93f41d1

Leo, on the composer's project and machine menus (2026-10-28): "For these left two dropdowns, we want to make it not cover the, you know, not open upwards ... why are there so many default icons? ... it's just not cohesive."

What base already does since the ask:

• The menus open away from the chat (New Tab: project and machine head the composer, menus open away from the chat, and Cloud picks wait for the machine #27956, sideAwayFromChat).
• The project menu has one icon column and one text inset (cmux NEXT project picker: one icon column, one text inset, even rows, no repeated path #28590), worktrees fold under their repo (cmux NEXT project picker: a lane's worktree folds under its repository; the agent chat's picker in the gallery with app icons #28747), each remote machine has its own colored computer (project chooser: each machine's projects carry its own colored computer, not one globe #31108), and the environment menu shows This Mac and Cloud, one line each (composer: the environment picker is This Mac and Cloud only; the machines are Machines… #28999, composer: the environment picker is This Mac and Cloud, one line each (carries #28999) #29891).

This PR fixes the remaining "default icons" case. In Leo's screenshot, cmux and cmuxterm-hq (manaflow-ai repos) show the plain folder while leo-workspace shows its owner's avatar. AgentPaneOwnerAvatars kept a failed fetch as nil for the whole app run. So one miss (offline at launch, the 5 s timeout) left every repository of that owner on the folder until relaunch. Now a failure is kept for 60 s (retryAfter), and the next menu open asks again. The page already re-asks on an empty answer (projectIcon.ts).

Regression test: AgentPaneProjectRepoTests/aFailedAvatarIsFetchedAgainAfterAMinute (committed first in 328dc05, red on old code: the second fetch never happens).

Observed / Not run

• Ran: the prepush gate (no new violations). Checked that https://github.com/manaflow-ai.png?size=64 answers 302 → 200 image/png, so the org's avatar URL works.
• Not run: the Swift suite red/green. This lane VM has no fleet key for cmux-ci run; the PR's CI runs it. Leo's Mac wasn't reachable from here, so the cause of the folder icons in his screenshot is inferred from the code, not read from his caches.

Changelog

Fixed: project menu icons come back after a failed avatar fetch instead of staying on the folder until relaunch.

Agent session: agent session

🤖 Generated with Claude Code

---

^{Need help on this PR? Tag @codesmith-bot with what you need.}

---

Summary by cubic

Failed owner avatar fetches in the project menu are retried after a minute instead of keeping the default folder icon for the rest of the app run. Before, one miss (for example, offline at launch or the 5-second timeout) left every repository of that owner on the plain folder until relaunch; now the next menu open at least 60 seconds later asks for the avatar again.

^{Written for commit e6f01df. Summary will update on new commits.}

[github-actions]

cmux status _{(one comment, edited in place; each line is updated by the job that owns it)}

Review e6f01df: HQ feed card · gallery before/after runs · checks

App of this head (app.zip, kept 1 day)

gh workflow run reload-build.yml -R manaflow-ai/cmux --ref feat-cmux-next -f tag=pr31728 -f ref=lane/project-avatar-retry -f platform=macos -f backend_mode=local

Shipped in:

• cmux NEXT nightly 1.0.0-nightly.4138963169701 (ad01dee1d0)
• cmux NEXT nightly 1.0.0-nightly.4139084486201 (b5060b494d)
• cmux NEXT nightly 1.0.0-nightly.4139171596001 (fb7e28b51d)
• cmux NEXT nightly 1.0.0-nightly.4139290103001 (a92c6ce841)

[teamleaderleo]

Review (codex gpt-6-astra high, next-review): SHIP at e6f01df

SHIP at e6f01df

Visual verdict: no images; Leo tries the build.

Checked retry timing, cache behavior, and actor request coalescing. The Swift suite was unavailable in this box.

Follow-ups: none

[cmux-bot]

cmux-bot approves e6f01df: an independent review passed this exact head (next-review receipt by teamleaderleo). A push needs a new review; a later BLOCK at this head dismisses this approval.