Skip to content
Back to search

Overture

Overture is an open-source, locally running web interface delivered as an MCP (Model Context Protocol) server that visually maps out the execution plan of any AI coding agent as an interactive flowchart/graph before the agent begins writing code.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/sixhq--overture/badge.svg)](/listings/sixhq--overture)

HTML

<a href="/listings/sixhq--overture"><img src="/api/listings/sixhq--overture/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Overture is an MCP server that works with **any MCP-compatible AI coding agent**. One command to install.

Claude Code

claude mcp add overture-mcp -- npx overture-mcp

Cursor

Add to `~/.cursor/mcp.json`:

{
  "mcpServers": {
    "overture": {
      "command": "npx",
      "args": ["overture-mcp"]
    }
  }
}

<details> <summary><strong>More Agents (Cline, Copilot, Sixth AI)</strong></summary>

Cline (VS Code Extension)

Open VS Code settings → search "Cline MCP" → add:

{
  "mcpServers": {
    "overture": {
      "command": "npx",
      "args": ["overture-mcp"]
    }
  }
}

GitHub Copilot

Create `.vscode/mcp.json` in your project root:

{
  "servers": {
    "overture": {
      "command": "npx",
      "args": ["overture-mcp"]
    }
  }
}

> **Note:** GitHub Copilot MCP requires VS Code 1.99+ and uses `servers` instead of `mcpServers`.

Sixth AI (VS Code Extension)

Add to your Sixth AI MCP settings file:

| Platform | Path | |----------|------| | macOS | `~/Library/Application Support/Code/User/globalStorage/sixth.sixth-ai/settings/sixth-mcp-settings.json` | | Windows | `%APPDATA%\Code\User\globalStorage\sixth.sixth-ai\settings\sixth-mcp-settings.json` | | Linux | `~/.config/Code/User/globalStorage/sixth.sixth-ai/settings/sixth-mcp-settings.json` |

{
  "mcpServers": {
    "overture": {
      "command": "npx",
      "args": ["overture-mcp"],
      "disabled": false
    }
  }
}

</details>

Global Installation (Optional)

npm install -g overture-mcp

Verify It Works

Give your agent any task. Overture automatically opens at `http://localhost:3031` with your plan ready for approval.

