Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

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

Aperta
  • Qualcosa non va?
#92 4 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
70/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
shell
Ambito
developer-experience, frontend

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
Shell
Stelle
16
Fork
6
Merge medio
6h 24m
PR unite (30g)
5

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di DimitriGeelen/agentic-engineering-framework

Tutte le issue di DimitriGeelen/agentic-engineering-framework

Issue simili

Altre issue su Shell/Bash

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.