At its annual Build conference, Microsoft dropped a surprise for developers: a brand-new command-line text editor called Edit on Windows. By simply typing “edit” into a command prompt, developers can now tweak files without leaving their terminal workflow. It’s a small but significant addition to Microsoft’s ongoing efforts to make Windows a more developer-friendly platform.

Edit on Windows is a lean, mean text-editing machine. Clocking in at under 250KB, it’s designed to be fast and unobtrusive, letting developers edit files directly in the command line without the overhead of launching a separate application. Think of it as Microsoft’s answer to tools like Vim or Nano, but with a distinctly Windows-friendly flavor.

The editor is open-source, hosted on Microsoft’s GitHub repository, which means developers can poke around the code, contribute improvements, or even fork it for their own projects. This transparency aligns with Microsoft’s broader push to embrace open-source development, a trend that’s been evident in projects like Visual Studio Code and the Windows Terminal.

Edit on Windows comes with a handful of features that make it practical for everyday use:

• Key bindings for all menu options, ensuring quick navigation.
• Multi-file support, with the ability to switch between open files using the Ctrl + P shortcut.
• Find and replace functionality, complete with support for case-sensitive searches and regular expressions.
• Word wrapping, because nobody likes horizontal scrolling in a terminal.

These features might sound basic, but they’re carefully chosen to make Edit a functional, no-frills tool for developers who live in the command line.

The motivation behind Edit on Windows stems from a gap in the Windows ecosystem. As Christopher Nguyen, product manager for Windows Terminal, explained, “32-bit versions of Windows ship with the MS-DOS Editor, but 64-bit versions do not have a CLI editor installed inbox.” For years, this left developers on 64-bit systems without a default command-line editor, forcing them to rely on third-party tools or heavyweight IDEs.

Then there’s the infamous “how do I exit Vim?” meme—a running joke in developer circles about the steep learning curve of Vim’s modal interface, where users must switch between distinct modes (like insert or command mode) to edit or navigate. Microsoft wanted to sidestep this entirely. “We decided that we wanted a modeless editor for Windows,” Nguyen said, emphasizing a design that avoids the complexity of modes. The result is an editor that’s intuitive for newcomers while still powerful enough for seasoned developers.

This focus on usability reflects Microsoft’s broader goal: to make Windows a more welcoming environment for developers, whether they’re building apps, scripting automation, or tweaking configuration files.

Edit on Windows isn’t a standalone project—it’s part of a suite of improvements Microsoft is rolling out to enhance the developer experience on Windows. At Build, the company also announced the rebranding of Windows Dev Home to Advanced Windows Settings. This isn’t just a name change; it’s a shift in approach. Instead of being a separate app, Advanced Windows Settings integrates directly into the Windows 11 settings interface, offering developers a centralized hub to tweak their system.

According to Pavan Davuluri, Windows chief, these settings “allow developers to easily control and personalize their Windows experience.” One standout feature is the integration of GitHub controls into File Explorer, making it easier to manage version-controlled projects without leaving the familiar Windows interface. These toggles are designed to streamline workflows, giving developers more control over their environment without needing to dig through obscure configuration menus.

Microsoft’s focus on developers isn’t new. Over the past decade, the company has transformed Windows from a consumer-focused OS to a platform that caters to coders. Tools like Windows Subsystem for Linux (WSL), Windows Terminal, and Visual Studio Code have made Windows a serious contender for developers who once gravitated toward Linux or macOS. Edit on Windows and Advanced Windows Settings are the latest steps in this journey, addressing pain points for developers who rely on the command line or need fine-grained system control.

Edit on Windows is still in its early days. Microsoft plans to roll it out to the Windows Insider program in the coming months, giving developers a chance to test and provide feedback before it hits general availability. The open-source nature of the project means the community will likely play a big role in shaping its future, whether through bug fixes, feature requests, or integrations with other tools.

For now, developers can check out the project on its GitHub repository, where Microsoft has shared more details about its architecture and roadmap. The lightweight design and focus on simplicity suggest Edit could become a go-to tool for quick edits, especially for those who don’t want to wrestle with more complex editors like Vim or Emacs.

At first glance, a command-line text editor might seem like a niche addition to Windows. But for developers, it’s a meaningful step toward making the OS a one-stop shop for their workflows. The command line is still a vital part of software development, whether you’re scripting, debugging, or managing servers. By providing a built-in, lightweight editor, Microsoft is removing friction for developers who want to stay in the terminal.

Moreover, Edit on Windows reflects Microsoft’s broader strategy of listening to its developer community. The company has been steadily chipping away at the barriers that once made Windows feel less developer-friendly than its competitors. From embracing Linux to open-sourcing core tools, Microsoft is doubling down on its commitment to coders.

For developers, Edit on Windows is a small but welcome addition to the toolbox. It’s not trying to replace full-fledged IDEs or battle-tested editors like Vim. Instead, it’s a practical, no-nonsense option for those moments when you just need to tweak a file and move on. And in a world where developer productivity is king, that’s a win worth celebrating.