Version control your team can actually use.

No. A Repository is any version-controlled workspace — a service's source, a quarter's strategy, a set of operating policies. The kind field (code or documents) changes the copy, the editor defaults, and how an AI Employee is briefed; underneath, every Repository is a plain git repository.

No. A local Repository is created empty inside Genosyn with git init and never leaves your server. A remote Repository clones any HTTPS or SSH URL — GitHub, GitLab, Bitbucket, or a self-hosted server. And a local one can be connected to GitHub whenever you want, which creates it there and pushes the history it already has.

It creates the repository on GitHub through the Connection your company already authorised under Settings → Integrations, then pushes the history the repository already has. Nobody creates or pastes a personal access token: the Connection's token is resolved per operation and never stored on the repository, and later pushes to that remote use the same Connection. Branches from AI work sessions are deliberately left out of that first push. If you would rather create the repository yourself, paste the clone URL of an empty one instead — a remote that already has commits is refused, not force-pushed. Owner or admin only.

Not for this. The browser editor and AI work sessions run against a server-owned checkout with no shell involved, so they work on the standard Docker install. The separate per-employee checkout — the one an employee uses with ordinary git during open-ended chat and Routine work — still needs coding execution enabled.

No. It commits to its own branch in its own worktree. A Member reviews the diff and merges, and only an owner or admin can push. Credentials are used exclusively in that push path and never enter a tree a model can reach.

Browsing, searching, editing, committing, branching, and starting AI work sessions are open to any company Member. Pushing, pulling, connecting a repository to a remote, and repository configuration — clone URL, credentials, and AI grants — require an owner or admin, because a local commit can be undone and a push cannot be recalled.

Encrypted at rest with AES-256-GCM, the same protection as model API keys, and never shown back in plaintext — the UI reports only whether a credential is set. An SSH key is written to an App-private temporary directory for exactly one operation and removed afterwards.

It removes the grants, the work sessions, and the server-side checkout. A remote repository is never touched on its host. A local repository has no remote, so deleting it deletes the only copy of its history.