--- title: Visual Studio Code 1.133 (Insiders) | daily.dev description: VS Code 1.133 Insiders release adds support for custom editor extensions to set separate priorities for standard text editors and diff editors. This allows... canonical: https://daily.dev/posts/visual-studio-code-1-133-insiders--9xyscgwgj twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Visual Studio Code 1.133 (Insiders) | daily.dev og:description: VS Code 1.133 Insiders release adds support for custom editor extensions to set separate priorities for standard text editors and diff editors. This allows... og:url: https://daily.dev/posts/visual-studio-code-1-133-insiders--9xyscgwgj og:image: https://api.daily.dev/og/posts/9xYScgWgj.png og:image:alt: Visual Studio Code 1.133 (Insiders) og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Visual Studio Code 1.133 (Insiders) **[Visual Studio Code](https://daily.dev/sources/vscode)** · 1 min read · 44 upvotes · 5 comments ## Summary VS Code 1.133 Insiders release adds support for custom editor extensions to set separate priorities for standard text editors and diff editors. This allows custom editors to remain the default while using the built-in text editor for diff views by default. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How do I make my VS Code custom editor extension use the default text editor for diffs but stay the default for regular viewing? Set separate priorities for the standard text editor and diff/merge editors in the custom editor contribution. This change, tracked as issue #292379, lets an extension remain the default editor for normal editing while the plain text editor is used by default when showing diffs or merges, avoiding forcing the custom editor into diff view. _Extension developers tracking VS Code Insiders editor API changes can follow updates like this on daily.dev._ ## Community discussion Top comments from developers on daily.dev. **@agustinbarrientos** · 1 upvotes > I prefer my custom editor for normal files and the plain text diff every time. **@springtofigh** · 1 upvotes >  **@allinonetools** · 1 upvotes > This is a really useful improvement. Keeping custom editors for normal work while defaulting to the built-in editor for diffs feels much cleaner. **@doncho** · 1 upvotes > I'm a bit worried that VS Code seems to incline more and more towards their own GitHub model. This might turn out bad. Let's see... ## Similar posts on daily.dev - [Visual Studio Code 1.120](https://daily.dev/posts/visual-studio-code-1-120-ngenkcuse) · Visual Studio Code · 90 upvotes · 1 comments - [VS Code now updates weekly](https://daily.dev/posts/vs-code-now-updates-weekly-faito46mt) · InfoWorld · 0 upvotes · 0 comments - [Visual Studio Code 1.113 <\!-- %IF INSIDERS % \(Insiders\) %ENDIF % -->](https://daily.dev/posts/visual-studio-code-1-113----if-insiders-insiders-endif-----uqg2gzvfg) · Visual Studio Code · 0 upvotes · 0 comments - [Visual Studio Code previews chat customizations editor](https://daily.dev/posts/visual-studio-code-previews-chat-customizations-editor-apzuovvgu) · InfoWorld · 0 upvotes · 0 comments - [Visual Studio January Update](https://daily.dev/posts/visual-studio-january-update-i6ak5emou) · Visual Studio Blog · 13 upvotes · 0 comments --- Tags: [#vscode](https://daily.dev/tags/vscode) [View this post on daily.dev](https://daily.dev/posts/visual-studio-code-1-133-insiders--9xyscgwgj) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Visual Studio Code 1.133 (Insiders)","url":"https://daily.dev/posts/visual-studio-code-1-133-insiders--9xyscgwgj","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/visual-studio-code-1-133-insiders--9xyscgwgj"},"datePublished":"2026-08-05T09:14:46.988Z","dateModified":"2026-09-14T06:41:34.026Z","description":"VS Code 1.133 Insiders release adds support for custom editor extensions to set separate priorities for standard text editors and diff editors. This allows...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/81678ab9e6e6411928e06acaf39051c6?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/81678ab9e6e6411928e06acaf39051c6?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Visual Studio Code","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Visual Studio Code","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/d5adab6ae9fb44d19859748fc30f5e18","url":"https://daily.dev/sources/vscode"},"commentCount":5,"discussionUrl":"https://daily.dev/posts/visual-studio-code-1-133-insiders--9xyscgwgj","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":44},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":5}],"keywords":"vscode","timeRequired":"PT1M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Visual Studio Code","item":"https://daily.dev/sources/vscode"},{"@type":"ListItem","position":3,"name":"Visual Studio Code 1.133 (Insiders)"}]} {"@context":"https://schema.org","@type":"WebPage","@id":"https://daily.dev/posts/visual-studio-code-1-133-insiders--9xyscgwgj","comment":[{"@type":"Comment","text":"I prefer my custom editor for normal files and the plain text diff every time.","datePublished":"2026-08-08T17:24:01.552Z","url":"https://daily.dev/posts/9xYScgWgj#c-VX4kzZS2m","author":{"@type":"Person","name":"Agustin Barrientos","url":"https://daily.dev/agustinbarrientos","image":"https://media.daily.dev/image/upload/s--5ayxQnqn--/f_auto/v1788281802/avatars/avatar_wQYYVe5Tbj0NJ7C7qPoa8?_a=BAMAMicg0"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1}},{"@type":"Comment","text":"","datePublished":"2026-08-09T18:07:32.612Z","url":"https://daily.dev/posts/9xYScgWgj#c-qmQs4gIyj","author":{"@type":"Person","name":"Spring Tofigh","url":"https://daily.dev/springtofigh","image":"https://avatars.githubusercontent.com/u/90114320?v=4"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1}},{"@type":"Comment","text":"This is a really useful improvement. Keeping custom editors for normal work while defaulting to the built-in editor for diffs feels much cleaner.","datePublished":"2026-08-08T03:02:39.501Z","url":"https://daily.dev/posts/9xYScgWgj#c-17iymrtXW","author":{"@type":"Person","name":"AllInOneTools","url":"https://daily.dev/allinonetools","image":"https://media.daily.dev/image/upload/s--4ZT8QlF0--/f_auto/v1769790028/avatars/avatar_igzBsWloJeaegzm9bQltZ?_a=BAMAMiiu0"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1}},{"@type":"Comment","text":"I’m a bit worried that VS Code seems to incline more and more towards their own GitHub model. This might turn out bad. Let’s see…","datePublished":"2026-08-09T05:25:14.029Z","url":"https://daily.dev/posts/9xYScgWgj#c-76vdZmR8D","author":{"@type":"Person","name":"Doncho Angelov","url":"https://daily.dev/doncho","image":"https://media.daily.dev/image/upload/s--j1MSm0hy--/f_auto/v1716369534/avatars/avatar_EB0j0Umzh5v3zGWUSL5ma"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1}}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/visual-studio-code-1-133-insiders--9xyscgwgj#faq","mainEntity":[{"@type":"Question","name":"How do I make my VS Code custom editor extension use the default text editor for diffs but stay the default for regular viewing?","acceptedAnswer":{"@type":"Answer","text":"Set separate priorities for the standard text editor and diff/merge editors in the custom editor contribution. This change, tracked as issue #292379, lets an extension remain the default editor for normal editing while the plain text editor is used by default when showing diffs or merges, avoiding forcing the custom editor into diff view. Extension developers tracking VS Code Insiders editor API changes can follow updates like this on daily.dev."}}]} ```