feat(agents): mark agents the provider runs in the background - #196
Merged
Conversation
The Agents tab could not tell a background agent from one the turn was waiting on, even though the Claude SDK reports it on every agent task. The roster gains an optional isBackgrounded flag (new nullable column on projection_thread_subagents, migration 049; NULL/0/1 mapped at the row boundary the same way message streaming flags are). The Claude adapter sends it with the depth at task start and again when a foreground agent is moved to the background. Live rows show "background" in the meta line after the model and effort; finished rows do not, since how an agent was launched no longer matters on a receipt. Codex never sets it. Also fixes a latent projection bug the move exposed: a metadata update that carried no depth information reset the agent's depth to 0.
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
github-actions
Bot
added
vouch:trusted
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Agents tab could not tell a background agent from one the turn was waiting on, even though the Claude SDK reports this on every agent task.
What changed
isBackgroundedflag: new nullable column onprojection_thread_subagents(migration 049). NULL/0/1 is mapped at the row boundary the same way the message streaming flag is, in one shared helper used by the repository and the snapshot query.task_started, and again when atask_updatedpatch moves a foreground agent to the background.backgroundin the meta line after the model and effort. Finished rows do not; how an agent was launched no longer matters on a receipt. Codex never sets the flag, since its agents always block the parent.subagent.metadataupdate that carried no depth information reset the agent's depth to 0. A payload now only sets depth when it knows it.Testing
backgroundappears on a live backgrounded row, not on a live foreground one, not on a finished one.