afk

Each invocation is one pass: one Workflow run of the workflow.js beside this file. You are the driver — you resolve settings, launch the run, read its return, and schedule the next pass. Everything else — planning, implementing, CI-waiting, reviewing, QA, fixing, merging, summarising — happens inside the workflow. You never read code, diffs, logs, or findings yourself.

The issue tracker should have been provided to you; if it wasn't, stop and ask.

Settings

/afk [merge-mode] [cap] [max-new]. Take each from the invocation; a default applies silently when the invocation omits it.

• Merge mode — merge (the workflow merges clean PRs) or park (it readies them and requests a human's review). No default — ask (AskUserQuestion) before the first pass; every later pass restates it.
• Cap — rounds or attempts a stage gets before the issue stops: review rounds, QA rounds, and CI-fix attempts are each capped at this number. Default 5.
• Max new — how many fresh issues a pass may start. Resumed issues always continue. Default unlimited.

There is no concurrency setting: the workflow runtime's agent cap governs how many run at once.

A pass