Remote Spaces

A Remote Space is a Space inside a Vibecape Group. The server stores a bare Git repository; each user works in a complete local clone.

Create or open from the App

Open the Space selector and choose a joined Group. Owners can create a project; members can open an existing project and choose a local directory. The App obtains the clone endpoint from the Group and Space metadata, so users do not paste Git URLs.

Use the CLI

vibecape space list --group <group-url>
vibecape space create . --group <group-url> --name "Project name"
vibecape space clone <space-id> ./project --group <group-url>
vibecape space settings ./project

Connection information lives in the Git remote. Vibecape does not create .vibecape/space.json, and it never places a server database inside the Space directory.

What Sync does

Core Sync flushes open documents, creates a local checkpoint, fetches main, integrates compatible remote changes, and pushes when authorized. Conflicts remain in the local clone for resolution; a failed network request never deletes local edits.

.downcity/ and .vibecape/ contain machine-local runtime state. The App and CLI maintain .gitignore and automatically stop tracking these directories without deleting local files. For real content conflicts, resolve each file by keeping your version, using the remote version, or editing it manually before continuing.

The Git extension remains useful for status, staging, history, branches, and manual Git operations. Remote Space membership and Core Sync belong to Vibecape Core and continue to work without the Git extension.

Files and size limits

Text and ordinary images can be committed normally. A server hook rejects any individual Git blob larger than 20 MiB. Keep video and large binary assets outside the Space until Git LFS support is available.