# Private Content Repo

> **Coming Soon**

## The Problem

Teams have internal documentation that agents need: private API references, deployment playbooks, coding conventions, auth patterns. This content doesn't belong in a public registry, but agents should be able to search and fetch it just as easily as public docs.

Today, you can build local content with `chub build` and point your config at it. But distributing that content across a team — keeping it in sync, versioned, and accessible to every developer's agent — is a manual process.

We're working on making private content repos easy to set up, distribute, and keep current across your team.

## What we're solving for

- **Team-wide conventions** — Every agent on your team should follow the same patterns. Write them once, distribute everywhere.
- **Internal API docs** — Your private APIs need the same quality docs as public ones. Agents shouldn't have to guess.
- **Seamless search** — `chub search` should cover both public and private content without extra steps.
- **Easy distribution** — Adding a new team member's agent to the private repo should be simple.

## Enterprise

For enterprise use cases, reach out at info@tbd-domain.com.
