[
    {
        "role": "user",
        "content": "is%20cursor%20based%20on%20vs%20code%3F"
    },
    {
        "role": "assistant",
        "content": "Hey! Just to double check: by \u201cis%20cursor%20based%20on%20vs%20code%3F\u201d I think you meant \u201cIs Cursor based on VS Code?\u201d \u2014 referring to the Cursor AI editor/IDE vs. Microsoft\u2019s Visual Studio Code. Here\u2019s the latest on that, plus what it means in practical terms:\n\n---\n\n## What is Cursor\n\n- Cursor is an AI-powered integrated development environment (IDE) developed by Anysphere. ([en.wikipedia.org](https://en.wikipedia.org/wiki/Cursor_%28code_editor%29?utm_source=openai))  \n- It was released in 2023 and is proprietary software. ([en.wikipedia.org](https://en.wikipedia.org/wiki/Cursor_%28code_editor%29?utm_source=openai))  \n\n---\n\n## Is Cursor based on VS Code?\n\nYes \u2014 Cursor is **based on (or forked from) Code OSS**, which is the open-source core of Visual Studio Code. ([lowcode.agency](https://www.lowcode.agency/blog/is-cursor-ai-vs-code-fork?utm_source=openai))\n\n- \u201cForked\u201d means they took the open-source VS Code foundation and built upon it, adding their own features \u2014 especially AI-focused ones \u2014 rather than writing a completely new editor from scratch. ([lowcode.agency](https://www.lowcode.agency/blog/is-cursor-ai-vs-code-fork?utm_source=openai))  \n- Being based on VS Code gives Cursor a lot of existing strengths from the VS Code ecosystem: familiar keyboard shortcuts, extension/theme support, settings, debugging tools, etc. ([xda-developers.com](https://www.xda-developers.com/replaced-vs-code-cursor-v2-absolutely-phenomenal/?utm_source=openai))  \n\n---\n\n## What are the differences compared to VS Code\n\nWhile Cursor inherits many features from VS Code, it also diverges in some key ways because of its AI-first design. Here are the main differences:\n\n| Area | VS Code (with extensions) | Cursor (fork) |\n|---|---|---|\n| AI integration | Optional, via extensions like GitHub Copilot or Continue. Not always deeply integrated. ([getaiperks.com](https://www.getaiperks.com/kk/articles/cursor-vs-vscode?utm_source=openai)) | Built-in AI features: multi-file edits, deep context awareness, code-base chat, etc. ([lowcode.agency](https://www.lowcode.agency/blog/is-cursor-ai-vs-code-fork?utm_source=openai)) |\n| Customization & Extensions | Very large extension ecosystem, massive variety. ([getaiperks.com](https://www.getaiperks.com/kk/articles/cursor-vs-vscode?utm_source=openai)) | Supports many VS Code extensions/themes; but some compatibility issues exist, especially with niche or UI-deep extensions. ([zoer.ai](https://zoer.ai/posts/zoer/cursor-vs-vscode-ai-features-comparison?utm_source=openai)) |\n| Performance & Updates | Generally lighter without AI overhead. Updates from Microsoft are frequent. ([reddit.com](https://www.reddit.com/r/cursor/comments/1k2b7l2?utm_source=openai)) | AI features add some performance overhead; updates from VS Code are merged, but with some delay. ([docs.cursor.com](https://docs.cursor.com/en/guides/migration/vscode?utm_source=openai)) |\n| Pricing / Licensing | VS Code itself is free and open source; AI features (e.g. Copilot) usually cost separately. ([authorityaitools.com](https://authorityaitools.com/blog/cursor-vs-vscode?utm_source=openai)) | Cursor has a free/hobby tier with limits; full access costs around $20/month. ([authorityaitools.com](https://authorityaitools.com/blog/cursor-vs-vscode?utm_source=openai)) |\n\n---\n\n## What \u201cbeing based on\u201d truly means for you\n\nIf you use VS Code or are considering using Cursor, here\u2019s what this relationship boils down to:\n\n- If you're used to VS Code, you\u2019ll find Cursor familiar in many ways (editor behaviors, settings, themes, etc.). Switching is less traumatic than with a completely new editor. ([xda-developers.com](https://www.xda-developers.com/replaced-vs-code-cursor-v2-absolutely-phenomenal/?utm_source=openai))  \n- Some VS Code extensions may not work perfectly, especially those that rely on very specific or newer parts of the VS Code architecture. ([reddit.com](https://www.reddit.com/r/cursor/comments/1k2b7l2?utm_source=openai))  \n- Cursor tends to blur the line between editor and AI assistant; its new UI/features are more integrated than what extensions alone can offer. If you want AI to be deeply part of your workflow, Cursor accelerates that. ([lowcode.agency](https://www.lowcode.agency/blog/is-cursor-ai-vs-code-fork?utm_source=openai))  \n- On the flip side, if you want absolute control, maximum stability, or use niche tools/plugins, sticking with VS Code + known extensions may feel safer. ([getaiperks.com](https://www.getaiperks.com/kk/articles/cursor-vs-vscode?utm_source=openai))  \n\n---\n\nIf you want, I can also compare how Cursor vs. VS Code + Copilot fares for specific use cases (web dev, data science, enterprise, etc.) so you can see which might be a better fit. Do you want me to pull that together?"
    },
    {
        "role": "user",
        "content": "vs%20code%20is%20pretty%20good%20for%20accessibility%20with%20a%20screen%20reader.%20how%20is%20cursor%20in%20this%20regard%3F"
    },
    {
        "role": "assistant",
        "content": "Here\u2019s what I found on how Cursor\u2019s screen reader and accessibility support compares to VS Code\u2019s. If you rely on screen readers, these are what I uncovered.\n\n---\n\n## VS Code: Strong Accessibility Foundations\n\nVS Code has well-documented, mature features aimed at screen reader users:\n\n- It detects screen readers automatically (or you can force-enable \u201cscreen reader optimized\u201d mode), and adjusts UI accordingly \u2014 for example disabling features like the minimap which are hard to use via screen readers. ([code.visualstudio.com](https://code.visualstudio.com/docs/configure/accessibility/accessibility?utm_source=openai))\n- There are settings such as `editor.accessibilitySupport` that let you control this behavior explicitly (set it to `on`, `off`, or `auto`). ([code.visualstudio.com](https://code.visualstudio.com/docs/configure/accessibility/accessibility?utm_source=openai))\n- VS Code also has accessibility help menus, focuses heavily on keyboard navigation, and supports multiple screen readers (like NVDA, Narrator, JAWS, Orca) across platforms. ([code.visualstudio.com](https://code.visualstudio.com/docs/configure/accessibility/accessibility?utm_source=openai))\n\nIn short, for users who depend on being able to hear everything, navigate via keyboard, get auditory feedback from screen reader-friendly UI elements \u2014 VS Code is fairly solid.\n\n---\n\n## Cursor: Accessibility Today is Limited\n\nIn contrast, Cursor\u2019s support for screen readers and overall accessibility is **incomplete** and currently raises several known issues:\n\n- On Cursor\u2019s community forum, a user reported that the \u201cCtrl + L UI\u201d (which allows you to ask questions about code sections) is *not accessible with a screen reader*. It doesn\u2019t always announce when the answer is in progress, and the response, when it appears, isn\u2019t always reachable or readable via keyboard navigation. ([forum.cursor.com](https://forum.cursor.com/t/the-ctrl-l-ui-is-not-accessible-with-a-screen-reader/47977?utm_source=openai))\n- The \u201cGenerate\u201d feature (activated with `Ctrl + K` in Cursor) also has accessibility gaps: NVDA (a common screen reader) doesn\u2019t properly read the edit field, and users can\u2019t always tab into the buttons or menus (e.g. to change which model to use). ([forum.cursor.com](https://forum.cursor.com/t/needs-screen-reader-accessibility-for-generate-feature/26110?utm_source=openai))\n- Cursor\u2019s developers have acknowledged that screen reader support is something \u201cthey have not been able to add and test yet.\u201d There are no clear timelines for when accessibility enhancements will land. ([forum.cursor.com](https://forum.cursor.com/t/the-ctrl-l-ui-is-not-accessible-with-a-screen-reader/47977?utm_source=openai))\n\n---\n\n## Bottom Line: Where Cursor Falls Short\n\nHere are some specific areas where Cursor currently lags behind VS Code in terms of screen reader accessibility:\n\n| Feature Area | What Cursor Does | What VS Code Does Better / Missing in Cursor |\n|--------------|------------------|-----------------------------------------------|\n| Screen Reader Announcements & Feedback | Often missing (e.g. actions in progress aren't announced; responses aren\u2019t always navigable) ([forum.cursor.com](https://forum.cursor.com/t/the-ctrl-l-ui-is-not-accessible-with-a-screen-reader/47977?utm_source=openai)) | VS Code gives auditory signals, explicit notifications, and status indicators ([code.visualstudio.com](https://code.visualstudio.com/docs/configure/accessibility/accessibility?utm_source=openai)) |\n| Keyboard Navigation | Key dialogs / UI flows like `Ctrl + K` / `Ctrl + L` don\u2019t always work reliably with screen readers / tab navigation ([forum.cursor.com](https://forum.cursor.com/t/the-ctrl-l-ui-is-not-accessible-with-a-screen-reader/47977?utm_source=openai)) | Better consistent support for navigating dialogs, sidebar items, buttons through keyboard |\n| Readability of Dynamic AI Components | Replies or content generated by AI may not be \u201creachably\u201d read or focused on by assistive tech in Cursor ([forum.cursor.com](https://forum.cursor.com/t/the-ctrl-l-ui-is-not-accessible-with-a-screen-reader/47977?utm_source=openai)) | VS Code tends to treat these dynamic parts more accessibly via its UI framework; though sometimes individual extensions may vary |\n| Testing & Official Support | Cursor admits limited testing and support so far ([forum.cursor.com](https://forum.cursor.com/t/the-ctrl-l-ui-is-not-accessible-with-a-screen-reader/47977?utm_source=openai)) | Microsoft publicly documents accessibility for VS Code, including for screen readers; more mature in that regard |\n\n---\n\n## If You\u2019re Considering Which to Use\n\nDepending on how important screen reader usability is to your workflow, here are some thoughts:\n\n- If your priority is **full accessibility**, reliable keyboard navigation, and consistent screen reader compatibility, VS Code remains the safer choice right now.\n- If you want Cursor for its AI capabilities, you may be able to use it, but expect occasional friction \u2014 some features might not work fully with screen readers, and you might need to combine with VS Code (or similar) to fill in gaps.\n- Checking whether the specific features you use work with your preferred screen reader (NA, NVDA, JAWS, etc.) can help \u2014 Cursor is still under development in this area.\n\n---\n\nIf you want, I can try to find any more recent updates (in 2026) specifically from Cursor\u2019s devs or roadmap that address screen reader accessibility improvements. Would that be helpful?"
    }
]