Skip to content

fix(chat): Reports no answer after a reply already landed #681

Closed

Description

@omesser

Problem

The Chat surface wrote No answer came back. under a turn that already had a Buddy Bot reply.

Reproduced 2026-09-14 on Codex, Buddy Bot, Blank AI on. Same minute (16:50):

  1. You: may I hoop you?
  2. You: Help*
  3. Buddy Bot: You may! Tell me one thing that would make me a more useful little buddy.
  4. Then the note: No answer came back.

Chat: Buddy Bot replied, then the surface wrote No answer came back.

The Speech is in the log. The note is a lie.

src/chat.js paints that string only when a waiting caret is settled with said empty and no error. The Shell emits ChatReply { said: None, busy: false, error: None } from several frame-loop sites — a line nothing can ask, Do Not Disturb, a superseded wake starting (ADR-0016), a missing Instance. Any of those after a real line has already been drawn will consume the next waiting turn and claim nothing came back.

Two typed lines in one minute is enough to leave a second caret. A Harness that speaks via speak and then times out or is superseded is enough to send the empty payload. #514 already called this report wrong when the Harness did answer with an error; this is the same lie when the buddy did speak.

Proposal

Do not write No answer came back. when this window has already drawn Speech for that question — or when the empty payload is “we cancelled you because a newer wake started,” which is not “no answer.”

The waiting queue and the emit sites have to agree: one caret, one outcome. A superseded typed line should say it was dropped for the next question, or take no note at all if the reply that landed is the one on screen. A Completer timeout after speak already filled the bubble is not a silent Static fallback as far as the log is concerned.

Done when

  • The sequence above (two typed lines, one Buddy Bot reply) does not append No answer came back.
  • A superseded caret is either silent or named as superseded — never as a missing answer.
  • A turn that really produced no Speech (failed Completer, Do Not Disturb, nothing to ask) still says so.
  • A test covers “Speech already in the log, then said: None” so the note cannot come back.

— Cursor agent (Grok), on @omesser's behalf.

Activity

  1. added
    bugSomething isn't working
    p1Next up: the default for work that should happen
    on Sep 14, 2026
  2. added this to the V1 milestone on Sep 14, 2026
  3. moved this from 👷 Todo to 🏗 In Progress in Fidgeton Sep 14, 2026
  4. moved this from 🏗 In Progress to 🏁 Done in Fidgeton Sep 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingp1Next up: the default for work that should happen

    Projects

    • Status
      Done

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions