<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Editor on Vibe Coding</title><link>https://vibecoding.rest/tags/editor/</link><description>Recent content in Editor on Vibe Coding</description><generator>Hugo</generator><language>en</language><atom:link href="https://vibecoding.rest/tags/editor/index.xml" rel="self" type="application/rss+xml"/><item><title>Cursor</title><link>https://vibecoding.rest/tools/cursor/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/tools/cursor/</guid><description>&lt;p&gt;Cursor takes the familiar VS Code shell and rebuilds the editing experience around AI: inline &amp;ldquo;Cmd+K&amp;rdquo; edits, a chat sidebar with full repo context, and an agent mode that can plan and execute multi-file changes.&lt;/p&gt;</description></item><item><title>GitHub Copilot</title><link>https://vibecoding.rest/tools/github-copilot/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/tools/github-copilot/</guid><description>&lt;p&gt;Copilot started as an autocomplete extension and has grown into a full assistant: inline suggestions, a chat pane, a CLI, and an agent mode that can open pull requests on its own.&lt;/p&gt;</description></item><item><title>Zed</title><link>https://vibecoding.rest/tools/zed/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/tools/zed/</guid><description>&lt;p&gt;Zed is a code editor built from the ground up (not forked from VS Code) for raw editing and rendering speed, with AI collaboration — chat, inline edits, and agentic multi-step changes — designed in as a core feature rather than bolted on through extensions.&lt;/p&gt;</description></item><item><title>Void</title><link>https://vibecoding.rest/tools/void/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/tools/void/</guid><description>&lt;p&gt;Void is an open-source fork of VS Code built as a transparent alternative to Cursor and Copilot: every AI request is visible and configurable, and nothing routes through a proprietary backend unless you choose to.&lt;/p&gt;</description></item><item><title>Supermaven</title><link>https://vibecoding.rest/tools/supermaven/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/tools/supermaven/</guid><description>&lt;p&gt;Supermaven built its name on speed: a purpose-tuned completion model with an unusually large context window, designed to suggest code with minimal lag as you type. In late 2024 it was acquired by Anysphere, the makers of Cursor, and its completion engine now powers Cursor&amp;rsquo;s Tab feature.&lt;/p&gt;</description></item><item><title>Pear AI</title><link>https://vibecoding.rest/tools/pear-ai/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/tools/pear-ai/</guid><description>&lt;p&gt;Pear AI is an open-source code editor built on top of VS Code and the Continue extension, aiming to package the best available AI coding tools into a single, ready-to-use interface rather than making users assemble their own stack of extensions.&lt;/p&gt;</description></item><item><title>Melty</title><link>https://vibecoding.rest/tools/melty/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/tools/melty/</guid><description>&lt;p&gt;Melty is an open-source code editor built around a persistent chat pane rather than inline suggestions: it watches your terminal, compiler output, debugger, and GitHub activity so it can propose changes, fix errors, and draft commit messages with real context on what you&amp;rsquo;re doing.&lt;/p&gt;</description></item><item><title>Aide</title><link>https://vibecoding.rest/tools/aide/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/tools/aide/</guid><description>&lt;p&gt;Aide is an open-source VS Code fork from CodeStory AI that merges chat and editing into one flow — you can brainstorm a problem by referencing files in chat, then jump straight into applying edits across multiple files in the same session.&lt;/p&gt;</description></item></channel></rss>