How to keep your repository before a team is deleted
When a team is archived — after a plan downgrade or a cancellation — what happens to its repository depends on the repository type. Your own connected GitHub repository is never touched. A Quick-start repository provisioned by Operum is deleted together with the team, so this guide shows how to keep it.
First, which kind of repository is it?
Operum teams use one of two repository types, and only one of them needs any action:
- Your connected GitHub repository — a repository you already own and connected to Operum. It lives on your own GitHub account.
- A Quick-start repository provisioned by Operum — a
repository Operum created for you (it lives under
operum-ai/<name>). You can see and manage it in the Operum desktop app under Settings → Managed Repository, which only appears for Quick-start teams.
Your connected GitHub repository — nothing to do
Your connected GitHub repository stays on your own account — nothing there changes. Archiving or deleting a team only removes the Operum-side state (agent configurations, team knowledge, and run history). Your code, issues, PRs, and branches remain exactly as they are on github.com.
Quick-start repositories — keep them before deletion
Quick-start repositories provisioned by Operum are archived read-only when the team is archived, and they are deleted together with the team once the recovery window closes. If you want to keep one, save it before then.
Both options live in the Operum desktop app under Settings → Managed Repository — no cancellation required, and you can do this anytime while the repository still exists:
- Export it as a ZIP. Use Download zip to get a snapshot of the repository. Operum prepares a private download link that is valid for 1 hour and supports repositories up to 100 MB. Good when you just want a local backup and don't have a GitHub destination ready.
- Transfer it to your own GitHub account. Use the Fork to GitHub control (despite the label, it performs a GitHub transfer, not a public fork): enter the GitHub username or organisation to transfer to, and confirm. GitHub queues the transfer and the new owner accepts it from an email invite. Once accepted, you own the repository — with its full history, branches, and issues — outright, and Operum no longer hosts it.
Why isn't a plain GitHub "fork" offered? Quick-start repositories are private and live inside Operum's GitHub organisation, so a standard GitHub fork doesn't apply. The transfer above moves the whole repository to your account instead, and the ZIP gives you a files-only snapshot.
Only you can copy or transfer your repository
Only you, signed in to your own Operum account, can export or transfer your Quick-start (Operum-managed) repository. Every copy, transfer, or ZIP-export action is authenticated against your account and authorised against the repository's owner — no other Operum user, and no unauthenticated request, can read, export, transfer, or obtain a token for your private managed repository.
Quick-start repositories stay private inside Operum's GitHub organisation and are reachable only through Operum acting on your own authorised request. A transfer additionally requires the destination GitHub account to explicitly accept it, so a repository can never be silently pushed to someone else. The ZIP download link is private, scoped to your repository, and expires after one hour.
Do it before the recovery window closes
An archived team stays restorable for a 30-day recovery window — upgrade back to a plan that supports the team count and restore it from the Archived teams page in your account. Once that window closes, the team and any Quick-start repository it owns are deleted. Export or transfer a Quick-start repository before the window ends if you want to keep it.
Need help?
Email team@operum.ai before the recovery window expires and we'll do what we can to help.