-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Open
Labels
bugSomething isn't workingSomething isn't working
Description
Bug Description (required)
It seems like Dyad sends two prompts after cancellation: the old one and a new one (the next one after the cancelled generation). It's not an issue if the old prompt doesn't contain any incorrect information or an incorrect implementation order, but if it does, the AI agent tries to process both the incorrect and the corrected prompt, which sometimes leads to loops or, even worse, bad code implementation.
I think that the old prompt doesn't need to be deleted when the user presses the "Cancel generation", but needs to be ignored in the next messages and dimmed out to indicate that this is the ignored prompt (but the user would still see and copy needed info from the cancelled prompt, if needed).
Steps to replicate:
- Write the wrong prompt with the "AAA" mistake
- Cancel the generation of output
- Add a new prompt with "BBB" corrected information
- See how the AI Agent still includes the wrong information in the count.
System Information
- Dyad Version: 0.40.0
- Platform: win32
- Architecture: x64
- Node Version: v22.14.0
- PNPM Version: 10.15.0
- Node Path: C:\Program Files\nodejs\node.exe
- Pro User ID: n/a
- Telemetry ID: b6a2441f-ac6f-4507-b7a5-eb5db9c3774a
- Model: custom::minimax:MiniMax-M2.7 | customId: 14
Settings
- Selected Model: custom::minimax:MiniMax-M2.7
- Chat Mode: build
- Auto Approve Changes: true
- Dyad Pro Enabled: n/a
- Thinking Budget: high
- Runtime Mode: n/a
- Release Channel: stable
- Auto Fix Problems: true
- Native Git: true
Logs
}
[2026-03-21 23:46:36.263] [error] (pro_handlers) LLM Gateway API key (Dyad Pro) is not configured.
source: 'remote',
version: '2026-03-21T20:02:57.079Z',
expiresAt: '2026-03-21T21:02:57.079Z'
}
source: 'remote',
version: '2026-03-21T20:02:57.079Z',
providerCount: 6
}
source: 'remote',
version: '2026-03-21T20:02:57.079Z',
expiresAt: '2026-03-21T21:02:57.079Z'
}
source: 'remote',
version: '2026-03-21T20:02:57.079Z',
providerCount: 6
}
[2026-03-21 23:46:38.626] [error] (tsc) TSC worker exited with code 1 for app C:\Users\User\dyad-apps\********
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working