Rope Session

Rope Session connects a running Rope Notes workspace to a desktop agent through a local MCP companion. The current documented client setup is for Codex. It lets the agent inspect the text you are actually editing, including unsaved changes, alongside terminal output, Git status and diffs, and language diagnostics.

Reading is the default capability. Editor navigation, edits, and saving require separate opt-ins. Sharing can disclose sensitive information in buffers or terminal output; review the scope before approving it.

Share a desktop workspace

1. Open the workspace in desktop Rope Notes.
2. Open Preferences → Extensions → Share this Rope session and enable the bridge.
3. Expand Share this desktop workspace instead, load the desktop chats, and select the intended conversation.
4. Choose whether to allow navigation, editing, or saving, then use Share with this desktop chat and review the disclosure prompt.
5. Use Copy MCP TOML to obtain the companion configuration. Add it to the trusted configuration for the desktop client and reload its MCP configuration as required.

The bridge must be attached to the approved chat. Installing the MCP companion alone does not grant workspace access.

Share the phone's live workspace

This route needs both a working remote conversation connection and separate Rope pairing and live sync. Codex and the MCP companion run on the desktop; the desktop relays requests to the approved phone workspace.

1. On both devices, select the exact trusted Rope peer and start live sync for the corresponding workspace.
2. On desktop, enable session sharing, select the phone under Trusted Rope peer, and choose Listen for paired offers.
3. On the phone, enable session sharing, choose Use connected Codex chat, select the trusted desktop peer, and choose Offer this chat. Review the requested disclosure and optional editor capabilities.
4. Configure the desktop MCP companion once using Copy MCP TOML, then explicitly accept the incoming peer and chat offer on the desktop.

After a disconnect or a workspace change, a fresh sharing approval may be required. Reapproval does not require a new companion configuration.

Read, edit, and save with a defined scope

• Read: Inspect bounded live buffer text, terminal output, Git status and diffs, and diagnostics.
• Navigate: Optionally let the agent open or reveal workspace files on the owning device.
• Edit: Optionally accept version-checked changes to a live buffer. Each successful batch is one Undo step; editing does not automatically save.
• Save: Separately permit saving the named document at its expected version. Stale requests or conflicting changes are rejected.

Directly permitted buffer edits are distinct from the local agent's accept/reject proposal workflow. Enable this capability only when you want the connected agent to edit within its approved scope.

Follow open remote chats can extend a session approval to participating conversations. Each chat retains its own grant, and only the focused chat can navigate the editor. Background participants may read or apply permitted version-checked edits. Close a chat to remove its access, or revoke sharing for the whole session.

The bridge does not provide terminal input, command execution, or Git mutations. The current documented integration is with Codex; this guide does not claim compatibility with other MCP clients.

Rope Notes is independent of OpenAI and is not affiliated with, sponsored by, or endorsed by it. OpenAI, ChatGPT, and Codex are third-party names used to identify the integration.