continuedev / continuedev/continue

Accept buttons

Open
#13,075 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
36k
Forks
5.4k
PR merge metrics
No merged PRs in 30d

Description

Type: Bug

Coming from a Cursor environment, I was accustomed to accept buttons that allowed at least a temporary override for most operations. As I continue with the migration to VSCodium I am frequently plagued by these buttons popping up sometimes three or more at a time at unpredictable intervals. The buttons offer no alternatives such as "always accept" or "stop bugging me." The end effect is to significantly curtail a useful workflow. For instance, I can give the ai a research task that might involve searching several sources of information, including files, websites, networked devices, etc. I would expect to set it on its task, and come back 10 minutes later and find the result. That will never happen because the first file access stopped the entire process and has caused the ai to pause and wait for my okay to continue. This continues for dozens of repeats, so I have to sit there and play nursemaid to the user interface. To make this user friendly, I need a work-around, or some new buttons.

Extension version: 2.0.0
VSCodium version: VSCodium 1.126.04524 (4c0b0c6cc561d2d3636d1ec250935431876ce4dc, 2026-06-23T01:46:13Z)
OS version: Darwin arm64 24.6.0
Modes:

System Info
Item Value
CPUs Apple M2 Max (12 x 2400)
GPU Status 2d_canvas: enabled
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_graphite: enabled_on
trees_in_viz: disabled_off
video_decode: enabled
video_encode: enabled
webgl: enabled
webgpu: enabled
webnn: disabled_off
Load (avg) 2, 2, 2
Memory (System) 64.00GB (0.33GB free)
Process Argv
Screen Reader no
VM 0%

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file, test, or entry point is named. Reproduce the repeated accept prompts in the reported VSCodium and extension versions, then trace the UI flow that pauses agent operations. Done requires an agreed way to avoid repeated interruptions, but the exact button behavior and acceptance scope still need clarification.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript, vscode
Domain
developer-experience, devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.