(bug) The Stop button disappears for a moment before an approval card shows
Maintainers usually reply within 1 day
@rishu685 is already working on this.
Since Oct 8, 2026.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
- Domain
- frontend
Research direction
The issue identifies the composer in /m but does not name a source file or test. Start by tracing how the composer renders the Stop button during the Thinking state and while an approval is pending, then look for related frontend tests. Done when the button remains visible through the transition to the approval card; verify by reproducing the listed Ask-policy scenario.
Written by the indexing model from the issue text.
Description
In /m, the Stop button disappears for a moment between the "Thinking" state and the approval card. The button flickers, and the user cannot press Stop during that gap.
Reproduce
- Open an agent in /m with the permission policy Ask.
- Ask for a command that needs approval, for example "Use the bash tool to run exactly: echo X".
- Watch the composer from the moment you send until the approval card shows.
Expected
The Stop button stays visible for the whole time the turn is active, including the moment before the approval card shows.
What we saw (v0.122.4 release candidate QA, /m)
The Stop button shows while the agent is "Thinking", goes away for a short time, and comes back with the approval card. The gap is short but visible.
Related: #7425 (the session tab keeps a stale status after Stop or after an approval). That issue is about the tab label. This one is about the composer button.
🤖 The AI agent says: filed from the v0.122.4 release QA.
- Dominant language
- TypeScript
- Stars
- 4.8k
- Forks
- 690
- Avg merge
- 19h 50m
- Merged PRs (30d)
- 419
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Agenta-AI/agenta
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Agenta-AI/agenta#7468 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Agenta-AI/agenta#7441 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
bug frontend
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Agenta-AI/agenta#7426 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
No CI job runs the mobile app's unit testsPossibly taken @Mahaboob-Ashraf claimed this 4 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Agenta-AI/agenta#7326 · 2 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
Agenta-AI/agenta#7074 · 1 comment · 2 reactions ·
Maintainers usually reply within 1 day
All issues in Agenta-AI/agenta
Similar issues
-
affected/v17 affected/v18 area/frontend type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
umbraco/Umbraco-CMS#24186 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
better-auth/better-auth#11723 · 1 reaction ·
Maintainers usually reply within 1 day
-
area: docs difficulty: easy documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Worker-Erstellung bricht langsame Git-Worktree-Checkouts nach 20 Sekunden abPossibly taken @KajoVanBuyten claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
AgentSystemLabs/agent-office#367 ·
Maintainers usually reply within 1 day