Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

Edit and delete queued messages, and choose steer, follow-up, or interrupt

Offen
  • Stimmt etwas nicht?
#24 5 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
45/100
Issue-Typ
Feature
Klarheit
Muss geklärt werden
Aktivitätsstatus
Aktiv
Tech-Stack
typescript
Bereich
frontend

Rechercherichtung

The issue is a one-line feature request migrated from the old Ace TODO.md, so start by reading that linked TODO entry and the parity issue #6 plus dogfooding issue #5 to recover the intended behaviour of edit, delete, and steer for messages queued on a busy chat. Then locate the chat message-queue code in this TypeScript repo (search for queued/pending message state and the composer UI) to see where a waiting message is held before send. Done looks like a user can modify, remove, or redirect a message still waiting in the queue, with the existing queue behaviour unchanged.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Edit, delete, or choose how a message waiting on a busy chat is delivered: steer, follow-up, or interrupt now.

Done

  • Queued messages are visible above the composer for everyone in the chat, live and after reconnect (#193, apps/app/src/message-queue.tsx, packages/channel/src/queue.ts), with authors named as the timeline names them (#278). Verified in the two-person study (#218, scenario 10).
  • Every ask to a busy chat is already a steer: packages/channel/src/channel.ts submits with whenBusy: "steer", so pi places it after the current tool round. Another channel's queued handoff also interrupts the chat's shell commands (#400).

Remaining

  • Delete a queued message: its author can withdraw it. pi already has per-submission withdrawal (Submissions.abort(id)); the channel protocol has no op for it.
  • Edit a queued message: withdraw and resubmit in place, keeping its queue position if pi allows, otherwise say it moves to the end.
  • Choose steer (after the current tool round) or follow-up (after the run ends) per message; pi supports whenBusy: "followUp", the app has no control for it.
  • Interrupt now: deliver a queued message right away instead of waiting for the current tool round. In-flight tools get aborted and pi reports them to the model as interrupted, then the run continues with the message. Today a person can only queue (as a steer) or Stop. Stop ends the run and sends queued messages back to their authors' drafts (#433), so they have to resend by hand. Handoffs from other channels already interrupt shell commands (#400, packages/channel/src/handoffs.ts); a person's interrupt should also cover other long tools, and say which ones were cut short (#442).
  • What Stop does to the queue was decided in #279 (fixed in #433).

Dogfooding core/QOL: #5. Also tracked in #6 for old-Ace feature parity. Migrated from TODO.md — Port from old Ace.

Vorherrschende Sprache
TypeScript
Sterne
1
Forks
0
Keine gemergten PRs in 30 T.

Entwicklungsumgebung

  • Kein Dockerfile und keine Docker-Compose-Datei
  • Hat eine Pull-Request-Vorlage
  • Kein Beitragsleitfaden

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus githubnext/ace2

Alle Issues in githubnext/ace2

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.