Install Sepo agent infrastructure

AS
8d ago
+62857-0

Summary

Adds the Sepo agent backend to this repository so @sepo-agent can answer, implement, review, and fix work on GitHub. This PR adds agent infrastructure only — no application source, secrets, or branch protection are changed.

Installed from the latest stable Sepo release v0.5.0 (self-evolving/repo).

Required setup after merge

  1. Install the Sepo GitHub App on this repository, or choose another auth path from the setup guide.
  2. Add at least one model-provider secret under Actions secrets: OPENAI_API_KEY, CLAUDE_CODE_OAUTH_TOKEN, and/or ANTHROPIC_API_KEY.
  3. Run the Agent / Onboarding / Check Setup workflow.
  4. Review the Sepo setup check issue it opens and complete any remaining setup it reports.
  5. If agent/memory is missing, run Agent / Memory / Initialization.
  6. Optionally run Agent / Rubrics / Initialization if this repo wants rubric steering.

Also confirm Issues and GitHub Actions are enabled (Settings → General → Features, Settings → Actions → General).

Source revision

  • self-evolving/repo @ v0.5.0 (5f7d2032080e9c0578d0e4cb3b98b2f695f33547)

Installed files

  • .agent/ — agent backend (265 files), excluding generated .agent/dist/ and .agent/node_modules/.
  • .github/ — agent workflows (28), composite actions, prompts, issue templates, and assets, merged into the existing .github/.
  • .gitignore — appended .agent/dist/ and .agent/node_modules/.

Preserved / skipped

  • All target-owned .github/ files preserved; the conflict audit found no source path that collides with an existing target path.
  • Root README.md, AGENTS.md, and .skills/ were not copied (install defaults).
  • No application source changed.

Validation

  • npm ci, npm run build, and npm test pass on the source at v0.5.0 (run once against the identical payload).
  • git diff --cached --check is clean.
  • Conflict audit: no source .github path collides with an existing target path.

Skipped checks

  • Per-repo .agent build/test not rerun; the payload is byte-identical to the validated source revision.

This PR was created by an AI agent (OpenHands) on behalf of @ashcoft.


Devin Review


Summary by cubic

Installs the Sepo agent backend from self-evolving/repo v0.5.0 so @sepo-agent can answer, implement, review, and fix work on GitHub. Agent infrastructure only — no application source, secrets, or branch protection are changed.

Required setup after merge

  • Install the Sepo GitHub App on this repository.
  • Add at least one model-provider secret: OPENAI_API_KEY, CLAUDE_CODE_OAUTH_TOKEN, or ANTHROPIC_API_KEY.
  • Run the Agent / Onboarding / Check Setup workflow, then complete any remaining setup in the issue it opens.
  • Confirm Issues and GitHub Actions are enabled in repository settings.

This change is Reviewable

RetriggerView in GreptileConfidence Score: 2/5

Do not merge until the fix workflow protects trusted agent code and fork review requests can use the configured provider.

Fix All in CodexFindings

  1. P1 Security PR replaces trusted agent code ▶
  2. P1 Fork PR mentions fail ▶
  3. P2 Staged edits skip checks ▶
Fix with agent prompt
### Issue 1
.github/workflows/agent-fix-pr.yml:153-159
`agent-fix-pr.yml` switches the runtime checkout to the PR branch before loading `run-agent-task`. A same-repository PR can replace that local action and receive the GitHub token and provider secrets passed into it. Branches created before this installation instead lose the action and prompts, so the fix run fails before starting.

Keep the runtime on the trusted default branch and edit the PR in a separate worktree.

**How this was verified:** `checkout-pr.ts` replaces the working tree with the PR head before the workflow loads a local action and passes it write credentials and provider secrets.

### Issue 2
.github/workflows/agent-entrypoint.yml:14-17
Mentions in fork PR reviews and inline comments run under `pull_request_review` and `pull_request_review_comment`, which do not receive repository secrets. With the documented API-key setup and default provider selection, even a maintainer's `/answer` request reaches `Resolve answer provider` without keys and fails without replying.

Use a trusted base-repository entry point for these requests, while keeping fork code out of the privileged runtime checkout.

### Issue 3
.agent/scripts/post-agent-verify.sh:18-26
`post-agent-verify.sh` ignores staged changes. If the agent stages a workflow or runtime edit, `hasChanges()` still requests verification, but both `git diff --check` and the changed-file list omit that edit. The workflow can then commit and push it without the intended YAML or build checks.

Include `git diff --cached --check` and staged paths.

```suggestion
git diff --check
git diff --cached --check

changed_files="$(
  {
    printf '%s\n' "$history_changed_files"
    git diff --name-only
    git diff --cached --name-only
    git ls-files --others --exclude-standard
  } | sed '/^$/d' | sort -u
)"
```

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Summary

Installs Sepo's agent runtime, documentation, shared actions, and GitHub workflows without changing application code.

  • GitHub requests can now reach the installed Sepo agent workflows.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart TD
  A[GitHub mention or label] --> B[Router and access checks]
  B --> C[Answer]
  B --> D[Implementation]
  B --> E[Review]
  B --> F[Fix PR]
  F --> G[Build runtime on default branch]
  G --> H[Replace checkout with PR branch]
  H --> I[Load local action with credentials]
  E --> J[Check reviewed head]
  J --> K[Optional approval and merge]

Reviews (1) · Last reviewed commit: "chore: install Sepo agent infrastructure" · Reviewed by Greptile