> For the complete documentation index, see [llms.txt](https://docs.katara.ai/about/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.katara.ai/about/brains/github-export.md).

# GitHub export

GitHub export publishes committed Wiki content and its **full reachable history** to a dedicated repository. It is not GitHub source ingestion, original-file backup, or bidirectional repository synchronization.

## Review the disclosure before enabling export

Full history may contain knowledge derived from deleted sources, earlier editor contributions, and withdrawn or expired facts. External copies cannot be recalled. Removing something from the current page, withdrawing a fact, deleting a source or deleting the Brain does not erase past GitHub history or copies.

Original files, private facts and secrets are excluded from the export payload. That exclusion is not a promise to sanitize sensitive information already written into exportable Wiki narrative or history. Review what contributors have committed before approving the destination.

A public destination requires separate acceptance of public disclosure of full history. Unknown visibility must not be treated as private. A scheduled export also requires permission to publish future contributor commits, not only the content reviewed today.

## Before you start

You need current owner authority to configure export, a dedicated GitHub repository destination, and a repository-scoped token appropriate to that destination. Keep the token secret; enter it only in the repository credential field. It is not shown after saving.

Local Wiki freshness and remote export freshness are separate. Review [Knowledge](https://docs.katara.ai/about/brains/knowledge.md) and [Activity](https://docs.katara.ai/about/brains/activity.md) before deciding which content you intend to publish.

## Configure the destination

1. Open the Brain's **Settings → GitHub export** sheet. There is no separate primary Export tab.
2. Enter **GitHub owner** and **Dedicated repository**.
3. Open **Destination proposals** to provide the proposed **Default branch** and **Destination visibility**. Typed values are proposals, not confirmation that the destination has been resolved.
4. Supply the required matching repository-scoped token. Retaining a saved token is permitted only when the form explicitly offers it for the current owner and destination.
5. Choose whether to **Enable export**. Leave **Schedule (UTC; empty for manual)** empty for manual requests, or enter a supported UTC cron schedule.
6. Accept the destination and retention of full history. Separately accept public disclosure when the destination is public. For enabled scheduled export, authorize future contributor commits on that schedule.
7. Save the owner acceptance using **Save configuration** or **Save and enable schedule**, as shown. Review the resolved branch, visibility and saved status.

A saved configuration does **not** request an export. If a destination change invalidates previous confirmation, review the new destination and renew the required consent rather than assuming old acceptance applies.

## Request and monitor an export

Choose **Request export** when it is available. The acceptance receipt means the run was accepted, not that GitHub has been updated. Open **Activity → Export history** to inspect the run and its reported outcome.

Use **Pause export** to stop export through the configured connection. Pausing does not remove previously published content. Editing the schedule or enabling scheduled export again requires renewed consent for future contributor commits.

## Troubleshooting

* **Request export is unavailable:** check current authority, connection state, required consent and the [availability guidance](https://docs.katara.ai/about/reference/availability.md). Do not treat saved configuration as evidence that the export runtime is enabled.
* **Branch or visibility is unresolved:** review the destination proposal and repository credentials. Unreported visibility is not private.
* **Ownership changed:** transfer and recovery pause export. The new owner must provide fresh credentials and renew consent; the former owner's token is not inherited.
* **A run failed or is uncertain:** inspect Export history before requesting another run. A queued receipt is not proof of remote publication.
* **You need information removed externally:** handle the GitHub repository and any copies separately. Katara withdrawal, cleanup and pause actions cannot recall those copies.
