Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

[Bug]: Swift iOS: tapping a delegated task in the Agents sheet fails with thread_not_found

Abierto Apto para principiantes
  • ¿Algo no está bien?
#17,643 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
swift
Área
api, mobile

Línea de trabajo

Empieza en apps/swift-ios/Core/OrchestrationV2Client.swift en threadPath (alrededor de la línea 325), que codifica en porcentaje el ID del hilo una vez, y en apps/swift-ios/Core/HTTP.swift en endpoint (alrededor de la línea 767), que asigna esa ruta ya codificada a URLComponents.path y la vuelve a codificar. Cambiar endpoint para que establezca percentEncodedPath debería solucionarlo. Se considera terminado cuando una prueba de regresión demuestre que el ID de hilo thread:a%3Ab produce la ruta de solicitud /api/orchestration/threads/thread:a%253Ab/bounded, y cuando los hilos de tareas delegadas se abran en la aplicación.

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

Descripción

Opened on behalf of Ben by Claude Code (Opus 5.5).

Before submitting
  • I searched existing issues and did not find a duplicate.
  • I included enough detail to reproduce or investigate the problem.
Area

apps/mobile (experimental SwiftUI client, apps/swift-ios)

Steps to reproduce
  1. In a thread on a desktop host, have the agent call the delegate_task MCP tool (for example a Codex child task) and let it finish.
  2. On iPhone, open the same thread in the Swift app (TestFlight).
  3. Open the Agents sheet. The delegated task shows as Completed.
  4. Tap the task row.
Expected behavior

The child thread opens, the same as it does on web and desktop.

Actual behavior

The app shows Could not open thread: thread_not_found. The child thread exists. t3_thread_read and desktop both open it.

Delegated-task thread IDs contain literal % characters, for example thread:delegated-task:command%3Amcp%3A<uuid>%3Adelegate-task%3A<clientRequestId>. The Swift client percent-encodes the ID twice, so it requests a thread that does not exist:

GET /api/orchestration/threads/thread:delegated-task:command%25253Amcp%25253A…/bounded

The server decodes the path once and looks up command%253Amcp… instead of command%3Amcp….

On t3code/rebuild-mobile-app-swift @ 52912fe7e3:

  1. apps/swift-ios/Core/OrchestrationV2Client.swift:325 (threadPath) encodes the ID once. It removes /?#% from .urlPathAllowed, so %3A becomes %253A and : is left alone.
  2. apps/swift-ios/Core/HTTP.swift:767 (endpoint) assigns that already-encoded path to URLComponents.path. That setter expects an unencoded path and escapes % again, so %253A becomes %25253A.

HTTPClient.threadSnapshot (HTTP.swift:274) pre-encodes with .urlPathAllowed and goes through the same endpoint, so it double-encodes too. Ordinary thread IDs are UUIDs with nothing to escape, which is why only delegated-task children (and any other ID containing %) hit this.

A likely fix is to set components.percentEncodedPath = path in endpoint and keep the per-segment encoding in threadPath. Fixed paths such as /api/orchestration/shell are already valid encoded paths, so they are unaffected. A regression test could assert that thread ID thread:a%3Ab produces the request path /api/orchestration/threads/thread:a%253Ab/bounded.

Impact

Major degradation or frequent failure

Version or commit

Swift app: TestFlight build 60 (code reference: t3code/rebuild-mobile-app-swift @ 52912fe7e3). Server: 0.0.46-nightly.20261008.2849.

Environment

iOS 27, iPhone. macOS host running the Nightly desktop app, connected over Tailscale HTTPS. Child task: Codex gpt-6.1-sol.

Logs or stack traces
# server.trace.ndjson, http.server GET
http.route: /api/orchestration/threads/:threadId/bounded
url.path:   /api/orchestration/threads/thread:delegated-task:command%25253Amcp%25253A9dd2e492-724d-437f-b41a-cdc6ec10ec65%25253Adelegate-task%25253Averify-t3-workflow-vs-flowition-r1/bounded
user_agent: T3Code/60 CFNetwork/3896.100.1.2.1 Darwin/27.0.0

# sql.transaction failure
ProjectionStoreThreadNotFoundError: No orchestration projection exists for thread thread:delegated-task:command%253Amcp%253A9dd2e492-724d-437f-b41a-cdc6ec10ec65%253Adelegate-task%253Averify-t3-workflow-vs-flowition-r1.

# actual thread ID
thread:delegated-task:command%3Amcp%3A9dd2e492-724d-437f-b41a-cdc6ec10ec65%3Adelegate-task%3Averify-t3-workflow-vs-flowition-r1
Workaround

Open the child thread from desktop or web.

Lenguaje dominante
TypeScript
Estrellas
24.8k
Forks
6.4k
Merge medio
10 h 41 min
PR fusionados (30 d)
352

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.