There are two ways to get Sepo into a repository: start fresh from the template, or install it into a project you already have. Both end the same way — you mention @sepo-agent in an issue and it answers.
Path 1: start from the template
- Create a new repository from self-evolving/repo with Use this template. (Forking works too, but forks often have Issues or Actions disabled by default.)
- Install the Sepo GitHub App. For a first setup, choose Only select repositories and pick the repository you just created.
- Add at least one model-provider credential as a repository secret under
Settings > Secrets and variables > Actions:OPENAI_API_KEYfor Codex-backed runs, orCLAUDE_CODE_OAUTH_TOKEN/ANTHROPIC_API_KEYfor Claude-backed runs. - Confirm Issues and Actions are enabled in the repository settings.
- Run
Agent / Onboarding / Check Setupfrom the Actions tab. It creates the built-inagent/*trigger labels and opens aSepo setup checkissue with configuration status and copyable test commands.
Path 2: install into an existing repository
For a public repository, the quickest path is to open an Install Sepo into another repository issue in self-evolving/repo and paste your repository’s URL — Sepo runs the install for you.
For the manual route (or private repositories), follow Install into an existing repository. It covers copying .agent/ and .github/, configuring secrets, running the onboarding setup check, and bootstrapping the agent/memory branch.
Check that it works
Open an issue and mention @sepo-agent in the body or a comment:
@sepo-agent what does this repository do?After a short delay the workflow adds an 👀 reaction, and then posts a response in the thread. If nothing happens, re-run Agent / Onboarding / Check Setup and work through the items it flags — the most common misses are the App not being installed for the repository or a missing model-provider secret.
Next: your first agent session.