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

Abierto Apto para principiantes
  • ¿Algo no está bien?
#37,270 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
70/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
typescript
Área
mobile

Línea de trabajo

Empieza en apps/mobile/src/features/threads/SubagentRow.tsx: la fila resuelve el proveedor desde useEnvironmentServerConfig(...) y recurre a provider?.driver ?? subagent.driver, que es el marcador de posición "remote" de apps/server/src/peer/RemoteDelegation.ts. Compáralo con las guardas que ya se usan en thread-subagent-group.tsx (SubagentAvatar) y en ThreadRelationshipsControl.tsx de web (fallbackIcon={BotIcon}), y luego revisa apps/mobile/src/components/ProviderIcon.tsx donde el fallback genérico renderiza el nudo de OpenAI. Terminado se ve así: una fila para una tarea delegada a un entorno desconectado muestra un glifo de robot neutro, no el logo de OpenAI, y lo mismo ocurre con los drivers "remote" que llegan al fallback genérico.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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

Lenguaje dominante
TypeScript
Estrellas
24.8k
Forks
6.4k
Merge medio
3 h 40 min
PR fusionados (30 d)
543

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de pingdotgg/t3code

Todos los issues de pingdotgg/t3code

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.