Version Packages - #123
Merged
Merged
Conversation
tangletools
approved these changes
Aug 4, 2026
tangletools
left a comment
There was a problem hiding this comment.
✅ Auto-approved GitHub Actions PR — 64e9dd70
This PR was opened by trusted GitHub Actions automation.
The full PR reviewer audit still runs separately and will publish findings if it detects issues.
tangletools · auto-approval · reason: github_actions_author · 2026-08-04T05:55:37Z
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 4, 2026 05:57
64e9dd7 to
21aadaf
Compare
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@tangle-network/agent-core@0.5.0
Minor Changes
b449679: Carry prompt-cache tokens through
readTokenUsageinstead of discarding them.TokenUsageCountsgainscacheReadTokensandcacheWriteTokens, and the threeprompt-side fields are now disjoint and additive:
inputTokensis the freshlybilled tail, and
inputTokens + cacheReadTokens + cacheWriteTokensis the sizeof the prompt the model saw. Two helpers expose that directly —
promptTokens()and
cacheHitRate().Behavior change on an existing field. For OpenAI-compatible payloads,
inputTokenspreviously returned the reportedprompt_tokens, which alreadyincludes the cached share; it now excludes it, so a warm call's
inputTokensdrops to the part actually billed at the input rate. Measured on
router.tangle.tools with
glm-5.2, one append-only turn:prompt_tokens=8656, cached_tokens=8576used to read as 8,656 input tokens andnow reads as 80 input + 8,576 cache-read.
The error flips direction, so callers must be updated, not just re-read. A
caller that prices
inputTokensat the full input rate previously OVERCHARGED awarm call (8,656 × full rate against a true 80 × full + 8,576 × cache rate); it
now UNDERCHARGES, because the 8,576 cache-read tokens are no longer in the field
it prices and it does not yet charge for them anywhere. Correct usage is to
price all three terms:
and to use
promptTokens(usage)— neverinputTokens— wherever the numbermeans "context size".
genAiUsageAttributesemitsgen_ai.usage.cache_read_input_tokensandgen_ai.usage.cache_creation_input_tokensbesidegen_ai.usage.input_tokens,so total prompt volume stays recoverable on the attribute bag rather than being
silently under-reported once
input_tokensnarrows to the billed tail. Both areomitted entirely for a producer that reported no cache information, because a
synthesized
0would read as "measured, no cache".The reader normalizes two provider conventions that reach callers through the
same endpoint — OpenAI-style, where the cached count is inside the reported
prompt total, and Anthropic-style, where it sits beside it — and does not
double-count the router's normalized
prompt_cacheecho of a provider-nativecounter.
Patch Changes
@tangle-network/agent-interface@0.43.1
Patch Changes
682814e: Offer codex
noneand piultracodein the reasoning-effort sets.Both were measured against the pinned CLI binaries and both were reachable all along: the codex API enumerates
nonefirst in its own error, andpi --thinkingacceptsmax, which canonicalultracodemaps to. The picker hid them, so turning thinking off on codex and reaching pi's top rung were not selectable.@tangle-network/agent-provider-cli-bridge@0.3.5
Patch Changes
@tangle-network/agent-provider-computesdk@0.2.37
Patch Changes
@tangle-network/agent-provider-daytona@0.2.37
Patch Changes
@tangle-network/agent-provider-e2b@0.2.37
Patch Changes
@tangle-network/agent-provider-tangle@0.4.11
Patch Changes
@tangle-network/agent-provider-testkit@0.5.3
Patch Changes