Is there an agent or in-repository automation in MSKazemi/idkmesh that continuously creates new branches?
No in-repository agent or scheduled GitHub Actions workflow was found that continuously creates branches.
The repository does have many non-main branches, including acceptance, benchmark, integration, feature, maintenance, and Codex-named branches. Their presence by itself does not prove that a resident continuous branch-creation agent exists; the GitHub branches endpoint does not expose the creator or creation event for each branch.
.github/workflows/branch-convergence-audit.yml
17 4 * * *), on main pushes, PR lifecycle events, and manual dispatch.contents: read and pull-requests: read permissions..github/workflows/evolution-loop.yml
17 5 * * *).contents, issues, PRs, and Actions permissions..github/workflows/real-node-verifier-e2e.yml
contents: read, persist-credentials: false, and explicitly documents that it has no push or merge authority.Repository code searches for branch-creation/push patterns such as create branch, git branch, and git push returned no matching implementation. GitHub code search reported an incomplete index for one permission query, so this is best understood as an audit of the currently visible repository mechanisms rather than proof about external tools.
The large branch population is more consistent with branches created during manual work, pull-request work, external coding-agent sessions, or one-off integration/evidence work. An external agent connected through GitHub can create a branch without a branch-creation loop being defined inside this repository.
Do not add a branch-creation agent that creates branches simply because time passes. If autonomous branch creation is introduced later, make it demand-driven and bounded: create a branch only for a selected work unit, attach it to an issue/PR, enforce a branch budget and TTL, and converge or delete it after completion. The existing Branch Convergence Audit should remain the read-only governor over that lifecycle.