Edit project files together

What live co-editing does

Open the same project file in the BlinkHost IDE with another workspace member. BlinkHost merges each acknowledged edit into the shared document, shows who else is present and marks their latest cursor position. Changes continue through the normal project autosave flow.

Live edits do not create Git commits, push a branch or deploy the project. Use the explicit source-control and publish actions when the team is ready.

Connection and recovery states

The editor reports its current state near the top-right corner:

• Live edits connected means acknowledged edits are being exchanged.
• Recovering saved edits means the browser is sending edits retained after a reload or interrupted connection.
• Offline — edits are queued means this browser is keeping new edits locally and will retry. Keep the tab or browser profile available until it reconnects.
• Document changed — reload to continue means the live document moved to a new session. Reload before making more changes so the editor can start from the current shared state.

Acknowledged edit history remains recoverable for the period listed in the workspace plan. Very old history may be consolidated into an integrity-checked checkpoint without changing the current document.

Access and review

Workspace owners, administrators and developers can edit project files together. Owners and administrators can grant an existing BlinkHost account time-limited viewer, reviewer or editor access through the collaboration access API. A file-specific grant cannot be used to open another file; project-wide access should be used only when the guest needs it.

POST /api/source-control/collaboration/access-grants/
Content-Type: application/json

{
  "project": "PROJECT_ID",
  "document_id": "FILE_ID",
  "email": "reviewer@example.com",
  "role": "reviewer",
  "expires_at": "2026-08-25T12:00:00Z"
}

Use the file ID returned with the project's browser-IDE file tree. Leave document_id empty only when the person needs every collaborative document in the project. The email must already belong to a BlinkHost account. Delete the access-grant resource to revoke it.

Remove access when the work is complete. Presence expires shortly after a participant leaves, and revoking a grant stops later replay, presence and edit requests.

If changes do not appear

Confirm that both people opened the same project and file, then check the connection label. If the editor is offline, restore the network connection and leave the document open while queued edits are acknowledged. If the label asks you to reload, copy any text you need as an extra precaution, reload the IDE and compare the recovered document before continuing.

If recovery still fails, contact support@blinkhost.me with the project name, file name, approximate time and the connection label. Do not send secrets or private source code by email.