A task keeps going after its PR, and you can steer a running agent
A task is now a conversation that can open several PRs and takes replies after a merge, and a message sent mid-run reaches the agent while it works.
The dashboard shows each task as In progress, Queued, Needs your input or Idle, and lists every PR the task opened with its own status. Merging or closing a PR changes that PR, not the task: reply on the ticket and the same task carries on.
A message you send while a run is going now reaches Claude Code as well as oh-my-pi. Sinatra decides whether it changes the work in progress now, gets folded in before the run finishes, or runs as its own next turn, and tells you when it waits. A message from someone who can't spend the running agent's credentials becomes their own next turn instead of being refused.
A CI failure on the task's PR now runs as its own turn, after any work people asked for, and stops after the repository's ci.max_rework attempts in a row with a note on the PR.