Repository navigation
chore: publish new package versions - #4544
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
2 times, most recently
from
June 10, 2026 12:36
cfa5cef to
89e6bf9
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
June 10, 2026 14:24
89e6bf9 to
b8f671e
Compare
balegas
approved these changes
Jun 10, 2026
This branch was previously deployed
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
@electric-ax/agents@0.4.16
Patch Changes
@electric-ax/agents-runtime@0.3.12
Patch Changes
5238055: Show per-response token usage in the agent meta row, e.g.
1.2k ↑ 412 ↓. Updates as each step settles — for a single-turn call this landsonce at done; for tool-using runs the counter jumps at each step
boundary (the LLM SDK only emits
usageat end-of-step, so we can'ttick smoothly between tokens).
Plumbing:
StepValuegains optionalinput_tokens/output_tokenscolumns(Zod + TS). Strictly additive: events recorded before this change
stay valid since both fields are optional, so no migration.
outbound-bridge.ts:onStepEndnow persists thetokenInput/tokenOutputit already received frompi-adapter.ts— previouslythose values were accepted and silently dropped.
EntityTimelineStepItem/IncludesStepsurface the new fields,and the three
.select()blocks that materialize steps includethem.
agent_responsesection gets atokens?: { input?, output? }summed across the run's steps at section-build time, andthe section-cache fingerprint factors in step token deltas so a
late-arriving
onStepEndinvalidates a stale section.916f6cd: agents-mobile: native slash-command composer for the Horton prompt. The in-session and new-session inputs gain slash-command autocomplete, structured
composer_inputpayloads, and inline command/argument highlighting — reaching feature parity with the desktop composer, on a nativeTextInputrather than a WebView. The slash-command grammar and serializer move into@electric-ax/agents-runtime(exported via/client) as the shared source of truth for both surfaces; the desktop composer repoints to them with no behaviour change.a044ede: agents-server, agents-runtime: fix two first-spawn races that prevented writer-side shared-state entities from reaching their first handler run on a fresh tenant.
agents-server:
PUT /_electric/shared-state/<id>now inserts the correspondingshared_state_linksrow synchronously whenever the request carries a validelectric-owner-entityheader and the principal can access the entity. Previously this PUT only ran the authz check; the link row was created later — asynchronously — when the entity's manifest stream event was processed viaapplyManifestEntitySource. The runtime'smkdbwiring schedules the PUT and the preload GET back-to-back, so the GET always raced ahead of the eventually-consistent link insert and returned401 UNAUTHORIZED: Principal is not allowed to read shared stateon every fresh-tenant first wake.agents-runtime:
createChildDb(used by entity observations) now swallowsStream not found/404on initial preload. A handler may legitimately observe an entity that hasn't been spawned yet — e.g. a parent observes its own future child to wake on the child'srunFinished. Treating the 404 as "no events yet" matches the spirit of the observation (we'll be woken when the entity appears); the previous unconditional throw aborted the entire wake withHTTP Error 404 ... Stream not found, and the entity could never recover because the spawn that would create the child never ran.Verified end-to-end with OpenFactory's
daily-digestentity (usesmkdb+observe(db(...))+observe(entity(<future child>))) against a freshly torn-down local agents-server: the firstrun-nownow writes the digest row, the discord-router subscriber picks it up, and the digest reaches Discord — without manual SQL or out-of-band link bootstrapping.@electric-ax/agents-server@0.4.19
Patch Changes
a044ede: agents-server, agents-runtime: fix two first-spawn races that prevented writer-side shared-state entities from reaching their first handler run on a fresh tenant.
agents-server:
PUT /_electric/shared-state/<id>now inserts the correspondingshared_state_linksrow synchronously whenever the request carries a validelectric-owner-entityheader and the principal can access the entity. Previously this PUT only ran the authz check; the link row was created later — asynchronously — when the entity's manifest stream event was processed viaapplyManifestEntitySource. The runtime'smkdbwiring schedules the PUT and the preload GET back-to-back, so the GET always raced ahead of the eventually-consistent link insert and returned401 UNAUTHORIZED: Principal is not allowed to read shared stateon every fresh-tenant first wake.agents-runtime:
createChildDb(used by entity observations) now swallowsStream not found/404on initial preload. A handler may legitimately observe an entity that hasn't been spawned yet — e.g. a parent observes its own future child to wake on the child'srunFinished. Treating the 404 as "no events yet" matches the spirit of the observation (we'll be woken when the entity appears); the previous unconditional throw aborted the entire wake withHTTP Error 404 ... Stream not found, and the entity could never recover because the spawn that would create the child never ran.Verified end-to-end with OpenFactory's
daily-digestentity (usesmkdb+observe(db(...))+observe(entity(<future child>))) against a freshly torn-down local agents-server: the firstrun-nownow writes the digest row, the discord-router subscriber picks it up, and the digest reaches Discord — without manual SQL or out-of-band link bootstrapping.Updated dependencies [5238055]
Updated dependencies [916f6cd]
Updated dependencies [a044ede]
electric-ax@0.2.16
Patch Changes
@core/electric-telemetry@0.3.0
Minor Changes
process_typetelemetry attribute for the coarse buckets that previously hid most of the signal during overload.:erlangand:supervisorare now replaced by a more specific, low-cardinality name (registered name, falling back to the first named$ancestor, then to the initial-call MFA), and logger handler/proxy processes are reported aslogger_olp:<handler_id>instead of a barelogger_olp. This affects thevm.monitor.long_gc,vm.monitor.long_schedule,vm.monitor.long_message_queue,process.memory, andprocess.bin_memoryevents. No separate attribute is added.@electric-ax/example-agents-chat-starter@0.1.7
Patch Changes
@electric-ax/example-agents-walkthrough@0.1.4
Patch Changes
@electric-ax/example-deep-survey@0.1.23
Patch Changes
@electric-ax/agents-desktop@0.1.16
Patch Changes
5238055: Show per-response token usage in the agent meta row, e.g.
1.2k ↑ 412 ↓. Updates as each step settles — for a single-turn call this landsonce at done; for tool-using runs the counter jumps at each step
boundary (the LLM SDK only emits
usageat end-of-step, so we can'ttick smoothly between tokens).
Plumbing:
StepValuegains optionalinput_tokens/output_tokenscolumns(Zod + TS). Strictly additive: events recorded before this change
stay valid since both fields are optional, so no migration.
outbound-bridge.ts:onStepEndnow persists thetokenInput/tokenOutputit already received frompi-adapter.ts— previouslythose values were accepted and silently dropped.
EntityTimelineStepItem/IncludesStepsurface the new fields,and the three
.select()blocks that materialize steps includethem.
agent_responsesection gets atokens?: { input?, output? }summed across the run's steps at section-build time, andthe section-cache fingerprint factors in step token deltas so a
late-arriving
onStepEndinvalidates a stale section.@electric-ax/agents-mobile@0.0.14
Patch Changes
composer_inputpayloads, and inline command/argument highlighting — reaching feature parity with the desktop composer, on a nativeTextInputrather than a WebView. The slash-command grammar and serializer move into@electric-ax/agents-runtime(exported via/client) as the shared source of truth for both surfaces; the desktop composer repoints to them with no behaviour change.@electric-ax/agents-server-ui@0.4.19
Patch Changes
5238055: Show per-response token usage in the agent meta row, e.g.
1.2k ↑ 412 ↓. Updates as each step settles — for a single-turn call this landsonce at done; for tool-using runs the counter jumps at each step
boundary (the LLM SDK only emits
usageat end-of-step, so we can'ttick smoothly between tokens).
Plumbing:
StepValuegains optionalinput_tokens/output_tokenscolumns(Zod + TS). Strictly additive: events recorded before this change
stay valid since both fields are optional, so no migration.
outbound-bridge.ts:onStepEndnow persists thetokenInput/tokenOutputit already received frompi-adapter.ts— previouslythose values were accepted and silently dropped.
EntityTimelineStepItem/IncludesStepsurface the new fields,and the three
.select()blocks that materialize steps includethem.
agent_responsesection gets atokens?: { input?, output? }summed across the run's steps at section-build time, andthe section-cache fingerprint factors in step token deltas so a
late-arriving
onStepEndinvalidates a stale section.916f6cd: agents-mobile: native slash-command composer for the Horton prompt. The in-session and new-session inputs gain slash-command autocomplete, structured
composer_inputpayloads, and inline command/argument highlighting — reaching feature parity with the desktop composer, on a nativeTextInputrather than a WebView. The slash-command grammar and serializer move into@electric-ax/agents-runtime(exported via/client) as the shared source of truth for both surfaces; the desktop composer repoints to them with no behaviour change.Updated dependencies [5238055]
Updated dependencies [916f6cd]
Updated dependencies [a044ede]