Yes. ChatGPT scheduled tasks connected to GitHub can create branches when their prompt grants that behavior and the connected GitHub capability has write access.
In the current IDKmesh ChatGPT task set:
agent/reliability/ and allows a new reliability PR in BUILD mode when repository concurrency and overlap guards permit it.Therefore branch proliferation can come from ChatGPT scheduled agents even though no in-repository GitHub Actions workflow continuously creates branches.
A scheduled ChatGPT task is external to .github/workflows/. It can inspect the repository and, when authorized, call GitHub write operations such as creating a branch, committing changes, and opening a PR. Its behavior is controlled by its scheduled prompt and available connector permissions.
The enabled reliability task does not require creating a branch on every run. Its prompt first checks operating mode, PR budget, and file overlap; a new branch is only allowed in BUILD mode.
Keep branch-producing scheduled agents bounded:
This separation is important when diagnosing branch growth: GitHub Actions may be read-only while external ChatGPT agents still have GitHub write authority.