---

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 744 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. <p align="center">
  2. <picture>
  3. <source media="(prefers-color-scheme: light)" srcset="https://raw.githubusercontent.com/SixHq/Overture/main/assets/overture-logo-dark.png">
  4. <img src="https://raw.githubusercontent.com/SixHq/Overture/main/assets/overture-logo-light.png" alt="Overture" width="400">
  5. </picture>
  6. </p>
  7. <p align="center">
  8. <strong>See the plan before the code. Approve it. Then watch it execute.</strong>
  9. </p>
  10. <p align="center">
  11. <a href="https://www.npmjs.com/package/overture-mcp"><img src="https://img.shields.io/npm/v/overture-mcp?style=for-the-badge&color=blue" alt="npm version"></a>
  12. <a href="https://github.com/SixHq/Overture/actions"><img src="https://img.shields.io/github/actions/workflow/status/SixHq/Overture/ci.yml?branch=main&style=for-the-badge" alt="CI status"></a>
  13. <a href="https://www.npmjs.com/package/overture-mcp"><img src="https://img.shields.io/npm/dm/overture-mcp?style=for-the-badge&color=orange" alt="npm downloads"></a>
  14. <a href="https://github.com/SixHq/Overture/discussions"><img src="https://img.shields.io/github/discussions/SixHq/Overture?style=for-the-badge&color=purple" alt="Discussions"></a>
  15. <a href="LICENSE"><img src="https://img.shields.io/badge/License-MIT-green.svg?style=for-the-badge" alt="MIT License"></a>
  16. </p>
  17. <p align="center">
  18. <a href="#-the-problem">Problem</a> •
  19. <a href="#-the-solution">Solution</a> •
  20. <a href="#-installation">Install</a> •
  21. <a href="#-features">Features</a> •
  22. <a href="#-mcp-marketplace">Marketplace</a> •
  23. <a href="#-configuration">Config</a> •
  24. <a href="https://github.com/SixHq/Overture/discussions">Discussions</a>
  25. </p>
  26. <br>
  27. <p align="center">
  28. https://github.com/user-attachments/assets/eeb9c4cb-c80d-42da-bf63-c0c4ecb1e5d6
  29. </p>
  30. ---
  31. ## 🔥 The Problem
  32. Every AI coding agent today — **Cursor**, **Claude Code**, **Cline**, **Copilot** — works the same way:
  33. <table>
  34. <tr>
  35. <td width="50%">
  36. ### What Happens Now
  37. 1. You type a prompt
  38. 2. Agent **immediately starts writing code**
  39. 3. You have **zero visibility** into what it's doing
  40. 4. You realize it misunderstood your request
  41. 5. **Hundreds of lines of code** need to be discarded
  42. 6. You've wasted tokens, time, and patience
  43. </td>
  44. <td width="50%">
  45. ### Text Plans Don't Help
  46. Some agents show plans as text in chat. But text fails to show:
  47. - **Dependencies** — which tasks depend on what?
  48. - **Branch points** — what alternative approaches exist?
  49. - **Context requirements** — which files, APIs, or secrets are needed?
  50. - **Complexity** — which steps are risky?
  51. - **Progress** — what's done, what's next?
  52. </td>
  53. </tr>
  54. </table>
  55. <p align="center">
  56. <img src="https://raw.githubusercontent.com/SixHq/Overture/main/assets/problem-illustration.png" alt="The Problem" width="700">
  57. </p>
  58. ---
  59. ## ✨ The Solution
  60. **Overture** intercepts your AI agent's planning phase and renders it as an **interactive visual flowchart** — before any code is written.
  61. <p align="center">
  62. <img src="https://raw.githubusercontent.com/SixHq/Overture/main/assets/solution-screenshot.png" alt="Overture Solution" width="900">
  63. </p>
  64. ### The agent doesn't write a single line of code until you approve the plan.
  65. <br>
  66. <table>
  67. <tr>
  68. <td align="center" width="20%">
  69. <img src="https://img.icons8.com/color/96/flow-chart.png" width="64"><br>
  70. <strong>Visual Plans</strong><br>
  71. <sub>Interactive flowchart with pan, zoom, and click-through navigation</sub>
  72. </td>
  73. <td align="center" width="20%">
  74. <img src="https://img.icons8.com/color/96/attach.png" width="64"><br>
  75. <strong>Attach Context</strong><br>
  76. <sub>Files, API keys, instructions per step</sub>
  77. </td>
  78. <td align="center" width="20%">
  79. <img src="https://img.icons8.com/color/96/split.png" width="64"><br>
  80. <strong>Choose Approaches</strong><br>
  81. <sub>Compare pros/cons of different paths</sub>
  82. </td>
  83. <td align="center" width="20%">
  84. <img src="https://img.icons8.com/color/96/lightning-bolt.png" width="64"><br>
  85. <strong>Real-time Execution</strong><br>
  86. <sub>Watch nodes light up with progress</sub>
  87. </td>
  88. <td align="center" width="20%">
  89. <img src="https://img.icons8.com/color/96/shop.png" width="64"><br>
  90. <strong>MCP Marketplace</strong><br>
  91. <sub>Browse & attach tools per node</sub>
  92. </td>
  93. </tr>
  94. </table>
  95. ---
  96. ## 🚀 Installation
  97. Overture is an MCP server that works with **any MCP-compatible AI coding agent**. One command to install.
  98. ### Claude Code
  99. ```bash
  100. claude mcp add overture-mcp -- npx overture-mcp
  101. ```
  102. ### Cursor
  103. Add to `~/.cursor/mcp.json`:
  104. ```json
  105. {
  106. "mcpServers": {
  107. "overture": {
  108. "command": "npx",
  109. "args": ["overture-mcp"]
  110. }
  111. }
  112. }
  113. ```
  114. <details>
  115. <summary><strong>More Agents (Cline, Copilot, Sixth AI)</strong></summary>
  116. ### Cline (VS Code Extension)
  117. Open VS Code settings → search "Cline MCP" → add:
  118. ```json
  119. {
  120. "mcpServers": {
  121. "overture": {
  122. "command": "npx",
  123. "args": ["overture-mcp"]
  124. }
  125. }
  126. }
  127. ```
  128. ### GitHub Copilot
  129. Create `.vscode/mcp.json` in your project root:
  130. ```json
  131. {
  132. "servers": {
  133. "overture": {
  134. "command": "npx",
  135. "args": ["overture-mcp"]
  136. }
  137. }
  138. }
  139. ```
  140. > **Note:** GitHub Copilot MCP requires VS Code 1.99+ and uses `servers` instead of `mcpServers`.
  141. ### Sixth AI (VS Code Extension)
  142. Add to your Sixth AI MCP settings file:
  143. | Platform | Path |
  144. |----------|------|
  145. | macOS | `~/Library/Application Support/Code/User/globalStorage/sixth.sixth-ai/settings/sixth-mcp-settings.json` |
  146. | Windows | `%APPDATA%\Code\User\globalStorage\sixth.sixth-ai\settings\sixth-mcp-settings.json` |
  147. | Linux | `~/.config/Code/User/globalStorage/sixth.sixth-ai/settings/sixth-mcp-settings.json` |
  148. ```json
  149. {
  150. "mcpServers": {
  151. "overture": {
  152. "command": "npx",
  153. "args": ["overture-mcp"],
  154. "disabled": false
  155. }
  156. }
  157. }
  158. ```
  159. </details>
  160. ### Global Installation (Optional)
  161. ```bash
  162. npm install -g overture-mcp
  163. ```
  164. ### Verify It Works
  165. Give your agent any task. Overture automatically opens at `http://localhost:3031` with your plan ready for approval.
  166. ---
  167. ## 🎯 How It Works
  168. <p align="center">
  169. <img src="https://raw.githubusercontent.com/SixHq/Overture/main/assets/how-it-works.png" alt="How Overture Works" width="800">
  170. </p>
  171. **The Flow:**
  172. | Step | What Happens |
  173. |------|--------------|
  174. | **1. Prompt** | You give your agent a task: "Build a REST API with auth" |
  175. | **2. Plan** | Agent generates a detailed plan with steps, branches, and requirements |
  176. | **3. Visualize** | Overture renders the plan as an interactive graph |
  177. | **4. Enrich** | You click nodes, attach files, select branches, fill in API keys |
  178. | **5. Approve** | You click "Approve & Execute" (or press Enter) |
  179. | **6. Execute** | Watch real-time as nodes pulse, complete, or fail |
  180. | **7. Control** | Pause (Spacebar), resume, re-run nodes, or modify the plan mid-flight |
  181. ---
  182. ## 🛠 Features
  183. ### Interactive Plan Canvas
  184. <p align="center">
  185. <img src="https://raw.githubusercontent.com/SixHq/Overture/main/assets/feature-canvas.png" alt="Interactive Canvas" width="800">
  186. </p>
  187. | Feature | Description |
  188. |---------|-------------|
  189. | **React Flow Canvas** | Full pan, zoom, drag with smooth animations |
  190. | **Streaming Parser** | Plan nodes appear in real-time as the agent generates them |
  191. | **Dagre Auto-Layout** | Intelligent automatic positioning of nodes |
  192. | **Visual Status** | Pending (gray) → Active (pulsing yellow) → Completed (green) / Failed (red) |
  193. | **Next Node Indicator** | Blue pulse shows which node executes next |
  194. | **Complexity Badges** | Low (green), Medium (yellow), High (red) at a glance |
  195. | **Glow Effects** | Shadow glows highlight active and upcoming nodes |
  196. | **Insertable Edges** | Hover over edges to insert new nodes mid-plan |
  197. ---
  198. ### Node Details Panel
  199. <p align="center">
  200. <img src="https://raw.githubusercontent.com/SixHq/Overture/main/assets/feature-node-panel.png" alt="Node Details Panel" width="700">
  201. </p>
  202. Click any node to reveal its full details:
  203. | Info | What You See |
  204. |------|--------------|
  205. | **Title & Description** | Full context for what this step does |
  206. | **Complexity Level** | Low / Medium / High with visual indicator |
  207. | **Expected Output** | What the step should produce |
  208. | **Risks & Edge Cases** | Potential issues to watch for |
  209. | **Pros & Cons** | For branch options, compare trade-offs |
  210. ---
  211. ### Dynamic Fields (User Inputs)
  212. <p align="center">
  213. <img src="https://raw.githubusercontent.com/SixHq/Overture/main/assets/feature-dynamic-fields.png" alt="Dynamic Fields" width="600">
  214. </p>
  215. Nodes can request input from you before execution:
  216. | Field Type | Use Case |
  217. |------------|----------|
  218. | **String** | Project names, URLs, custom values |
  219. | **Number** | Port numbers, limits, counts |
  220. | **Boolean** | Yes/No toggles for options |
  221. | **Select** | Dropdown with predefined choices |
  222. | **Secret** | API keys, tokens (masked input) |
  223. | **File** | File paths to attach context |
  224. Each field includes:
  225. - Required/optional indicator
  226. - Default values
  227. - Help text & descriptions
  228. - Setup instructions ("How to get an API key")
  229. ---
  230. ### File Attachments
  231. <p align="center">
  232. <img src="https://raw.githubusercontent.com/SixHq/Overture/main/assets/feature-attachments.png" alt="File Attachments" width="600">
  233. </p>
  234. Attach context files to specific nodes:
  235. - **Automatic type detection** — Image, code, document, or other
  236. - **Visual icons** per file type
  237. - **Descriptions** — add notes about why this file matters
  238. - **Delete** — remove unwanted attachments
  239. ---
  240. ### Meta Instructions
  241. <p align="center">
  242. <img src="https://raw.githubusercontent.com/SixHq/Overture/main/assets/feature-meta-instructions.png" alt="Meta Instructions" width="600">
  243. </p>
  244. Add custom LLM instructions to any node:
  245. > "Pay special attention to error handling here"
  246. > "Use the existing auth pattern from src/auth.ts"
  247. > "Make sure to add tests for edge cases"
  248. Instructions are sent to the agent right before that node executes.
  249. ---
  250. ### Branch Detection & Selection
  251. <p align="center">
  252. <img src="https://raw.githubusercontent.com/SixHq/Overture/main/assets/feature-branching.png" alt="Branch Selection" width="800">
  253. </p>
  254. When the agent proposes multiple approaches:
  255. | Feature | Description |
  256. |---------|-------------|
  257. | **Auto-Detection** | Branches detected from graph structure (no special markup) |
  258. | **Branch Points** | Nodes with multiple outgoing edges become decision points |
  259. | **Selection Modal** | Side-by-side comparison with pros/cons |
  260. | **Complexity Comparison** | See difficulty level for each option |
  261. | **Visual Indicator** | Selected branch highlighted on canvas |
  262. | **Skip Unselected** | Only your chosen path executes |
  263. ---
  264. ### Requirements Checklist
  265. <p align="center">
  266. <img src="https://raw.githubusercontent.com/SixHq/Overture/main/assets/feature-checklist.png" alt="Requirements Checklist" width="400">
  267. </p>
  268. Before you can approve, Overture shows what's needed:
  269. - **Empty required fields** — counted per node
  270. - **Branch selections** — which decisions are pending
  271. - **Progress indicator** — visual completion tracking
  272. - **Expandable items** — click to see details
  273. - **Color coding** — Green (done) / Orange (pending)
  274. The Approve button stays disabled until all requirements are met.
  275. ---
  276. ### Execution Controls
  277. <p align="center">
  278. <img src="https://raw.githubusercontent.com/SixHq/Overture/main/assets/feature-execution.png" alt="Execution Controls" width="700">
  279. </p>
  280. | Control | How |
  281. |---------|-----|
  282. | **Approve** | Click button or press `Enter` |
  283. | **Pause** | Press `Spacebar` mid-execution |
  284. | **Resume** | Press `Spacebar` again |
  285. | **Re-run Node** | Click failed node → "Re-run" |
  286. | **Re-run From Here** | Re-execute from any node to the end |
  287. The approval button is smart:
  288. - 🟢 **"Approve & Execute"** — plan ready, requirements met
  289. - 🟠 **"Complete Requirements"** — conditions unmet
  290. - 🔵 **"Executing..."** — running with spinner
  291. - 🟢 **"Completed"** — all done
  292. - 🔴 **"Failed"** — error occurred
  293. ---
  294. ### Structured Output
  295. <p align="center">
  296. <img src="https://raw.githubusercontent.com/SixHq/Overture/main/assets/feature-output.png" alt="Structured Output" width="700">
  297. </p>
  298. After each node executes, see rich structured output:
  299. | Category | What It Shows |
  300. |----------|---------------|
  301. | **Overview** | Summary of what was accomplished |
  302. | **Files Changed** | Paths, lines added/removed, diffs |
  303. | **Files Created** | New files with line counts |
  304. | **Files Deleted** | Removed files |
  305. | **Packages Installed** | npm packages with versions |
  306. | **MCP Servers Setup** | Installation status (installed/configured/failed) |
  307. | **Web Searches** | Queries performed, results used |
  308. | **Tool Calls** | Which tools were used and how often |
  309. | **Preview URLs** | Links to deployed sites or previews |
  310. | **Notes** | Info, warnings, errors |
  311. Each category is **expandable** — drill in without visual overload.
  312. ---
  313. ### Output Modal
  314. <p align="center">
  315. <img src="https://raw.githubusercontent.com/SixHq/Overture/main/assets/feature-output-modal.png" alt="Output Modal" width="700">
  316. </p>
  317. Click any completed node to see full output:
  318. - **Scrollable** for long outputs
  319. - **Syntax highlighted** code snippets
  320. - **Close with Escape** or click outside
  321. ---
  322. ## 🏪 MCP Marketplace
  323. <p align="center">
  324. <img src="https://raw.githubusercontent.com/SixHq/Overture/main/assets/feature-marketplace.png" alt="MCP Marketplace" width="800">
  325. </p>
  326. **Browse and attach MCP servers directly from the Overture UI.**
  327. | Feature | Description |
  328. |---------|-------------|
  329. | **Built-in Marketplace** | Search and discover MCP servers |
  330. | **Server Details** | Descriptions, authors, GitHub links, stars |
  331. | **Category Browsing** | Filter by use case |
  332. | **Per-Node Attachment** | Attach specific tools to specific steps |
  333. | **Setup Instructions** | See how to configure each server |
  334. | **Recommended Servers** | Curated list for common tasks |
  335. When you attach an MCP server to a node, the agent gains access to those tools **only for that step**.
  336. ---
  337. ## 📂 Multi-Project Support
  338. Work on multiple projects simultaneously:
  339. | Feature | Description |
  340. |---------|-------------|
  341. | **Tab Navigation** | Switch between projects instantly |
  342. | **Auto Registration** | Projects register on first agent contact |
  343. | **Isolated State** | Each project has separate plans, nodes, configs |
  344. | **Unread Badges** | Know when other projects have updates |
  345. | **Project Context** | See project name, path, and agent type |
  346. Single project? Tab bar hides automatically for a cleaner UI.
  347. ---
  348. ## 📜 Plan History & Persistence
  349. Never lose your work:
  350. | Feature | Description |
  351. |---------|-------------|
  352. | **Auto-Save** | Plans saved every 3 seconds |
  353. | **Local Storage** | Stored in `~/.overture/history.json` |
  354. | **History Browser** | Slide-in panel with all past plans |
  355. | **Status Icons** | Completed, failed, executing, paused |
  356. | **Progress Bars** | Visual completion percentage |
  357. | **One-Click Resume** | Load and continue any past plan |
  358. | **Full Context** | All field values, branch selections, attachments preserved |
  359. ### Resume Information
  360. When resuming, you get complete context:
  361. - **Current node** — where execution stopped
  362. - **Completed nodes** — with their outputs
  363. - **Pending nodes** — what's left to do
  364. - **Failed nodes** — with error messages
  365. - **All configurations** — field values, branches, attachments
  366. - **Timestamps** — when created, when paused
  367. ---
  368. ## ✏️ Dynamic Plan Modification
  369. Modify plans even during execution:
  370. | Operation | Description |
  371. |-----------|-------------|
  372. | **Insert Nodes** | Add new steps mid-execution |
  373. | **Remove Nodes** | Delete steps (edges auto-reconnect) |
  374. | **Replace Content** | Update node title/description in-place |
  375. | **Batch Operations** | Multiple changes in one request |
  376. ### Plan Diff View
  377. When a plan changes, see exactly what's different:
  378. - **Added nodes** — highlighted green
  379. - **Removed nodes** — highlighted red
  380. - **Modified nodes** — yellow with before/after comparison
  381. - **Edge changes** — added/removed connections
  382. ---
  383. ## 🔌 MCP Tools (For Agent Developers)
  384. Overture exposes 11 MCP tools for agents to interact with:
  385. | Tool | Purpose |
  386. |------|---------|
  387. | `submit_plan` | Submit complete plan as XML |
  388. | `get_approval` | Wait for user approval (blocks until approved) |
  389. | `update_node_status` | Update node status + output during execution |
  390. | `plan_completed` | Mark plan as successfully completed |
  391. | `plan_failed` | Mark plan as failed with error message |
  392. | `check_rerun` | Check if user requested a node re-run |
  393. | `check_pause` | Check if user paused execution |
  394. | `get_resume_info` | Get full context for resuming a paused plan |
  395. | `request_plan_update` | Request incremental plan modifications |
  396. | `create_new_plan` | Signal creation of a new plan |
  397. | `get_usage_instructions` | Get agent-specific instructions |
  398. ---
  399. ## 🔄 Real-time WebSocket Communication
  400. **19 server-to-client message types:**
  401. `connected` • `plan_started` • `node_added` • `edge_added` • `plan_ready` • `plan_approved` • `node_status_updated` • `plan_completed` • `plan_failed` • `plan_paused` • `plan_resumed` • `nodes_inserted` • `node_removed` • `project_registered` • `projects_list` • `history_entries` • `plan_loaded` • `resume_plan_info` • `plan_updated`
  402. **16 client-to-server message types:**
  403. `approve_plan` • `cancel_plan` • `rerun_request` • `pause_execution` • `resume_execution` • `insert_nodes` • `remove_node` • `register_project` • `subscribe_project` • `unsubscribe_project` • `get_history` • `load_plan` • `get_resume_info` • `save_plan` • `request_plan_update` • `create_new_plan`
  404. ### Relay Mode
  405. When the WebSocket port is already in use, Overture automatically operates as a **relay client**, forwarding messages through the existing server. Multiple agent instances can share a single UI.
  406. ---
  407. ## ⚙️ Configuration
  408. | Variable | Default | Description |
  409. |----------|---------|-------------|
  410. | `OVERTURE_HTTP_PORT` | `3031` | Port for the web UI |
  411. | `OVERTURE_WS_PORT` | `3030` | Port for WebSocket |
  412. | `OVERTURE_AUTO_OPEN` | `true` | Auto-open browser on start |
  413. ### Setting Environment Variables
  414. <details>
  415. <summary><strong>Claude Code</strong></summary>
  416. ```bash
  417. claude mcp add overture-mcp -e OVERTURE_HTTP_PORT=4000 -e OVERTURE_AUTO_OPEN=false -- npx overture-mcp
  418. ```
  419. </details>
  420. <details>
  421. <summary><strong>Cursor / Cline / Sixth AI</strong></summary>
  422. ```json
  423. {
  424. "mcpServers": {
  425. "overture": {
  426. "command": "npx",
  427. "args": ["overture-mcp"],
  428. "env": {
  429. "OVERTURE_HTTP_PORT": "4000",
  430. "OVERTURE_WS_PORT": "4001",
  431. "OVERTURE_AUTO_OPEN": "false"
  432. }
  433. }
  434. }
  435. }
  436. ```
  437. </details>
  438. <details>
  439. <summary><strong>GitHub Copilot</strong></summary>
  440. ```json
  441. {
  442. "servers": {
  443. "overture": {
  444. "command": "npx",
  445. "args": ["overture-mcp"],
  446. "env": {
  447. "OVERTURE_HTTP_PORT": "4000",
  448. "OVERTURE_WS_PORT": "4001",
  449. "OVERTURE_AUTO_OPEN": "false"
  450. }
  451. }
  452. }
  453. }
  454. ```
  455. </details>
  456. ---
  457. ## ⌨️ Keyboard Shortcuts
  458. | Key | Action |
  459. |-----|--------|
  460. | `Enter` | Approve plan (when ready) |
  461. | `Space` | Pause / Resume execution |
  462. | `Escape` | Deselect current node / Close modal |
  463. ---
  464. ## 🤝 Supported Agents
  465. | Agent | Status | Notes |
  466. |-------|--------|-------|
  467. | **Claude Code** | ✅ Full | Native MCP support |
  468. | **Cursor** | ✅ Full | Via mcp.json config |
  469. | **Cline** | ✅ Full | Via VS Code settings |
  470. | **GitHub Copilot** | ✅ Full | VS Code 1.99+ required |
  471. | **Sixth AI** | ✅ Full | Built-in, zero config |
  472. Each agent has **custom-tailored prompts** for optimal plan generation.
  473. ---
  474. ## 💪 Why Overture?
  475. <table>
  476. <tr>
  477. <td width="50%">
  478. ### For Users
  479. - **Transparency** — See exactly what happens before code is written
  480. - **Control** — Approve, reject, or modify any plan
  481. - **Context** — Attach files and instructions to the right steps
  482. - **Choice** — Compare approaches and pick your path
  483. - **Visibility** — Real-time progress with rich output
  484. - **Safety** — Pause, resume, or re-run at any time
  485. - **History** — Resume any past plan instantly
  486. - **Efficiency** — No wasted tokens on rejected approaches
  487. </td>
  488. <td width="50%">
  489. ### For AI Coding
  490. - **Trust** — Makes agents predictable and controllable
  491. - **Interpretability** — See AI reasoning before execution
  492. - **Universal** — Works with any MCP-compatible agent
  493. - **Extensible** — MCP Marketplace for tool discovery
  494. - **Open Source** — MIT licensed, community-driven
  495. - **Self-Contained** — No cloud dependencies
  496. - **Works Offline** — Fully local execution
  497. - **Multi-Project** — Manage multiple workspaces
  498. </td>
  499. </tr>
  500. </table>
  501. ---
  502. ## 🧑‍💻 Development
  503. ```bash
  504. # Clone the repo
  505. git clone https://github.com/SixHq/Overture.git
  506. cd Overture
  507. # Install dependencies
  508. npm install
  509. # Build all packages
  510. npm run build
  511. # Start MCP server (in one terminal)
  512. cd packages/mcp-server && npm start
  513. # Start UI dev server (in another terminal)
  514. cd packages/ui && npm run dev
  515. ```
  516. ### Tech Stack
  517. | Layer | Technologies |
  518. |-------|--------------|
  519. | **MCP Server** | Node.js, TypeScript, Express, WebSocket (ws), SAX XML Parser |
  520. | **UI** | React 18, React Flow, Zustand, Framer Motion, Tailwind CSS, Vite |
  521. | **Layout** | Dagre (automatic graph positioning) |
  522. ---
  523. ## 🤝 Contributing
  524. Overture is open source and we welcome contributions!
  525. - 🐛 **Report bugs** at [GitHub Issues](https://github.com/SixHq/Overture/issues)
  526. - 💡 **Suggest features** at [GitHub Discussions](https://github.com/SixHq/Overture/discussions)
  527. - 📖 **Improve docs** — PRs welcome
  528. - 🔧 **Contribute code** — see [CONTRIBUTING.md](CONTRIBUTING.md)
  529. All contributions are appreciated, no matter how small.
  530. ---
  531. ## 📄 License
  532. MIT License - see [LICENSE](LICENSE) for details.
  533. ---
  534. <p align="center">
  535. <br>
  536. <img src="https://raw.githubusercontent.com/SixHq/Overture/main/assets/sixth-logo.png" alt="Sixth" width="120">
  537. <br><br>
  538. Built by <a href="https://trysixth.com"><strong>Sixth</strong></a>
  539. <br><br>
  540. For the best experience, try <a href="https://marketplace.visualstudio.com/items?itemName=Sixth.sixth-ai"><strong>Sixth for VS Code</strong></a><br>
  541. Overture is built-in with zero configuration required.
  542. <br><br>
  543. <sub>Stop flying blind. See the plan. Approve it. Execute with confidence.</sub>
  544. </p>
  545. ## Star History
  546. [![Star History Chart](https://api.star-history.com/svg?repos=SixHq/Overture&type=date&legend=top-left)](https://www.star-history.com/#SixHq/Overture&type=date&legend=top-left)

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.