Merge pull request #2855 from appwrite/feat/cursor-3-blog-post

Feat/cursor 3 blog post

Author: eldadfux

.optimize-cache.json

@@ -403,6 +403,9 @@
   "images/blog/cors-error/cors_error.png": "233a13bcbf4d2d6aac23a0ebf92c71c4442b3bea2848d9f927ea6ac38171ccce",
   "images/blog/cors-error/cors_example.png": "2c033efbf55a6269bd5f70abdf4b72fb355276e96bc08b03f09aaa18604779ac",
   "images/blog/csr-ssg-ssr.png": "cd07b21c221d97a59a9384aa86644886c27670f6d339d4f1696d331d93bf1e88",
+  "images/blog/cursor-3-parallel-fleets-appwrite/cover.png": "33061608299b5fb82dce8db7215ba78dec2a4ec78153c7cec4c8d8da19d833a9",
+  "images/blog/cursor-3-parallel-fleets-appwrite/cursor-agent-appwrite-workspace.png": "0d728a6011d81e166ccca1ecad4ba5abf3aa0835226146532b840b03a81d33fd",
+  "images/blog/cursor-3-parallel-fleets-appwrite/cursor-slash-skills-modes.png": "04dfc42db054cdfc5eb4b44f8026d9aafc343e18e44977442857af67dbb06cf0",
   "images/blog/custom-backup-policy/cover.png": "2fa12083bced8c44c2c1af68167ffacc8cf4332a46fb193355a8b4d5170b59d6",
   "images/blog/custom-domains-with-sites/cover.png": "ecd4c9621a67621b3a785ddcb04ef15cc5d3858ce2d9062867fa8dae2b29594d",
   "images/blog/custom-domains-with-sites/dns-records.png": "8acc1fb22263b50fd226c1ec2fb74957536545a20b6981d65037fe9f52aeaad6",

src/routes/blog/post/cursor-3-parallel-fleets-appwrite/+page.markdoc

@@ -0,0 +1,55 @@
+---
+layout: post
+title: "Cursor 3: parallel agents, cloud agents, skills, and MCP"
+description: An overview of Cursor 3 - agent-first layout, cloud agents, the skills marketplace and MCP, and the integrated browser - with notes on using it alongside Appwrite.
+date: 2026-04-03
+cover: /images/blog/cursor-3-parallel-fleets-appwrite/cover.png
+timeToRead: 7
+author: eldad-fux
+category: integrations
+featured: false
+---
+
+If you have been following the AI code editor space, you know that the "autocomplete" era is officially behind us. This week, the team at Cursor dropped **Cursor 3**, and it is not just a minor version bump - it is a complete reimagining of the IDE. For Appwrite developers, who are already used to "building like a team of hundreds" by offloading backend complexity, Cursor 3 is the perfect companion. It moves the needle from "AI that helps you write code" to "AI that helps you manage a fleet of developers." Here is everything you need to know about Cursor 3 and how it integrates with your Appwrite workflow.
+
+## 1. The "agent-first" interface
+
+Cursor 3 has moved away from the classic VS Code layout. It is now a **unified workspace** designed around **Agents**. Instead of opening a single chat window, you now have an **Agents Window** (`Cmd+Shift+P` - `Agents Window`). This allows you to run multiple agents in parallel across different repositories.
+
+![Cursor agent answering a question about the Appwrite codebase, with agent threads and Appwrite repositories in the sidebar.](/images/blog/cursor-3-parallel-fleets-appwrite/cursor-agent-appwrite-workspace.png)
+
+> **Appwrite impact:** Imagine having one agent refactoring your Appwrite Functions in your `/backend` repo while another agent builds out the new Auth UI in your `/frontend` repo - simultaneously. You are not waiting for the AI to finish one task to start the next; you are orchestrating a team.
+
+## 2. Long-running cloud agents
+
+One of the most significant additions is the ability to hand off tasks to **Cloud Agents**. By prepending a message with `&`, you can push a local conversation to a cloud-based VM.
+
+- **Autonomy:** These agents plan, execute, and test over longer horizons without human intervention.
+- **Artifacts:** When the agent finishes, it does not just give you a diff; it provides logs, video recordings of its work, and even live previews.
+
+**Why this matters for you:** Setting up complex Appwrite Database schemas or writing intricate migration scripts can be time-consuming. You can now hand off a prompt like `& Migrate our current SQL users to Appwrite Auth and set up the corresponding Collections` and walk away. The agent will handle the heavy lifting in the cloud and notify you when it is ready for review.
+
+## 3. Native Appwrite skills & MCP
+
+Appwrite recently introduced **Appwrite Skills** - open-source Markdown files that give AI agents deep, language-specific knowledge of Appwrite SDKs. Cursor 3 introduces a **Marketplace** for these types of skills and **Model Context Protocol (MCP)** servers.
+
+![Cursor chat slash menu listing Appwrite skills, commands, and Ask, Debug, and Plan modes.](/images/blog/cursor-3-parallel-fleets-appwrite/cursor-slash-skills-modes.png)
+
+- **Context precision:** Agents in Cursor 3 now discover and load these skills only when needed, reducing token waste and preventing the "hallucination" of old SDK methods.
+- **CLI integration:** You can manage these directly from the new Cursor CLI using `/mcp enable` or `/rules`.
+
+## 4. The integrated browser & style editor
+
+Cursor 3 includes a built-in browser and component tree. You can move elements, update colors, and test layouts in real-time. The agent then instantly applies those CSS or React changes to your codebase. For those using **Appwrite Realtime**, this makes debugging live state changes incredibly visual. You can watch your UI update as the agent tweaks the subscription listeners in the background.
+
+## How to get started
+
+To try the new experience, ensure you have updated to the latest version and use the following shortcuts:
+
+- **Open agents window:** `Cmd+Shift+P` - `Agents Window`
+- **Switch to plan mode:** `/plan` (great for mapping out Appwrite Function logic)
+- **Invoke Appwrite skill:** Use the slash command menu in chat.
+
+Cursor 3 feels less like a traditional code editor and more like a system for building software faster. For Appwrite developers, it cuts down time spent on boilerplate, SDK wiring, and repetitive setup, so you can stay focused on product logic, user experience, and shipping. Combined with Appwrite, it gives small teams and solo builders a much more practical way to build ambitious products without the usual overhead.
+
+**Have you tried the new parallel fleets yet? Join the conversation in our [Discord](https://appwrite.io/discord) and show us what you are building**