Introduction

Code Storage is managed Git infrastructure for agents. Create repositories, write commits, merge branches, and get Git remote URLs through the SDK, the HTTP API, or Git over HTTPS.

Create a repository on demand for each user, project, or agent session, and commit to it without a local clone. Each Code Storage request uses a JSON Web Token that your organization signs. You control the repository access, scopes, expiration, and ref policy in each JWT, so every client, agent, or task gets exactly the access it needs.

TypeScript

import { GitStorage } from '@pierre/storage';

const storage = new GitStorage({
  name: 'your-org',
  key: process.env.PIERRE_PRIVATE_KEY!,
});

const repo = await storage.createRepo({ id: 'new-workspace' });

const result = await repo
  .createCommit({
    targetBranch: 'main',
    commitMessage: 'Get started with Code Storage',
    author: { name: 'Pierre', email: '[e-mail]' },
  })
  .addFileFromString('README.md', '# Getting started\n')
  .addFileFromString('main.ts', 'console.log("Hello from Code Storage");')
  .send();

console.log(result.commitSha);

Features

• Git Operations. Clone, fetch, push, and pull over HTTPS with JWT-authenticated remotes.
• Git LFS. Track large files over the same remote, with no separate LFS server.
• Git Notes. Attach metadata to commits and keep note streams isolated by ref.
• Ref Policies. Limit the refs that a JWT can update and reject force pushes.
• Commit Signing. Register keys and require signed commits on selected refs.
• Import Namespace. Bulk push large repositories, which Code Storage moves to cold storage.
• Ephemeral Namespace. Create isolated refs for previews and experiments, then promote them.
• Repository Forks. Copy a repository for a template, a snapshot, or isolated work.
• GitHub Sync. Mirror a GitHub repository to and from Code Storage.
• Generic Sync. Mirror a GitLab, Bitbucket, or other HTTPS Git repository.
• Webhooks. Receive push and sync events, verified with HMAC signatures.

Workflows

These workflows give agents isolated, disposable Git state.

• Connect a Sandbox. Clone into Modal, E2B, Daytona, and other sandboxes with authenticated URLs.
• Load Agent Memory. Load selected memory files from one exact version, then save changes without a lost update.
• Store Session State. Store agent session state as ephemeral commits, with the normal branches unchanged.
• Resume Sandbox Work. Restore the last session state in a new sandbox.
• Show Live Diffs. Render an agent branch as a live diff that refreshes on each new state.
• Manage Product Files. Store product files in a managed repository, validate each change, and apply one exact revision.
• Run Parallel Attempts. Start several attempts from one commit and promote the best result.

Get started

Follow these steps in order:

1. Agent Setup: Give your agent the current docs through MCP or llms.txt.
2. Authentication & Security: Create an API key, store it, and sign JWTs with scopes and ref policies.
3. Quick Start: Install the SDK, create a repository, and make your first commit.

Code Storage does not provide pull requests, issues, or code review.