rcarmo/EditorBridge

Latest recorded source activity: July 5, 2026 at 15:44

SkillsMP catalog refreshed: November 5, 2026 at 19:57

skills collected: 3

GitHub stars: 0
GitHub forks: 0

Install with an AI assistant

Copy this prompt into the AI assistant you're using.

Follow https://skillsmp.com/skill-install/prompt.md to install Agent Skills from https://github.com/rcarmo/EditorBridge.

Repository README

Repository README source: README.md

Read the source README

Expand full README

# EditorBridge A native macOS automation bridge for agent-driven editing in GUI editors. ## Why I wanted to do bulk edits and revisions in long-ish pieces of text but didn't want to be stuck with Obsidian or VS Code, and I most definitely didn't want to create yet another Markdown editor with a bolted-on agent sidebar. Also, I can't rely on Apple's Writing Tools (which are, frankly, amateurish, not to mention likely not available in the EU in full form), and I most definitely didn't want to stay locked in to a single agent harness or provider (yes, Anthropic, I'm looking at you). So I started looking around at the wealth of decent, _fully native_, Markdown editors that are already out there for the Mac, and realized I _did not need to build my own editor_--I just needed to let Pi, Codex, GitHub Copilot and the like use them directly (instead of faffing about with file permissions, sandboxing, etc.) And no, this is not really for _coding_--if it was, I would just use VS Code. ## What EditorBridge provides an MCP server and a set of standard text editing tools to deal with GUI editors that support either AX or AppleScript, and aims to provide agents with tooling to do surgical edits to a document in a live editor. One of the most important tools is to snapshot a document before editing (because if you've ever used Anthropic models, you know they will definitely mess things up). And since I have relatively standard workflows I need to follow, it also allows agents to discover the skills I have for standard form letters, statements of work, presentation outlines... the works. ## MCP Tool Discovery EditorBridge uses progressive discovery so agents do not have to load every editor operation schema at startup. ```text Level 0: advertised by tools/list └── discovery façade ├── editor_tool_search │ └── returns compact matches by query or category ├── editor_tool_describe │ └── returns the full schema for one concrete tool └── editor_tool_call └── invokes a discovered concrete tool with JSON arguments Level 1: compact search results └── name, summary, categories, readOnly/destructive flags, enabled/direct flags Level 2: focused schema load └── full inputSchema and annotations for a single selected tool Level 3: concrete operation call └── validated dispatch to EditorBridgeService and the active editor adapter ``` Concrete tools currently exposed behind the discovery façade: ```text editor tools ├── discovery and diagnostics │ ├── editor_discover │ ├── editor_probe │ └── editor_list_events ├── permissions │ ├── editor_check_permissions │ ├── editor_request_accessibility │ └── editor_open_accessibility_settings ├── reading │ ├── editor_active_document │ ├── editor_read │ └── editor_read_selection ├── snapshots and safety │ ├── editor_snapshot │ ├── editor_preview_patch │ └── editor_restore_snapshot ├── selection and range control │ ├── editor_replace_selection │ └── editor_select_range ├── mutation │ ├── editor_apply_text │ └── editor_apply_patch └── editor commands ├── editor_save └── editor_undo ``` Tool categories are meant for retrieval as much as documentation. For example, an agent can search for `category = "permissions"` before asking for Accessibility access, or `query = "patch snapshot"` before loading any patch schemas. Set `EDITORBRIDGE_DIRECT_TOOLS` to promote a comma-separated subset of concrete tools, or `*`, into `tools/list`. Leave it unset for the default compact discovery surface. ## Build and Run Requirements: - macOS with SwiftPM/Xcode command line tools. - Accessibility permission for the hosting process before using AX-backed editor operations. Build and open the menu bar app: ```sh make open-app ``` Build only: ```sh make app ``` The app bundle is signed after packaging so macOS Accessibility permission is attached to the bundle identity (`dev.piswift.editorbridge`) instead of the raw SwiftPM executable. For stable Accessibility/TCC behavior across rebuilds, create a local code-signing identity once: ```sh make signing-identity ``` Then build normally: ```sh make app CONFIGURATION=release ``` If you have an Apple Development or Developer ID signing identity, you can use that instead: ```sh make app CONFIGURATION=release CODE_SIGN_IDENTITY="Apple Development: Your Name (TEAMID)" ``` For emergency unsigned-style local testing, `CODE_SIGN_IDENTITY=-` falls back to ad-hoc signing, but macOS may require a fresh Accessibility approval after binary changes. Run the test suite: ```sh make test ``` Build the MCP executable: ```sh make mcp ``` Run a local TCP MCP listener: ```sh make mcp-tcp ``` ## Codex MCP Setup Build the MCP executable: ```sh cd /path/to/EditorBridge make mcp ``` Add this to `~/.codex/config.toml`: ```toml [mcp_servers.editorbridge] command = "/path/to/EditorBridge/.build/debug/editorbridge-mcp" args = [] startup_timeout_sec = 30 [mcp_servers.editorbridge.env] EDITORBRIDGE_SKILLS_DIR = "/Users/rcarmo/Library/Application Support/EditorBridge/Skills" # Optional: comma-separated callable-tool allow-list. Omit this key to enable every concrete tool. EDITORBRIDGE_ENABLED_TOOLS = "editor_discover,editor_probe,editor_read,editor_read_selection,editor_snapshot" # Optional: promote direct tools into tools/list. Omit for progressive discovery via editor_tool_search. # EDITORBRIDGE_DIRECT_TOOLS = "editor_read,editor_snapshot" ``` Adjust the paths for your checkout and restart Codex after editing `config.toml`. The server is stdio-based in this configuration, so Codex starts it on demand. By default `tools/list` advertises only `editor_tool_search`, `editor_tool_describe`, and `editor_tool_call`; agents discover and invoke the concrete editor tools through that compact surface. Set `EDITORBRIDGE_DIRECT_TOOLS` to a comma-separated subset, or `*`, only when a client needs selected concrete schemas advertised directly. The menu bar app also hosts a local TCP MCP endpoint for manual MCP testing. Open it with: ```sh make open-app ``` Then open EditorBridge Preferences from the menu bar item to see the current TCP endpoint, copy the stdio Codex config snippet, enable or disable concrete MCP tools, choose the folder that backs `editorbridge://skills`, and open Privacy & Security > Accessibility when macOS permission is needed. Build the PiSwift tool plugin bundle from the nested integration package: ```sh make plugin ``` Install it for PiSwift: ```sh make install-plugin ``` Configuration can be overridden with: ```sh make app CONFIGURATION=release ``` ## Docs See [docs/SPEC.md](docs/SPEC.md).

Loading the repository README…