Scripts & Other

Table of Contents

  1. Jupyter Notebook Details
  2. Guided Argument Input for Scripts
  3. Next Steps

Shell Scripts Python Jupyter Notebook Visual Studio Code

Tool File Patterns Notes
Shell Scripts **/*.{sh,bash,zsh,fish,ps1,bat,cmd} Executable scripts
Extensionless Shell Scripts (no extension) Shebang + executable bit required; opt-in only
Jupyter Notebook **/*.ipynb Notebook cells (discovery works without extension; execution requires Jupyter Extension)
Visual Studio Code Tasks **/.vscode/tasks.json, user-level tasks.json Native VS Code tasks
Workspace Tasks .workspace-tasks.json Custom task templates

Jupyter Notebook Details

  • Discovery: Notebook tasks are discovered from *.ipynb files even if the Jupyter extension is not currently available
  • Requirements for execution: The Jupyter Extension must be installed and a Jupyter Server must be configured
  • Notebooks appear as parent tasks with individual code cells as child tasks
  • Click a task to open the notebook in VS Code’s notebook editor
  • Execute individual cells or entire notebooks
  • Real-time cell execution status via the Jupyter Extension UI
  • Inline CodeLens actions are not supported for .ipynb notebook documents
  • Notebook editor title action buttons from this extension are not supported for .ipynb files

Guided Argument Input for Scripts

Python (.py), PowerShell (.ps1), and Node.js (.js/.mjs/.cjs) scripts support guided argument input β€” instead of typing a raw argument string, the extension parses the script’s parameter declarations and presents each parameter as an individual prompt (input box, QuickPick for choices, Yes/No for flags, etc.).

Enable it in your settings.json:

"workspaceTasks.task.guidedArgInput": true

See the per-language pages for full details:


Next Steps


Table of contents