Skip to content

chore(claude): move to @col/a2a-claude@0.2.1-beta.7 - #12

Merged
col merged 1 commit into
mainfrom
chore/a2a-claude-beta-7
Aug 19, 2026
Merged

chore(claude): move to @col/a2a-claude@0.2.1-beta.7#12
col merged 1 commit into
mainfrom
chore/a2a-claude-beta-7

Conversation

@col

@col col commented Aug 19, 2026

Copy link
Copy Markdown
Owner

Moves throng-agent-claude to @col/a2a-claude@0.2.1-beta.7 (pulls @anthropic-ai/claude-agent-sdk 0.3.2020.3.235).

What the new wrapper version changes

It drives the Claude Agent SDK through a streaming input session rather than a one-shot prompt, so a single A2A Task can span several SDK rounds:

  • A turn that ends with background work still in flight leaves the Task in working and publishes a non-final response artifact per round. The Task only reaches a terminal state on a round that ends with nothing running.
  • Held rounds carry metadata.backgroundTasks on their status update, and the live set is published as a trace.background_tasks artifact.
  • agent_started / agent_finished are now deduplicated per Task instead of per SDK turn.

Throng-side changes

None needed. Both behaviours are on by the wrapper's own defaults (features.holdTaskForBackgroundWork, features.emitBackgroundTaskEvents) and Throng sends no features block, so the generated config is byte-identical.

The only edit beyond the version bump is a comment in config/build.ts recording the edge our timeouts.prompt: 0 inherits: with the timeout off and the Task held for background work, tasks/cancel is the only release if the background set never empties — and a held Task blocks later turns on the same contextId.

Also worth knowing for manifest authors: agent.max_turns now spans every round of a held-open Task rather than resetting per round.

Verification

npm run build, npm run typecheck, npm test — all green (115 tests).

🤖 Generated with Claude Code

https://claude.ai/code/session_01My4JH7AAyLhe9Hb5626Gdv

The wrapper now drives the Claude Agent SDK through a streaming input
session, so a Task whose turn ends with background work still running is
held open in `working` and reports back over several rounds instead of
completing at the first result.

Nothing to configure: both new features default on in the wrapper and
Throng sets no `features` block. The build.ts note records the one edge
that our `timeouts.prompt: 0` inherits — cancellation is the only release
for a Task whose background set never empties.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01My4JH7AAyLhe9Hb5626Gdv
@col
col merged commit 75a1c6d into main Aug 19, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant