Conversation
The client was pinned to rust-v0.146.0 and only knew the 0.150 multi-agent values through a generator override. Regenerate from codex-cli 0.150.1 and drop the override. The generator now also reads requests declared with optional params (0.150 marks account/usage/read that way, which had silently dropped the method). Server-side: new ChatGPT plan types, the "unknown" MCP auth status, the usage read call, and Thread fixtures gain the now-required projectId; item/tool/requestUserInput fixtures carry isBlocking.
Bump @anthropic-ai/claude-agent-sdk to 0.3.247 and use what it now reports about tasks. task.started carries isBackgrounded, spawnDepth, and ambient. A spawned agent's depth reaches its roster row through subagent metadata, so nested agents get a real tree depth. Ambient housekeeping (live-update watchers and the like) never counts as pending background work: it is flagged on its edges and skipped in snapshot counts, so it cannot hold a thread in "Background" or "Waiting". The session also declares perTaskStopAffordance, so Stop ends the current turn and leaves background agents running; they are stopped one at a time from the Agents tab.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Collaborator
Author
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
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.
Two provider bumps that unblock the Agents tab work. Separate commits, reviewable on their own.
Codex: app-server client on protocol 0.150.1
The client was pinned to rust-v0.146.0 and only knew the 0.150 multi-agent values through a generator override. Regenerated from codex-cli 0.150.1 and dropped the override.
Found along the way:
params?:declarations. 0.150 marksaccount/usage/readthat way, so the token-usage read had silently vanished from the method table. Fixed the parser.Threadgained a requiredprojectId, anditem/tool/requestUserInputgained a requiredisBlocking. Real Codex sends both; our fixtures now do too.unknownMCP auth status are labelled.Effect: Codex subagent nicknames and roles now reach the roster (the Agents tab already prefers the nickname for the row name). Non-blocking questions (
isBlocking: false) are accepted but not modelled yet.Claude: SDK 0.3.238 to 0.3.247
task.startednow carriesisBackgrounded,spawnDepth, andambient. Depth flows into the roster so nested Claude agents indent correctly.perTaskStopAffordance: true: Stop ends the turn only; background agents keep running and are stopped one at a time from the Agents tab. Before, an interrupt killed them all.Testing
schema.test.tsresumes a thread with acompletedsubagent and afollowupTaskcall), contracts 195, server Codex suites 257 and Claude suites 204, web 316.