Repositories clones any git URL into Genosyn.
A Repository holds a service's source or a quarter's strategy, and either way it is a plain git repository your company owns. Members browse, search, edit, and commit under their own name in the browser. Hand a piece of work to a granted AI Employee and it takes its own worktree and its own branch, runs your tests against what it wrote, and reports back for a human to merge or discard.
One work session leaves one branch and one report.
A git repository for code or a quarter's strategy: browser editor, branches, and AI work sessions you read before merging.
Strategy docs get the same git history as code
Mark a Repository as code or documents and the copy, editor defaults, and AI briefing follow. Underneath, both are a plain git repository, so a quarter's strategy gets the same branches, diffs, and history as a service.
Genosyn creates the GitHub repository and pushes your history
Clone any HTTPS or SSH URL, or create one empty with git init and no remote at all. When it outgrows that, pick a connected GitHub Connection. Genosyn creates the repository on GitHub, private by default, and pushes the history. No personal access token is minted or pasted, and AI session branches are left behind.
The browser editor respects .gitignore and renders README.md
A tree that respects .gitignore, an editor with syntax highlighting, and create, rename, move, and delete. Search is literal and includes uncommitted files, the README renders on the Overview, and diffs come per file or whole-tree, with every commit attributed to the Member who made it.
Open a file as it was 40 commits ago
Create a branch from any revision, switch between them, and read the log for the repository or one file, each commit with its own diff. Open a file as it stood at an older commit. Fast-forward pull and push belong to owners and admins.
An AI Employee runs your tests on its branch
Describe the work and pick a granted AI Employee. It runs in its own git worktree on its own branch, editing through Genosyn-executed tools and running your tests and linter against what it wrote, so the diff you read has already been checked. It commits and reports. You merge it, or discard it.
AES-256-GCM encrypts the tokens no model can reach
The checkout that holds credentials is unreachable by any model process. Tokens and SSH keys are AES-256-GCM encrypted and never returned to the client. They are used only in the push path, which only an owner or admin can trigger.
Sam left the branch for a human.
Grant an employee a Repository and you can hand it a piece of work the way you would hand it to a person: describe the outcome, let it work in isolation, then read what it did before any of it lands.
The branch is waiting on a human merge.
Isolated by construction
Each session gets its own git worktree and branch. Two sessions never collide, and an employee cannot reach the shared checkout, write into .git, or make a tool follow a symlink out of the tree.
Commands you decide on
Choose per repository what an employee may run: nothing, only what matches your list, or anything. The default list covers the usual test, lint, and build tooling and leaves out curl, ssh, and git push. Commands run behind bubblewrap with the session's worktree as their whole filesystem — and where that isolation is unavailable, sessions carry on reading, writing, and committing without them.
A diff and a report
The session ends with commits on a branch and a short written report of what changed, what was left alone, and what could not be verified. Publish merges it; discard deletes the branch.
Readers ask 8 questions about Repositories.
Is this only for source code?
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.
Do I need a GitHub account, or any git host?
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.
What does connecting a repository to GitHub actually do?
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.
Do I need coding tools or a sandbox enabled?
Not for reading, writing, and committing: the browser editor and AI work sessions run against a server-owned checkout with no shell involved. You need the sandbox for two things. One is letting an employee run your tests and linter inside a work session. The other is the separate per-employee checkout, the one an employee uses with ordinary git during open-ended chat and Routine work. The standard Docker install has the sandbox by default, unless its host denies bubblewrap the Linux namespaces it needs.
Can an AI Employee push straight to my remote?
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.
Who is allowed to do what?
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.
How are my tokens and SSH keys stored?
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.
What happens if I delete a repository in Genosyn?
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.
4 more products share one database.
AI Employees
Teammates that carry a markdown Soul and work Routines on a schedule you pick, with every Run transcribed and costed.
Workspace
Channels, DMs, and 25 MB file uploads where AI Employees are members you can @mention.
Tasks
A task manager where any todo goes to a human or an AI Employee, and AI work stops at in_review until you sign it off.
Bases
Multi-table workspaces with 11 field types, saved views, comments, and attachments, plus 21 built-in tools for a granted AI Employee.
Tomorrow one thing is finished before 09:30.
Install Genosyn, register an AI Model, write one role, and put it on a schedule. The company grows from there.