Feature settings
Toggle optional capabilities that extend what Test Companion can do, including checkpoints, notifications, and Electron testing support.
Feature settings lets you toggle optional capabilities that extend what Test Companion can do. Each feature here adds a specific type of functionality — workspace snapshots, desktop notifications, or Electron app testing support. You can enable or disable them independently based on your needs.
How to open Settings
-
Click the gear icon (⚙) in the top-right corner of the Test Companion panel.

-
Select the Feature Settings tab.

- Make the necessary changes and click Save to apply them.
- Click Cancel to discard any unsaved changes.
Enable Checkpoints
When checkpoints are enabled, Test Companion automatically creates a snapshot of your workspace files at important moments while it works on a task — for example, before modifying a file or before running a command that could change your project state. If the AI makes a change you are unhappy with, you can revert to an earlier checkpoint instead of manually undoing the changes.
| Setting | Details |
|---|---|
| Field type | Checkbox |
| Default value | Enabled (checked) |
| What it does | Saves snapshots of your workspace at key points during a task, so you can roll back if something goes wrong. |
Under the hood, checkpoints use Git to track workspace state. The extension creates lightweight commits behind the scenes to mark each checkpoint.
When to enable this
Checkpoints are valuable in most situations and are enabled by default. They are especially useful when:
- You are letting the AI work autonomously in Default interaction mode
- The AI is making changes across multiple files at once
- You are experimenting with different approaches and want to easily backtrack
When to disable this
There are specific cases where you may want to turn checkpoints off:
- Very large workspaces: If your repository is exceptionally large (for example, a monorepo with tens of thousands of files), the Git operations behind checkpoints can slow down. If you notice sluggish performance during tasks, try disabling checkpoints.
- Non-Git projects: If your workspace is not a Git repository and you do not want one to be initialized, disable this feature.
Enable Notifications
This is particularly useful when you start a task and then switch to another window or application while the AI works. Instead of periodically checking back, you receive a notification that brings you back to VS Code at exactly the right moment.
| Setting | Details |
|---|---|
| Field type | Checkbox |
| Default value | Disabled (unchecked) |
| What it does | Sends you a system notification when Test Companion needs your approval to continue, or when a task is completed. |
Example use case
You ask Test Companion to generate a full test suite for your user registration module. You switch to your browser to review the application’s UI while the AI works. A few minutes later, you receive a desktop notification: “Test Companion requires approval to proceed.” You switch back to VS Code and see that the AI wants to create a new file — you approve, and it continues.
When to enable this
- When you multitask and frequently switch away from VS Code while the AI is working
- When using Guided mode, where the AI pauses at each step for approval
- For long-running tasks where you want to be alerted upon completion
Enable Electron
Electron is a framework used to build cross-platform desktop applications with web technologies (HTML, CSS, JavaScript). Many popular applications, such as VS Code itself, Slack, and Figma, are built on Electron.
| Setting | Details |
|---|---|
| Field type | Checkbox |
| Default value | Disabled (unchecked) |
| What it does | Enables testing of Electron-based desktop applications, including VS Code extensions and custom desktop apps. |
When this setting is enabled, Test Companion can understand and interact with Electron application structures, including:
- Testing VS Code extensions within the Extension Host
- Interacting with custom Electron app windows
- Analyzing Electron-specific APIs and IPC (inter-process communication) patterns
- Generating tests that account for Electron’s main process and renderer process architecture
When to enable this
- You are developing a VS Code extension and want to generate or debug tests for it
- You are building a desktop application using Electron and need testing assistance
- Your test automation needs to interact with Electron application windows
When to leave it disabled
If your testing work is limited to web applications and mobile apps (the most common use case), leave this disabled. Keeping it off avoids any unnecessary overhead or unintended Electron-related suggestions from the AI.
We're sorry to hear that. Please share your feedback so we can do better
Contact our Support team for immediate help while we work on improving our docs.
We're continuously improving our docs. We'd love to know what you liked
We're sorry to hear that. Please share your feedback so we can do better
Contact our Support team for immediate help while we work on improving our docs.
We're continuously improving our docs. We'd love to know what you liked
Thank you for your valuable feedback!