Mobile Agents sheet shows the OpenAI logo for a task delegated to another environment when the app is not connected to it

Offen Anfängerfreundlich
  • Stimmt etwas nicht?
#37,270 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
2/5
Geschätzter Aufwand
1-3 Stunden
Anfängerfreundlichkeit
70/100
Issue-Typ
Bug
Klarheit
Klar beschrieben
Aktivitätsstatus
Aktiv
Tech-Stack
typescript
Bereich
mobile

Rechercherichtung

Beginne in apps/mobile/src/features/threads/SubagentRow.tsx: Die Zeile ermittelt den Provider aus useEnvironmentServerConfig(...) und fällt auf provider?.driver ?? subagent.driver zurück, was der "remote"-Platzhalter aus apps/server/src/peer/RemoteDelegation.ts ist. Vergleiche mit den Guards, die bereits in thread-subagent-group.tsx (SubagentAvatar) und im Web-ThreadRelationshipsControl.tsx (fallbackIcon={BotIcon}) verwendet werden, und prüfe dann apps/mobile/src/components/ProviderIcon.tsx, wo der generische Fallback den OpenAI-Knoten rendert. Fertig sieht so aus: Eine Zeile für eine Aufgabe, die an eine getrennte Umgebung delegiert wurde, zeigt eine neutrale Roboter-Glyphe, nicht das OpenAI-Logo, und dasselbe gilt für "remote"-Treiber, die den generischen Fallback erreichen.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

What happened

On the iPad app, a thread on my MacBook delegated a task to my desktop environment with delegate_task, using Claude Opus 5.5. The iPad is connected to the MacBook but not to the desktop. In the thread's Agents sheet, that task's row shows the OpenAI/ChatGPT logo next to "Claude Opus 5.5". Local Claude tasks in the same sheet show the Claude logo correctly.

Reproduced with a placeholder task on Claude Haiku 5.5 delegated to the other environment: the row shows "Working on" followed by that environment's name and "Claude Haiku 5.5" with the OpenAI logo.

Diagnosis

The server records a cross-environment task with the placeholder driver "remote" (apps/server/src/peer/RemoteDelegation.ts: driver: ProviderDriverKind.make("remote"), commented "The driver runs there; this side only labels the task with it").

SubagentMetadata in apps/mobile/src/features/threads/SubagentRow.tsx looks up the provider instance in the remote environment's server config (useEnvironmentServerConfig(subagent.remoteChild?.environmentId ?? environmentId)). When the client is not connected to that environment, there is no config, so provider is undefined and the row falls back to <ProviderIcon provider={provider?.driver ?? subagent.driver} />, which means provider="remote".

ProviderIcon (apps/mobile/src/components/ProviderIcon.tsx) has no branch for "remote", and getProviderClient("remote") returns undefined, so it reaches the generic fallback at the end. That fallback is the OpenAI knot glyph (the same path as the OpenAI icon in apps/web/src/components/Icons.tsx). So any task whose driver cannot be resolved is drawn as an OpenAI task.

The other surfaces already handle this case:

  • the mobile chat subagent card (thread-subagent-group.tsx, SubagentAvatar) skips item.driver when remoteChild is set ("A remote task's own driver is only a "remote" label") and shows a neutral robot symbol;
  • web's lineage row (ThreadRelationshipsControl.tsx) does the same with fallbackIcon={BotIcon}.

Only the Agents sheet row passes the "remote" placeholder through. The code is unchanged on current main.

Possible fixes: apply the same remoteChild guard and robot fallback in SubagentRow; or, since launched.modelSelection is already stored, record or derive the real driver so the sheet can show the Claude logo even when it is offline. Separately, a generic fallback that is a real vendor's logo makes any unresolved driver look like Codex; a neutral glyph would be safer.

Steps to reproduce

  1. Link two environments, A and B.
  2. Connect the mobile app to A only.
  3. In a thread on A, have the agent run delegate_task with a target in environment B and a Claude model.
  4. On mobile, open the thread and tap the "Waiting on N subagents" pill to open the Agents sheet.
  5. The delegated row shows "Working on" followed by B's name, the model name, and the OpenAI logo instead of the Claude logo.

From the code, connecting the mobile app to B as well should make the row show the correct icon and instance name, because the config lookup then succeeds. This has not been tested.

Version

Mobile 2.3.0 (iPadOS). Parent server: 0.1.10-nightly.20261115.4723 (macOS desktop app). Delegated environment's server: 0.1.10-nightly.20261112.4580 (Windows desktop app).

Environment

iPad mini, T3 Code 2.3.0 (App Store). Parent environment: macOS desktop app. Delegated environment: Windows desktop app, linked to the parent but not connected from the iPad.

Evidence

apps/server/src/peer/RemoteDelegation.ts
  driver: ProviderDriverKind.make("remote"),

apps/mobile/src/features/threads/SubagentRow.tsx
  const config = useEnvironmentServerConfig(subagent.remoteChild?.environmentId ?? environmentId);
  ...
  <ProviderIcon provider={provider?.driver ?? subagent.driver} ... />   // "remote" when config is missing

apps/mobile/src/components/ProviderIcon.tsx
  // last return: the OpenAI knot, used for any driver without an icon
  <Svg ... viewBox="100 100 411 411"> <Path d="M252.794 108.802 ..." />

Related issues

#26854 (iPhone listed cross-machine delegated tasks as top-level threads, fixed) and #24831/#24896 (account badges on subagent rows) touch the same rows but not the icon fallback. No existing issue found for this.

Fix applied or workaround

None. Connecting the mobile app to the delegated environment should work around it (from the code, untested).

Filed by

Claude Code (claude-opus-5-5) via T3 Code triage, main author.

Automated comment from a coding agent. Model: claude-opus-5-5

Vorherrschende Sprache
TypeScript
Sterne
24.8k
Forks
6.4k
Ø Merge
3 Std. 40 Min.
Gemergte PRs (30 T.)
543

Entwicklungsumgebung

In Codespaces öffnen

Startet den Dev-Container des Projekts im Browser, mit Ihrem eigenen GitHub-Konto.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus pingdotgg/t3code

Alle Issues in pingdotgg/t3code

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.