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

Hand-off to an agent in two steps, and the Agents view as one list

Aperta
  • Qualcosa non va?
#347 2 commenti 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@PelikanFix16 ci sta già lavorando.

Dal 8/10/2026.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
python, react, sql, typescript
Ambito
backend-api-design, databases, frontend

Direzione di ricerca

Start with app/apps/web/src/agents/ProjectAgents.tsx and app/apps/web/src/work/WorkDetails.tsx, then review the design guide and its §5 behavior. Rewrite test_agents_view.py, test_grant_controls.py, and test_project_policy.py; run ./scripts/check_ui.sh and ./scripts/check_application.sh when data paths change. Done means the acceptance criteria work across desktop and phone, light and dark, with interaction and accessibility checks.

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

Descrizione

agent:ready enhancement

Part of #336 (F-026, founder direction 2026-10-07). Design guide: docs/design/final (§5 behaviour · §3 kreska logo agent icon and mascot; until #337 merges, read the pinned copy). Interactive boards (light/dark toggle, notes): design canvas, page "Prostota".

Outcome

Handing work to an agent is two steps, and the Agents view shows who is doing what.

Final design

desktop-handoff desktop-agents phone-handoff phone-agents phone-agentdetail

Acceptance criteria

  • AC-1. Hand-off has two steps: choose the agent, then see what it may do (its grant in this place), then confirm (S12). On the computer a task can also be dragged onto an agent.
  • AC-2. Agents is one list (P9): each row shows the agent with its colour, its owner and what it is doing now. Below are one row each for Requests, Policy and "Connect your own agent", and one primary button, "Hand off a task".
  • AC-3. A working agent is always visible with Stop (S13): in the sidebar card, on Home, and in the conversation header on the phone.
  • AC-4. An agent's question is a card with ready-made answers (S14). Answering it records the reply in the same thread.
  • AC-5. Agent details open in the detail panel or sheet and show its owner, its grant, its current work and its history.

What changes in the code today

From a read of main at 3c553b79; the owner confirms before starting. Paths are under app/apps/web/src, public/ is app/apps/web/public, root scripts/ and tests/ are the repository's, and UI tests are in app/tests/ui.

Change

  • agents/ProjectAgents.tsx ("Working together", "Connect my agent", connection list with dots, task picker, inline thread) → the P9 list with Requests, Policy, Connect rows and "Hand off a task".
  • Hand-off is only the Owner <select> in work/WorkDetails.tsx today → the two-step dialog.

Remove

  • Connection dots and terminal icons as agent identity.

New

  • Two-step hand-off dialog and desktop drag of a task onto an agent.
  • An index on agent_command_receipts (connection_id, project_id, completed_at) for the Agents view's last-activity query (app/packages/db/src/repositories/project-agents.ts around lines 104–109; the table in migration 0034 has only its primary key). Carried over from the #183 review.
  • Stop for any working agent (today only the personal assistant run has Stop) in the sidebar card, Home and the phone conversation header.

Tests to rewrite

  • test_agents_view.py, test_grant_controls.py, test_project_policy.py.

Depends on

#339, #344 (tokens and shared components first; independent parts can start earlier).

How to test

./scripts/check_ui.sh            # browser suite; add the new or changed tests
./scripts/check_application.sh   # when API or data paths change
python3 scripts/check_agent_setup.py && git diff --check

Compare with the renders above at 1440 × 900 and 390 × 844 CSS px, in light and dark, on ./flux demo data, then get an independent visual review with a neutral brief (guide §9). Screenshots do not prove interaction or accessibility, so also test keyboard, touch (Chromium and WebKit emulation), reduced motion and contrast in the running app.

Owner: whoever claims it (assign yourself and comment once). Evaluator: the other agent. The design is a founder direction: implement it as drawn; raise a conflict with a functional contract on #336 instead of changing the design.

Updated 2026-10-07: carries the last-activity index follow-up from the #183 review.

Lingua principale
TypeScript
Stelle
3
Fork
0
Merge medio
22h 53m
PR unite (30g)
272

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 ColdPhase/flux

Tutte le issue di ColdPhase/flux

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.