---
title: Repositories
description: "Create the workspace's repos by purpose, clone the whole workspace to your machine, and push with plain git."
canonical_url: https://wiblo.app/docs/developers/cli/repos
last_updated: 2026-10-11T19:02:53+02:00
md_url: https://wiblo.app/docs/developers/cli/repos.md
---

# Repositories

Every workspace owns private git repositories that Wiblo creates and hosts for it. Each repo has a **purpose**: `base` (the one repo your agents learn from: skills, scripts, context), `site` (a website), `app`, or `other`. The purpose decides the template: the base and websites always start from a template, everything else starts empty unless you name one.

- [List repos](/docs/developers/cli/repos/repos-list): `wiblo repos list`
- [Create a repo](/docs/developers/cli/repos/repos-create): `wiblo repos create`
- [List templates](/docs/developers/cli/repos/repos-templates): `wiblo repos templates`
- [Clone the workspace](/docs/developers/cli/repos/repos-clone): `wiblo repos clone`
- [Link a checkout](/docs/developers/cli/repos/repos-link): `wiblo repos link`
- [Add a repo to a run](/docs/developers/cli/repos/repos-add): `wiblo repos add`
- [Remove a checkout](/docs/developers/cli/repos/repos-remove): `wiblo repos remove`

After `wiblo repos clone`, daily work is plain `git`: add, commit, push. A credential helper installed with the CLI turns your Wiblo login into a short-lived ticket for each git operation, so no token is ever stored on your machine.

> **Workspace selection**
>
> The repos commands resolve the workspace like every other command: `--workspace <slug or id>`, then `WIBLO_WORKSPACE`, then the active workspace from `wiblo workspaces use`. Inside an agent sandbox the workspace id and the run id are already set.