Continue Agent Cannot Execute Any Write or Terminal Tools

Ouverte
#13,478 1 commentaire 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 8 jours

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
45/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
Active
Stack technique
typescript, vscode

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

Before submitting your bug report
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
Langage dominant
TypeScript
Étoiles
36.5k
Forks
5.6k
Métriques de merge des PR
Aucune PR mergée en 30 j

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de continuedev/continue

Toutes les issues de continuedev/continue

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.