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

[Feature]: Task board column for "agent done, waiting for the human's review"

Abierto
  • ¿Algo no está bien?
#92 4 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
70/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
shell
Área
developer-experience, frontend

Línea de trabajo

Start with web/templates/tasks.html around line 498 and the task grouping logic in web/blueprints/tasks.py; trace how the board renders statuses and how partial completion and count_human_acs are computed. Add a derived Awaiting review grouping for started-work tasks with all Agent criteria ticked and at least one Human criterion unticked. Verify the board separates those tasks from In Progress without adding a status.

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

Descripción

area:watchtower enhancement severity:low status:released triaged
Problem

The Watchtower task board cannot tell "the agent is working on it" from "it is waiting for my review".

The board has four columns, one per status: Captured, In Progress, Issues, Completed (web/templates/tasks.html, line 498). A task whose ### Agent criteria are all ticked and whose ### Human criterion is still open stays started-work, so it sits in In Progress next to the tasks the agent is still working on.

Observed: eleven cards in In Progress; for seven of them the agent's work was finished and only a Human criterion was left. Nothing on the board distinguished the seven from the four. The operator asked: "can we add a column to tell in progress for you from in review for me?"

Proposed Solution

Derive a fifth column, for example "Awaiting review", without adding a status: a task is shown there when its status is started-work, all ### Agent criteria are ticked and at least one ### Human criterion is unticked. The framework already computes this state (the partial-complete case, and count_human_acs used in web/blueprints/tasks.py), so the board would only need to group on it.

A count of unticked Human criteria on each card would be a smaller step in the same direction.

Subsystem

Watchtower (Web UI)

Scope

Medium (few files, 1-4 hours)

Alternatives Considered
  • Workaround in use: set owner: human on every task whose agent work is finished, and use the owner label and the owner=human filter. It works, but it overloads owner (it now means "whose turn it is", not "who is accountable"), and nothing sets it automatically.
  • /approvals lists the pending Human criteria, but as a separate page, not as a position on the board.
Additional Context

Version: 1.8.6 (1ea10441f), vendored consumer. First seen on 1.8.3; web/templates/tasks.html and web/blueprints/tasks.py are byte-identical between the versions. Checked again on the served board of 1.8.6: four columns. The suggestion was not prototyped.

Lenguaje dominante
Shell
Estrellas
16
Forks
6
Merge medio
6 h 24 min
PR fusionados (30 d)
5

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 DimitriGeelen/agentic-engineering-framework

Todos los issues de DimitriGeelen/agentic-engineering-framework

Issues similares

Más issues de Shell/Bash

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.