Conversation: aligned authors, @ and / in the composer, swipe left, long press, task notices with source, agent thinking
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, typescript
- Ambito
- accessibility, frontend, testing
Direzione di ricerca
Read the design guide’s §5 and §4, then inspect app/apps/web/src/work/inline.tsx, app/ConversationStream.tsx, app/project-conversation.css, assistant/ConversationParts.tsx, typing/TypingNotice.tsx, and app/ProjectConversation.tsx. The issue says the owner confirms before starting and depends on #338 and #339; coordinate with the owner and check those dependencies first. Run the named UI tests with ./scripts/check_ui.sh, then compare desktop and phone renders and verify keyboard, touch, reduced motion, and contrast against the acceptance criteria.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Part of #336 (F-026, founder direction 2026-10-07). Design guide: docs/design/final (§5 behaviour · §4 structure and navigation; until #337 merges, read the pinned copy). Interactive boards (light/dark toggle, notes): design canvas, page "Prostota".
Outcome
The conversation reads like a calm messenger, and every action on a message is one gesture or key away.
Final design

Acceptance criteria
- AC-1. Every author, person or agent, has a 32 px avatar and their full name in the same position, whether they wrote a message or triggered an event. Cards, bubbles and event text share one left edge (avatar column plus 12 px on the computer, 10 px on the phone). 20 px avatars appear only as owners in task rows.
- AC-2. The composer offers
@to mention and/for actions (/task,/decide,/handoff,/file) and has no separate Ask or Cite buttons (S5). Mention chips align to the text baseline. - AC-3. On the computer, hovering a message shows its actions. On the phone, swipe left reveals Done, Not now, Hand off and Reply in thread, and long press opens Reply in thread, Create task, Hand off to an agent, Cite and Copy text. Nothing swipes right.
- AC-4. A "Since you left: …" line jumps to the first unread item (S7). Several task updates in a row fold into one expandable line (S8).
- AC-5. A new task is announced in one line with its source (P5): "made a task from Jonas's message", "added a task in Tasks", "added 3 tasks on the Map". While an agent composes, a row shows its Kreska thinking expression and Stop.
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
work/inline.tsxMessageActions(always-visible Task / Decision / Result / Details, "⋯" on touch) → hover actions on the computer, swipe left and long press on the phone.app/ConversationStream.tsxNoticeItem("New task · ") → one line with source;streamEntriesfolds consecutive task updates (S8).- Avatars 32 px on both devices (today 27 px on the computer and hidden on the phone,
app/project-conversation.css) and one left edge. assistant/ConversationParts.tsxWorkingLine → Kreska thinking row with Stop.typing/TypingNotice.tsxshows people typing (#155 AC-2, never agents) and keeps doing so.
Remove
- The separate "Sources" (cite) and ✦ ask buttons and the
/aihint in the composer (app/ProjectConversation.tsx).
New
@and/menus in the composer (/task,/decide,/handoff,/file).- The "Since you left" jump line in the stream.
- Agent question cards with ready-made answers (S14).
Tests to rewrite
test_shared_composer.py,test_task_announcements.py,test_file_messages.py,test_one_conversation.py,test_motion.py,test_work_associations.py,test_personal_assistant.py.
Depends on
#338, #339 (tokens and shared components first; independent parts can start earlier).
Related: #154 (the task notice is separate from the first real message; AC-5 draws that behaviour), #155 (typing presence and motion).
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: current avatar sizes and the typing line corrected; cross-links to #154 and #155 added.
- Lingua principale
- TypeScript
- Stelle
- 3
- Fork
- 0
- Merge medio
- 18h 21m
- PR unite (30g)
- 385
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di ColdPhase/flux
-
good first issue
Difficoltà 2/5 1-3 ore Idoneità per principianti 88/100
I maintainer di solito rispondono entro 1 giorno
-
good first issue
Difficoltà 2/5 1-3 ore Idoneità per principianti 95/100
I maintainer di solito rispondono entro 1 giorno
-
good first issue
Difficoltà 2/5 1-3 ore Idoneità per principianti 91/100
I maintainer di solito rispondono entro 1 giorno
-
good first issue
Difficoltà 2/5 1-3 ore Idoneità per principianti 90/100
I maintainer di solito rispondono entro 1 giorno
-
enhancement
Difficoltà 4/5 3-5 giorni Idoneità per principianti 35/100
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di ColdPhase/flux
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
I maintainer di solito rispondono entro 1 giorno
-
Broken links in the docsAperta
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 83/100
I maintainer di solito rispondono entro 1 giorno
-
🔊 a11y
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
betagouv/mon-entreprise#4726 ·
I maintainer di solito rispondono entro 9 giorni
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
Deltares/fews-pi-requests#357 ·
I maintainer di solito rispondono entro 1 giorno
-
bug confirmed js v6
Difficoltà 2/5 1-3 ore Idoneità per principianti 85/100
I maintainer di solito rispondono entro 1 giorno