Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
There is no single VS Code settings bundle that makes AI-generated code reliable. A safer baseline is to keep personal preferences in user settings, put agreed project conventions in workspace settings, choose save and formatting behavior that matches the project, and leave unfamiliar repositories in Restricted Mode until you have reviewed them. Profiles can keep different project setups separate, while AI controls must be checked for the specific feature or extension you use.
Start with the right settings scope
VS Code settings can affect one developer’s whole editor setup or just a particular project. Choosing the right scope helps avoid surprising teammates and makes it easier to understand why a value is—or is not—taking effect. User settings apply broadly. Workspace settings are stored with the project and override user settings when both define the same setting. Extensions can contribute their own settings and scopes, so precedence is not always limited to those two levels. Microsoft’s settings documentation explains the available scopes and precedence rules.
As an Amazon Associate I earn from qualifying purchases.
Put personal preferences in user settings
Use user settings for choices you want to follow you across projects, such as editor appearance or personal editing preferences. These are a poor place for a project’s required formatter or other convention: a different repository may expect different behavior, and a personal global value can make that conflict harder to spot.
User scope is also useful for preferences that should not be committed with project files. If you experiment with an AI extension, a user-level choice may affect every folder you open, so confirm that this broad reach is intentional. When moving to a new project, assume your user settings are still active until a workspace or language-specific value replaces them.
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
Put shared conventions in workspace settings
Use workspace settings for project-specific choices the team wants contributors to share, such as a language-specific formatter selection. In a multi-root workspace, check the scope of the setting as well as which folder or workspace owns it. A workspace value generally overrides a conflicting user value, but language-specific overrides and extension-contributed settings can affect the result. If the editor behaves differently from what you expect, inspect the setting’s scope and effective value in the Settings editor rather than assuming the project file is the only source.
Workspace settings live with the project, which makes them useful for shared conventions but also means they deserve review when you open an unfamiliar repository. Do not treat a checked-in editor setting as proof that a project is safe or that every contributor has the same extensions installed. A workspace can express a preferred formatter, while each contributor’s installed extensions determine whether that formatter is actually available.
A simple scope decision
| Question | Prefer user settings when… | Prefer workspace settings when… |
|---|---|---|
| Who should feel the effect? | Only you should see it across your projects. | Contributors to this project should share the convention. |
| How stable is the choice? | It is a personal preference that follows your working style. | It is tied to the repository’s language, tools, or review rules. |
| What happens in another repository? | The same behavior is still desirable. | Another project may require a different value. |
| What should you inspect first when behavior differs? | Check whether a workspace or language-specific value overrides it. | Check the effective value, folder, language override, and extension contribution. |
This distinction prevents a common failure mode: a global formatter silently rewriting a project that expects another style, or a project setting changing your behavior in every folder because you placed it at the wrong scope.
Choose save behavior deliberately
Auto Save and formatting on save are separate controls. Auto Save determines when VS Code saves edits; formatting on save determines whether formatting runs during a save. You can use either, both, or neither. Their behavior should match the way you and your team review changes, not an assumption that more automation always improves code.
| Choice | What it does | Useful when | Trade-off to check |
|---|---|---|---|
| Auto Save: off | Saves happen when you explicitly save. | You want a deliberate save point before reviewing or committing edits. | Unsaved changes remain until you save them. |
| Auto Save: afterDelay | Saves after a delay; Microsoft documents a default delay of 1000 ms. | You want edits saved automatically after a short pause. | That delay is a product default, not evidence of a reliability or productivity improvement. |
| Auto Save: onFocusChange | Saves when the editor loses focus. | You prefer a save when moving away from the editor. | Review when a focus change will save edits in your workflow. |
| Auto Save: onWindowChange | Saves when the VS Code window loses focus. | You want saving tied to switching away from the application window. | Switching windows can trigger a save even when you did not intend to make a separate save decision. |
These Auto Save options and the documented delay are described in Microsoft’s basic editing documentation. No official figure cited there establishes that one option produces more reliable AI-assisted code than another.
Set Auto Save to suit review and recovery
To choose the behavior, open Settings and search for Files: Auto Save. The corresponding JSON setting is files.autoSave; its documented choices are off, afterDelay, onFocusChange, and onWindowChange. If you use afterDelay, files.autoSaveDelay controls the delay in milliseconds. The documented default is 1000 ms; that is a setting default, not a recommendation for every team.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →For example, an explicit-save setup can be represented as {"files.autoSave":"off"}. A delayed setup can be represented as {"files.autoSave":"afterDelay","files.autoSaveDelay":1000}. Put an example in the appropriate user or workspace settings file only after deciding which scope fits. If you paste JSON into an existing settings file, preserve valid JSON syntax and merge the entries rather than adding a second conflicting setting.
Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
Think through what an AI-assisted edit looks like in your chosen mode. With explicit saves, you can ask for a change, inspect the proposed diff, and save only after deciding it belongs. With delayed or focus-based saving, an edit may be written while you are switching files or reviewing another part of the change. Neither approach is inherently safer; the important point is that everyone involved understands when a file becomes part of the saved working tree.
Separate saving from committing
Saving a file does not approve an AI-generated change, and none of the Auto Save modes performs code review. Keep your normal diff review, tests, and approval process in place. If a formatter runs on each save, expect the saved diff to include formatting as well as the requested code change. A deliberate save mode can make that boundary easier to see; an automatic mode can reduce the chance of leaving work unsaved. Choose according to the project’s review and recovery habits.
Use format-on-save only with an accepted formatter
The editor.formatOnSave setting can run formatting when a file is saved. It does not itself select a formatter, and it does not guarantee that the formatter’s output is accepted by the project. Turn it on when the relevant language has a configured formatter and the team accepts that formatter’s changes. Otherwise, formatting may produce unwanted diffs, fail because no formatter is available, or apply a style that conflicts with project conventions.
Recommended Free Tools
Check the formatter before enabling it
- Open a representative file in the language you want to configure.
- Use the Settings editor to find
Editor: Format On Save, or seteditor.formatOnSavein the intended user or workspace scope. - Check which formatter is selected for that language. A project may use a language-specific setting or an extension to provide its formatter.
- Format a small, reviewable change and inspect the diff. Confirm that the output matches the project’s accepted style before applying the setting across the workspace.
VS Code supports built-in formatters for JavaScript, TypeScript, JSON, HTML, and CSS. Other languages may require an extension. A formatter can also come from an extension, so the behavior depends on the installed tooling as well as the save setting. Microsoft describes the formatting and save options in its basic editing guide.
Choose manual formatting when the project is inconsistent
Format-on-save is convenient when the repository has one accepted formatter and contributors expect its output. Manual formatting is often easier to reason about when a project is migrating styles, contains generated files, or uses different conventions by language. You can still format a selected file or change when you are ready, while avoiding an automatic rewrite every time an AI tool touches the document.
Language-specific settings are important in mixed repositories. A JavaScript formatter that is appropriate for one folder may not be appropriate for a JSON, HTML, or CSS file, and an extension-provided formatter may be required for another language entirely. If only some files format, check the language mode, the effective setting for that language, and whether the expected formatter extension is installed and enabled.
Formatting is not a correctness check. It can make generated code conform to a style, but it cannot establish that the code is safe, logically correct, or appropriate for the project. Review formatted changes like other edits, especially when a formatter creates a large diff.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteRank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
Use Restricted Mode before trusting an unfamiliar repository
Before enabling execution-capable features in an unfamiliar codebase, review the repository and keep it in Restricted Mode. VS Code’s Workspace Trust protections limit features while you decide whether to trust a folder. Microsoft notes that AI agents can change files, run terminal commands, and make web requests. Project content supplied as context to an agent can also contain prompt-injection attempts, so files and instructions in a repository should not automatically be treated as trustworthy.
Workspace Trust is a protective layer, not a guarantee that malicious extensions cannot bypass it. Treat the trust decision as one part of assessing a repository and its tooling, not as a security certification. Microsoft’s guidance is direct: “When in doubt, leave a folder in Restricted Mode. You can always enable trust later.” See Workspace Trust in VS Code.
A cautious review sequence
- Open an unfamiliar folder and leave it in Restricted Mode while you inspect its contents.
- Review project instructions, scripts, dependencies, and configuration that could affect commands or files.
- Check the extensions and AI features you intend to use, including what capabilities they have and which project content they may receive.
- Only enable trust when you have made an informed decision about the folder and its tooling. If you are not comfortable with it, keep Restricted Mode in place.
Trusting a folder is not the same thing as approving every generated change. Continue to review file modifications and any commands an agent proposes or runs according to the controls available in the particular feature you use.
What Restricted Mode does and does not answer
Restricted Mode helps you pause before project-controlled behavior and execution-capable features are enabled. It does not tell you whether the code is well designed, whether its dependencies are safe, or whether an AI suggestion is correct. It also does not replace checking extension permissions and publisher documentation. Use it as a decision point: inspect first, decide whether the folder and tooling are acceptable, then enable trust only when you are comfortable with the consequences.
Free tools Windows power users keep installed
One-click scans. No signup required.
Prompt injection deserves special attention when an agent reads repository files. A README, issue export, generated file, or comment can contain instructions aimed at the agent rather than at you. Treat such text as untrusted project content, and do not allow it to substitute for your own review of commands, file changes, or requests for secrets.
Isolate project setups with profiles
Profiles let you keep different settings and extensions for different kinds of work, and can be associated with a folder or workspace. That is useful if one project needs an AI-enabled extension set and another should use a different set, or if language-specific tooling would otherwise make a single editor setup confusing. A profile can be temporary for an experiment or saved for repeated work. Profiles organize editor configuration; they do not make an untrusted repository safe or validate an extension. See Microsoft’s Profiles documentation.
| Approach | Best fit | What to keep in mind |
|---|---|---|
| One common profile | Projects that use similar extensions and personal preferences. | Project-specific conventions still belong at the appropriate workspace scope. |
| Separate saved profiles | Repeatedly switching between projects or language setups with different settings and extensions. | Associate the profile with the intended folder or workspace and confirm it is active when behavior differs. |
| Temporary profile | Trying an extension set or setup without folding it into regular work. | Do not mistake isolation of settings for a security boundary around code execution. |
Use profiles as a troubleshooting checkpoint
If AI behavior, formatting, or commands differ between two projects, first confirm which profile is active. A profile can change the installed extension set and settings at the same time, so comparing only workspace files may miss the cause. Record which profile belongs with each workspace, and avoid assuming that a setting present in one profile exists in another.
Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
Profiles are also a practical way to trial an AI extension. A temporary profile can keep experimental extensions and settings out of your normal setup. Before using that profile on a real repository, still apply Workspace Trust and review the extension’s capabilities. Isolation reduces configuration spillover; it is not a security promise.
Control AI features at the right level
There is no universal AI switch that governs every feature in VS Code and every installed extension. VS Code documents chat.disableAIFeatures for its built-in AI features. That control should not be assumed to disable separate AI extensions or their capabilities. Extensions may add their own settings and scopes, so consult the current settings and publisher documentation for the exact extension you use. Microsoft’s settings reference describes the general settings model, and its Copilot setup guide documents Copilot-specific setup.
Copilot account preferences can be scoped to a workspace and profile. That is a Copilot-specific capability, not a template for how all AI extensions work. If your goal is to limit file changes, command execution, or other agent actions, inspect the controls for that particular feature; do not assume that disabling a general chat setting or changing a Copilot preference controls every agent in the editor.
Match the control to the risk
| Goal | Where to look | What not to assume |
|---|---|---|
| Disable built-in VS Code AI features | VS Code’s chat.disableAIFeatures setting. |
That it disables third-party extensions. |
| Change Copilot behavior | Copilot’s account preferences, including workspace or profile scope where supported. | That the same preference exists in another AI tool. |
| Limit an agent’s file or terminal actions | The particular agent feature and its extension or publisher documentation. | That a chat toggle automatically blocks every action. |
| Keep AI tooling out of one project | A separate profile and the project’s workspace settings. | That profile separation replaces trust review. |
When you change an AI setting, test the exact feature you intend to control. Confirm whether the setting is user-wide, workspace-specific, profile-specific, or supplied by an extension. This avoids the false confidence that comes from changing a similarly named option at the wrong scope.
Troubleshoot settings that do not behave as expected
- A setting seems ignored: Check whether a workspace value overrides the user value, whether a language-specific override applies, and whether an extension contributes another setting or scope.
- Files save sooner than expected: Check
files.autoSaveand, when it isafterDelay,files.autoSaveDelay. Focus-based modes save on the documented focus changes, not only on an explicit save command. - Formatting does not run: Confirm that
editor.formatOnSaveis enabled at the scope you intend, and that a formatter is available and selected for the file’s language. - Formatting changes are unwelcome: Disable format-on-save for that scope or choose the formatter the project accepts. Review the diff before keeping broad formatting changes.
- Only one language behaves differently: Inspect the language-specific override and the formatter selected for that language; a general editor value may be overridden.
- AI behavior differs between projects: Confirm the active profile, workspace settings, installed extensions, and the relevant extension’s own settings. Built-in AI controls should not be presumed to govern third-party extensions.
- An unfamiliar project asks for trust: Keep it in Restricted Mode until you have reviewed the repository and its tooling; declining to trust it is a valid choice.
- A workspace setting appears risky or unexpected: Review the repository’s settings and scripts before trusting the folder, and remember that checked-in settings do not prove the repository or its extensions are safe.
A practical baseline to adapt
For a project with an agreed formatter and a team that wants delayed saving, a reasonable starting point is to keep personal preferences in user settings, put the formatter convention in workspace settings, and enable format-on-save only for the languages where that formatter is accepted. Choose an Auto Save mode separately based on how edits should be saved and reviewed. Use a profile when projects need different extension sets, and keep unfamiliar repositories in Restricted Mode during review.
- Open the project without trusting it if the repository is unfamiliar.
- Confirm the active profile and note which AI and formatter extensions are installed.
- Inspect the effective values for Auto Save, format-on-save, language-specific formatter settings, and AI controls.
- Choose the save mode that matches the team’s review process.
- Enable format-on-save only after formatting a small sample and checking the diff.
- Review the extension’s own documentation for controls over chat, file edits, commands, and account or workspace scope.
- Trust the folder only after reviewing its instructions, scripts, dependencies, and tooling.
These choices create clearer boundaries between personal preferences, project conventions, automation, and trust. They cannot guarantee that an AI agent will produce correct code; code review, testing, and an informed decision about repository trust remain necessary.
Frequently Asked Questions
What VS Code settings should I use for AI coding?
Start by separating scope: keep personal editor preferences in user settings and project conventions, such as the accepted formatter, in workspace settings. Choose Auto Save independently from format-on-save, use a profile when projects need different extension sets, and review unfamiliar repositories in Restricted Mode. Check the settings supplied by the exact AI extension you use; there is no universal control for every AI feature.
How do I stop Copilot or another AI tool from changing files automatically?
Do not assume a general VS Code chat setting controls every extension. Inspect the feature’s current settings and publisher documentation for controls over file edits, terminal commands, and agent actions. Copilot account preferences can be scoped to a workspace and profile, while other extensions may use different settings. Continue reviewing proposed and completed changes.
Should I turn on format-on-save in VS Code?
Turn on editor.formatOnSave only when a formatter is configured for the file’s language and the project accepts its output. Format a small representative change and inspect the diff first. If no formatter is available, the formatter is disputed, or automatic rewrites create noisy diffs, leave it off or configure it only for the appropriate language and workspace.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
What is the difference between Auto Save and format-on-save?
Auto Save controls when VS Code writes edits to disk. Format-on-save controls whether formatting runs during a save. They are independent, so you can use explicit saves with formatting, automatic saves without formatting, both, or neither. The documented afterDelay default is 1000 ms, but it is a product default rather than a reliability guarantee.
How do I configure VS Code for a specific project?
Put shared project conventions in workspace settings and keep personal preferences in user settings. Check language-specific overrides and the effective value when behavior differs. Confirm the active profile and installed extensions, because a workspace setting cannot provide a formatter or AI capability that is not available in the current setup.
Is it safe to use AI agents in an unfamiliar repository?
Leave the folder in Restricted Mode while you review its files, instructions, scripts, dependencies, extensions, and configuration. Microsoft advises leaving a folder in Restricted Mode when in doubt. Workspace Trust is a protective layer, not a guarantee against malicious extensions, so review agent capabilities and every proposed command or file change before enabling trust.
Can I use one profile for all my projects?
Yes, if projects use similar settings and extensions. Separate saved profiles are useful when language tooling or AI extensions differ, and a temporary profile is useful for experiments. Confirm the active profile whenever behavior changes. Profiles organize configuration but do not make an untrusted repository safe.
Why is VS Code ignoring my setting?
Check the setting’s scope and effective value. A workspace value can override a user value; a language-specific override can change one file type; and an extension can contribute additional settings or scopes. Also confirm the active profile and whether the expected formatter or AI extension is installed and enabled.
The Bottom Line
Reliable AI-assisted coding starts with clear boundaries, not a magic settings file: scope conventions to the workspace, choose saving and formatting deliberately, isolate tooling with profiles, and keep unfamiliar repositories in Restricted Mode until reviewed. Then verify the controls for the exact AI extension and continue to review, test, and approve every generated change.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
