Continue Agent Cannot Execute Any Write or Terminal Tools
Maintainers usually reply within 8 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript, vscode
- Domain
- developer-experience, tooling
Research direction
Start by tracing the approval and execution path for create_new_file, edit_existing_file, and run_terminal_command in the Continue VS Code extension; the issue does not identify relevant source files. Reproduce the immediate cancellation with a minimal write call, then inspect the UI and logging paths to find why no approval prompt or error appears. Done means identifying the cancellation path and a way to capture its underlying reason.
Written by the indexing model from the issue text.
Description
Before submitting your bug report
- I've tried finding an answer on the Continue docs site
- I'm not able to find an open issue that reports the same bug
- I've seen the troubleshooting guide on the Continue Docs
Relevant environment info
Description
Continue Agent Cannot Execute Any Write or Terminal Tools ("The user cancelled this tool call")
Environment
Continue Extension: v2.1.0 (Pre-Release)
VS Code: Current version
Provider: OpenRouter
Models tested:
qwen/qwen3.8-flash
anthropic/claude-sonnet-4.5
Workspace: Trusted
OS: Windows
Agent Mode: Enabled
Problem
Continue can successfully use read-only tools, but every mutating tool is rejected immediately with:
The user cancelled this tool call.
No approval dialog is shown.
Working Tools
read_file
ls
grep_search
codebase
file_glob_search
Other read-only tools
Failing Tools
create_new_file
edit_existing_file
run_terminal_command
Failure Pattern
Every write or execute tool fails instantly.
Read operations succeed consistently.
The failure is independent of:
file path
file size
file contents
workspace location
Minimal Reproduction
Prompt:
Plain Text
Create a file named test123.txt containing the word hello
Agent response:
Plain Text
Continue tried to create test123.txt
Result:
Plain Text
The user cancelled this tool call.
No approval popup appears.
Additional Evidence
Workspace Trust
The workspace is explicitly marked as:
Plain Text
You trust this folder.
All features are enabled because trust has been granted to the workspace.
Tool Availability
The model can see and attempt to use write tools.
Example configuration:
YAML
models:
- name: "Qwen: Qwen3.8 Flash"
provider: openrouter
model: qwen/qwen3.8-flash
capabilities: - tool_use
- name: "Anthropic: Claude Sonnet 4.5"
provider: openrouter
model: anthropic/claude-sonnet-4.5
capabilities: - tool_use
Extension Settings
Experimental tools: ON
Only use system message tools: OFF
Agent mode enabled
Comparison
Another VS Code agent (Cline) can successfully:
create files
edit files
execute tools
in the exact same workspace.
This suggests the issue is specific to Continue's execution/approval layer rather than filesystem permissions or Workspace Trust.
Question
What code path in Continue returns:
Plain Text
The user cancelled this tool call.
without displaying an approval UI?
Is there a way to enable logging for the underlying reason that caused the cancellation?
To reproduce
No response
Log output
Apply
Isolated repro on a clean, trivial call:
create_new_file(filepath="test123.txt", contents="hello")
-> "The user cancelled this tool call." (instant, no prompt shown)
Immediately prior, in the same session:
read_file, ls, grep_search, file_glob_search -> all succeed
So: tool definitions for write/execute ARE present; the model IS
emitting valid calls; only the mutating tools are refused, and the
refusal is attributed to the user who never saw a dialog.
Toggled and re-tested: "Only use system message tools" ON and OFF,
"Enable experimental tools" ON, "Stream after tool rejection" ON,
mode = Agent (system prompt reads "You are in agent mode").
VS Code Workspace Trust: reported as trusted.
Question: which code path in Continue returns "The user cancelled
this tool call" without displaying an approval UI, and how do I
capture the underlying reason (Continue: View Logs produced no
error line)?
That last clause matters: if the logs also show nothing, the
rejection is happening *before* logging, which is characteristic
of a UI-layer auto-cancel rather than a backend permission check.
## Consequences for the repo, unchanged
- **Nothing has been applied.** No file modified, no task touched.
`test123.txt` does not exist — I cannot delete it either.
- The `P0…P5` package remains the way forward, given to any agent
with working tools.
- The one thing you can do yourself right now, in your own
terminal (human-run commands aren't affected):
cd c:\trading-bot
Get-Content logs\zombie_cleanup_kills.log -Tail 40
- Dominant language
- TypeScript
- Stars
- 36.5k
- Forks
- 5.6k
- PR merge metrics
- No merged PRs in 30d
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 continuedev/continue
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
continuedev/continue#13486 ·
Maintainers usually reply within 8 days
-
Chat panel overflows horizontally when VS Code zoom level is increased (Cmd/Ctrl + +)Possibly taken @tang-ontheway claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
continuedev/continue#13483 ·
Maintainers usually reply within 8 days
-
Docs: show tool selection for a shared remote MCP endpointPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
continuedev/continue#13464 · 1 comment ·
Maintainers usually reply within 8 days
-
Inline code becomes unreadable in VS Code high-contrast themesPossibly taken @aminesayagh claimed this 21 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
continuedev/continue#13424 ·
Maintainers usually reply within 8 days
-
create_new_file writes a JSON file on one line when the model sends its contents as a JSON valuePossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
continuedev/continue#13363 ·
Maintainers usually reply within 8 days
All issues in continuedev/continue
Similar issues
-
area-templates triage:bot-seen triage:needs-human
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
microsoft/aspire#22356 · 1 comment ·
Maintainers usually reply within 1 day
-
Archiving an agent that is not loaded keeps its old updatedAtPossibly taken @luoph claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
content triage
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
contributor: external needs review severity: low
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
JSPrismarine/JSPrismarine#3214 ·
Maintainers usually reply within 1 day