git.
This page covers the plain Git interface — everything here happens in a clone, with ordinary git. Use Repository Mounts when an agent should work inside a mounted directory, persist snapshots, and promote when ready; Git or the tl CLI? is the one-rule guide for choosing between them.
Use Repository SDKs when you want to create repositories, inspect refs, push worktrees, or merge branches from Python or TypeScript.
Create a Repository
project_9f3c2a1b is the project your tl login is scoped to. You do not pass it to every command.
You can also create a repository lazily by pushing to a repository path that does not exist yet. Lazy creation only applies to git push; git clone and git fetch require the repository to already exist.
Get a Credential
Tensorlake authenticates Git operations with HTTP Basic Auth, not SSH keys. First make sure you are logged in:t. The password is the token.
Clone
Use Git’s credential store:Branch, Commit, and Push
From here, it is ordinary Git:Merge Changes
Tensorlake does not add a pull-request layer on top of Git repositories. Merge locally, then push the result:What Plain Git Does Not Cover
- Workspaces, snapshots, promotion, and rebase are the mount model for agent sessions. See Repository Mounts.
- Workspace refs such as
refs/workspaces/...are reserved on the server and cannot be updated with directgit push. - Archived repositories are read-only until restored with
tl git restore <repo>.
Repository Mounts
Mount repositories as directories for agent sessions.
Merging Changes
Land workspaces on moved branches and merge branches directly.
Repository SDKs
Create repositories, push worktrees, and merge branches from Python or TypeScript.
Authentication
tl login, Git credentials, scopes, and token lifetime.Architecture
How storage, lazy content delivery, merging, and observability work.