Orivox explains how its site editing connector behaves when idle
Zahi Raifer, founder of Orivox, describes what happens to websites built through the company's remote MCP server when the connector sits unused. The server keeps no session state between calls, so a pause or restart loses nothing beyond any request in flight. Site data is held in each project's Git history, which stores every edit as a commit and the original site as a baseline. Edits are sent as lists of operations from a fixed set of 14 verbs rather than as direct file writes, and the editing service applies them the same way regardless of whether the request came from Orivox's own planner or a user's Claude. The article frames the design as making a quiet connector harmless, while acknowledging where that reasoning stops.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)
Log in to join the discussion and vote.
Log in