[FEATURE]: Filter session lists by last execution outcome

Abierto
#65,386 1 comentario 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
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
48/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
typescript
Área
api

Línea de trabajo

Start from packages/schema/src/session.ts (lines 32-109) to see Session.Info.outcome and the existing list filter/cursor shapes, then find where session.list applies the project/directory and archive filters and where the pagination cursor is built. Done means an outcome filter applied before pagination, combined with the existing filters, retained in cursors, and treating sessions with no completed execution as non-matching, covered by tests for succeeded, failed and interrupted.

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

Descripción

area/sdk-api type/feature version/v2
Feature hasn't been suggested before.
  • I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request

Please let API clients filter session lists by the last completed execution outcome: succeeded, failed, or interrupted.

After running several automated tasks, a client needs to find the sessions that failed. Session.Info already returns outcome, but session.list cannot filter by it. The workaround is to fetch every page and filter locally; filtering just one page can hide older failures.

Apply the filter before pagination, combine it with existing project/directory and archive filters, and retain it in pagination cursors. Its meaning should match the existing field: the outcome recorded at time.idle, not whether the session is currently running. Sessions without a completed execution would not match a requested outcome.

This is a list/query enhancement; it would not retry or resume sessions. Current contracts: Session.Info and list filters. Related #63518 concerns CLI archive filtering, rather than execution outcomes.

Lenguaje dominante
TypeScript
Estrellas
227k
Forks
30.7k
Merge medio
3 h 57 min
PR fusionados (30 d)
484

Preparar el entorno

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 anomalyco/opencode

Todos los issues de anomalyco/opencode

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.