Does Apple Intelligence Work in VS Code on Mac?

No - Apple Intelligence Writing Tools do not work in VS Code on Mac. VS Code is built on Electron, which renders its text editor through Chromium's own engine, completely bypassing the macOS text services layer that Apple Intelligence depends on. For developers who write prose in VS Code - comments, docstrings, commit messages, and READMEs - Charm is the practical solution. It uses the Accessibility API and CGEventTap at the OS kernel level and corrects prose in VS Code without touching code identifiers.

Why can't Apple Intelligence reach VS Code?

Apple Intelligence Writing Tools communicate with applications through the macOS text services system, specifically the NSTextInputClient protocol. This protocol is the standard channel through which macOS delivers autocorrect, spell checking, text substitution, and now Apple Intelligence suggestions to app text fields.

VS Code is not a native Mac app. Despite running on macOS, VS Code is built on Electron - a framework that bundles the app inside a Chromium browser. The editor you type code into is a web view rendered by Chromium's layout engine, not an AppKit text field. macOS text services, and therefore Apple Intelligence, cannot reach inside Chromium's rendering pipeline.

VS Code has over 11 million monthly active users, making it the most widely used code editor in the world. The fact that Apple Intelligence cannot assist any of them in their primary tool is a significant coverage gap - one that exists purely due to Electron's architecture, not any limitation of the developers or their hardware.

Note that this limitation applies regardless of whether you are on Apple Silicon or Intel. Even if you have a brand-new MacBook Pro M4 running macOS 15 Sequoia with Apple Intelligence fully enabled, none of those features reach VS Code's text fields.

What correction options do developers have in VS Code on Mac?

Developers writing in VS Code actually write a lot of prose. Studies suggest that developers spend 30-40% of their VS Code time writing natural language - inline comments explaining logic, docstrings documenting functions, commit messages, PR descriptions, and README files. Errors in this prose reach colleagues, code review tools, and public repositories.

There are two complementary tools worth knowing about.

For code identifiers: The Code Spell Checker extension (available in the VS Code marketplace) is built specifically for code. It understands camelCase, snake_case, and PascalCase naming conventions and flags misspelled variable and function names. It is the right tool for catching getUserInformation misspelled as getUserInfromation.

For prose in VS Code: Charm handles everything at the OS level. Because Charm uses CGEventTap at the kernel level - below VS Code and Electron entirely - it corrects spelling and grammar in any text field in VS Code, from comment blocks to the integrated terminal. No extension needed. No configuration per project.

Is Charm better than a VS Code spell-check extension for prose?

For prose specifically - comments written in English, documentation, commit messages - Charm is significantly better than a VS Code extension for several reasons.

First, Charm works in real-time as you type, correcting errors before they are saved. VS Code extensions typically highlight errors after you pause, requiring you to manually accept or dismiss suggestions. The cognitive workflow is different: Charm's corrections are invisible, while extension suggestions require active attention.

Second, Charm works across your entire Mac. When you switch from VS Code to Slack to write a message about the same PR, Charm continues correcting seamlessly. A VS Code extension stops at VS Code's edge.

Third, Charm includes grammar correction via the Polish feature, which catches agreement errors, tense inconsistencies, and punctuation mistakes that a simple spell checker misses. For developers writing documentation that other engineers and non-technical stakeholders will read, grammar quality matters.

How does Charm handle code vs prose in VS Code?

This is a common and reasonable concern: developers do not want an autocorrect tool mangling variable names or function identifiers. Charm's Spells and Polish features are tuned for natural language. They correct words that appear in natural language dictionaries and apply grammar rules to prose-like sequences of words.

Code identifiers - myVariableName, getUserById, render_template - do not match natural language patterns and are left untouched. Charm recognises that a line like function calculateTotalRevenue() is code syntax, not a sentence, and does not apply prose correction rules to it.

The practical experience for developers is: write code as normal, Charm does nothing. Write a comment or docstring in English, Charm corrects spelling and grammar silently. The boundary is natural - prose gets corrected, code identifiers do not.

Frequently asked questions

Does Apple Intelligence work in VS Code?

No. VS Code is built on Electron and renders text through Chromium's engine, bypassing the macOS text services layer entirely. Apple Intelligence relies on NSTextInputClient, which only reaches native AppKit and SwiftUI text fields. This limitation applies on both Intel and Apple Silicon Macs.

Can I get spell check in VS Code comments?

Yes. Charm provides real-time spelling and grammar correction in VS Code comments, docstrings, commit messages, and any other prose you write inside VS Code. For code identifiers specifically, the Code Spell Checker VS Code extension is a good complement - it understands camelCase and snake_case conventions.

Does Grammarly work in VS Code?

No. Grammarly on Mac is a browser extension only. It works inside Chrome, Safari, and Firefox - not in any desktop application including VS Code. Grammarly cannot reach Electron apps like VS Code regardless of subscription tier.

Will Charm correct my code or just prose?

Charm corrects natural language prose - comments, docstrings, commit messages, READMEs, and PR descriptions written in English. It does not correct code identifiers, variable names, or programming syntax. For misspelled code identifiers, use the Code Spell Checker VS Code extension alongside Charm.

How do I get autocorrect in the VS Code terminal?

Charm works in the VS Code integrated terminal as well as the editor. When typing shell commands or notes in the terminal, Charm's Spells feature corrects prose in real-time. For command-line spell checking of code comment files, consider tools like aspell or codespell in your CI pipeline.