1.15.1
Every @aparte/* package ships at this version (they are released in lockstep).
Patch Changes
-
0ff08c9: Reasoning that arrives after its block was closed now opens a new block, instead of growing a block that already reads “Thought for 3s”.
Nothing to change in your code. A reasoning block closes when the answer starts or a tool is called, and only a
turn-startlet the next reasoning open a block of its own. Later reasoning in the same turn was appended to the closed block, folded, above the calls made since, and the block kept its finished label while it grew. It happened to a server loop that sent oneturn-startper run instead of one per model call (apartejs/aparte#272), and as well to a model that reasons again after it starts answering within one call (the engine,ai-sdkand AG-UI all pass that through), in the reply and in a sub-agent’s transcript.The server-loop guide now says what a server writing its own wire must send: a
turn-startbefore each model call, a sub-agent’s with itsagentId.@aparte/core -
350930e: A call in a sub-agent’s conversation under its line now shows its own state: a failed or refused call no longer reads in the success colour, and a reply being written has one caret instead of one per paragraph of the transcript.
Nothing to change in your code. Five rules of the tool row (the success ink of a call that is done, the quiet line’s target face and chevron place, a queued call’s muted name, a running quiet call’s state word under reduced motion) were keyed on the row’s state with a descendant combinator, so they reached every row drawn under it: with
setupSubagents({ details: 'transcript' })a failed call in the transcript of a line that was done read “Failed” in green (apartejs/aparte#271), and a quiet line made the calls under it quiet. They now name the row’s own line; their specificity is unchanged. The streaming caret (setStreamingCaret) had the same reach and blinked after the last paragraph of every text in a transcript; it now stays at the reply’s own words.A browser test now draws every state of a line with a call of every state under it, and compares each call with the same call on its own.
@aparte/core -
4879492: Under React, Vue, Svelte and Angular, a scrolled conversation no longer moves up and down by a pixel while a reply streams reasoning.
Nothing to change in your code. The space kept under a reply (so the question stays at the top) was written as a fraction and, under a wrapper, read back as that fraction against a
scrollHeightthe browser gives in whole pixels. It never settled: on every streamed delta that grew nothing on screen, a closed reasoning block in the reply or in a sub-agent’s transcript, it went 65.6, 66.1, 65.6 px, and the thread, held at the end of its scroll, moved a pixel each way for as long as the reply streamed (apartejs/aparte#270). The space is now whole pixels, so measuring it again with nothing changed gives the same value, in both modes; raw core also loses a one-pixel jump on the second measure.A browser test now reads every frame of a reasoning reply streaming into an already scrolled thread, on every example, at half a pixel.
@aparte/core -
11895b0: Formulas in a sub-agent’s conversation under its line are drawn at their own pace again, instead of waiting on each other.
Nothing to change in your code. A formula still arriving is drawn at most once a frame per reply part, and the part was found as a segment of the reply. A sub-agent’s text is drawn inside a segment of the reply (the line of the call that opened it), so every formula of its conversation, and of sub-agents writing at once, shared one pace: each answered null while another’s turn came. The part is now the nearest segment.
@aparte/plugin-katex
Version-only bumps (no changes of their own): @aparte/engine, @aparte/runner-ag-ui, @aparte/runner-n8n, @aparte/provider-ai-sdk, @aparte/provider-openai-compat, @aparte/provider-scenario, @aparte/provider-transformers, @aparte/plugin-approval, @aparte/plugin-artifacts, @aparte/plugin-ask-user, @aparte/plugin-cards, @aparte/plugin-chartjs, @aparte/plugin-compaction, @aparte/plugin-diff, @aparte/plugin-echarts, @aparte/plugin-marked, @aparte/plugin-mermaid, @aparte/plugin-model-selector, @aparte/plugin-shiki, @aparte/plugin-storage-idb, @aparte/plugin-streaming-markdown, @aparte/plugin-subagents, @aparte/plugin-titler, @aparte/plugin-triggers, @aparte/angular, @aparte/react, @aparte/svelte, @aparte/vue, @aparte/locales, @aparte/docs-mcp.
1.16.0
Every @aparte/* package ships at this version (they are released in lockstep).
Minor Changes
-
4130c3e:
<aparte-conversation-list>can move a conversation to another of your groups: setmoveTargets, and each row’s menu offers “Move to…” and “Remove from “…””, a row can be dragged onto another group, andaparte-conversation-movetells you where.Nothing changes without
moveTargets: the menu and the rows are the ones they were. Set it to the groups a conversation can go to ([{ key, label }], the shape an item’sgroupalready has). “Move to…” lists every target but the row’s own group, in the same menu and walked by its keys; “Remove from “…”” takes a row in a group out of it; a row dragged onto another group (its heading or its rows) moves there, the group marked while a drop would land, and dropped on the rows of no group it leaves its group. Each sendsaparte-conversation-movewith{ id, from, to }(tois a key, ornullfor no group), and the list moves nothing: you write it and assignconversationsagain.managedoes not carry it out, since a group is your data. A target no row is in has no heading to drop on, so the menu reaches it. Under a wrapper,moveTargetsis a prop or input and the event isonConversationMovein React,(conversationMove)in Angular,aparte-conversation-movein Vue and Svelte.Three locale keys, in the nine languages of
@aparte/locales:moveConversation,moveConversationTo,removeFromGroup. The icon provider gainsfolder, which the “Move to…” item draws;folderIconis still exported from@aparte/core/icons.@aparte/core,@aparte/locales
Patch Changes
-
0ad9f5c: A reply, or a sub-agent’s conversation, no longer loses its last words when the server sends no
text-flushbefore the next call or the run’s end.Nothing to change in your code. The stream parser holds a delta that ends on a backtick (or on the start of a block tag) until more arrives, and only
text-flushhanded it over. aparté’s own runner sends one at the end of every model call; a server loop of one’s own may not (apartejs/aparte#275). Then a reply ending on inline code lost it, and was saved that way: “La valeur est42” in one delta showed nothing at all. The text is now handed over at everyturn-startand at the run’s end (done, suspended, stopped), and a sub-agent’s at its own end and at the run’s; after atext-flushthere is nothing left to hand over, so nothing appears twice. The server-loop guide’s wire example closes each call withtext-flush.@aparte/core,@aparte/plugin-subagents -
0448d6f:
<aparte-model-selector>lists the new models when a provider is replaced while it is on screen, instead of an empty list or the old models.Nothing to change in your code. An app that replaces its model catalogue (
unregisterAIProvider(id), thenregisterAIProvider(createModelCatalogue({ id, ... }))with the new models) saw an empty picker: the second change was compared with the list loaded before the first one, taken for no change, and the load the first one had started, which saw no provider, wrote an empty list (apartejs/aparte#276). A change that comes while a load runs now makes that load go round again. And a provider registered again under the same id, a catalogue whose models changed, now reloads the list: the selector compared provider ids only, and kept the old models. A fresh id per catalogue, the workaround, is no longer needed.@aparte/plugin-model-selector
Version-only bumps (no changes of their own): @aparte/engine, @aparte/runner-ag-ui, @aparte/runner-n8n, @aparte/provider-ai-sdk, @aparte/provider-openai-compat, @aparte/provider-scenario, @aparte/provider-transformers, @aparte/plugin-approval, @aparte/plugin-artifacts, @aparte/plugin-ask-user, @aparte/plugin-cards, @aparte/plugin-chartjs, @aparte/plugin-compaction, @aparte/plugin-diff, @aparte/plugin-echarts, @aparte/plugin-katex, @aparte/plugin-marked, @aparte/plugin-mermaid, @aparte/plugin-shiki, @aparte/plugin-storage-idb, @aparte/plugin-streaming-markdown, @aparte/plugin-titler, @aparte/plugin-triggers, @aparte/angular, @aparte/react, @aparte/svelte, @aparte/vue, @aparte/docs-mcp.
1.17.0 Latest
Every @aparte/* package ships at this version (they are released in lockstep).
Minor Changes
-
3a59a20: A message the server refuses for its size (HTTP 413) now reads “This message is too large to send. Remove a file or send a shorter one.” instead of promising a retry, and is left out of later requests.
AparteError.codeForStatushad no case for 413, so the error fell back to a failing provider: “Try again in a moment”, and a retry sends the same bytes. It is easy to hit: nginx refuses a body over 1 MB by default, PHP one over 8 MB, and an image travels in base64. It has its own code now,USAGE_TOO_LARGE, its own sentence,errorTooLarge, in the nine languages of@aparte/locales, and it joins the codes whose message is left out of every later request: a long pasted text refused for its size no longer goes out again with the next message and takes it down too. (apartejs/aparte#294)@aparte/core,@aparte/locales -
118707f: A sub-agent opened by another sub-agent, saved while it waited for an approval, now goes on on its own line in its parent’s transcript when the reply is resumed after a reload.
Its saved line was looked for in the reply’s own segments only, so its resumed work was dropped, or went to a second, top-level line, and its call stayed awaiting approval. The plugin now finds it at any depth and takes up the sub-agents it sits under first.
createSegmentListgains apausedoption for that: a saved list taken up as a pause keeps its calls waiting for an approval open, where history aborts them.@aparte/core,@aparte/plugin-subagents -
6d1f934: A conversation row can say its turn is queued:
setConversationStatus(id, 'queued')(oraparte-conversation-statuswithstatus: 'queued') draws a muted mark, no shimmer, and “Queued” for a screen reader.For a turn sent but waiting behind another conversation’s: a local engine that serves one turn at a time, a backend’s queue. Read as
running, the row shimmered and said “Answering” while nothing was being written. Only the app knows a turn is queued, so the app says it, and saysrunningonce the turn is served; the conversation controller’srunningat the turn’s start no longer takes aqueuedback.AparteConversationStatusgains'queued': a host that matched every status exhaustively has one more to handle. The new locale keyconversationQueuedis translated in the nine languages of@aparte/locales. (apartejs/aparte#289)@aparte/core,@aparte/locales -
608fb2c: A conversation can be dragged from one
<aparte-conversation-list>onto another: give each list the key of the group it stands for indrop-key(dropKey). The drag type is public:APARTE_CONVERSATION_DRAG_TYPE.For an app that renders one
flatlist per project under headings of its own. A list’s rows with nogroupare in its key’s group, a row dropped on it moves there, from another list of the page or from an element of the app’s own that carries the type, and a row dropped back on its own list moves nothing. A list with no rows still takes a drop. The move is the sameaparte-conversation-move, sent by the list the row lands on,fromthe key of the list it came from. Withoutdrop-key, nothing changes. (apartejs/aparte#278)@aparte/core,@aparte/angular,@aparte/react,@aparte/svelte,@aparte/vue -
6db770f: A step can say what it is about:
step-startcarries adetail, a newstep-update { name, detail }changes it while the step stays open, and the step’s label function is handeddetailand the reply’smessageId.A server waiting for a slot of a local engine knows who holds it, and the words belong to the page. A step carried its name alone and its label saw only that: an app kept the last holder in a module of its own, ended and restarted the step to have the words asked again, and two chats waiting showed the last one told. The detail travels with the step to the reply’s waiting indicator and to a sub-agent’s line, and the label is asked again when it changes. A second
step-startof the same name still opens a nested step, as AG-UI’s rule says: update a step withstep-update. (apartejs/aparte#288)@aparte/core,@aparte/engine,@aparte/plugin-subagents -
6d5eab5: A sub-agent heard before it names the call that opened it (an AG-UI agent whose first event arrives before
SUBAGENT_STARTED) now moves onto that call: one line with all it said, and nothing marked Stopped.It got a line of its own first, as a sub-agent with no call does. Announced again with its call, it was taken for another sub-agent under the same id: the first line read Stopped and what it said was split across two lines.
createSegmentListgainsremoveSegment, so a sub-agent’s own transcript can take a line out as a reply can.@aparte/core,@aparte/plugin-subagents -
85ea6eb: New
showToast(text, { tone, timeout, target })in the kit: a short message in a corner of the page that goes away on its own.For what has nowhere else to be said, such as why an action did not happen. It is the kit’s alert, stacked in a fixed corner that never moves the layout under the pointer. It is announced as a status, or as an alert in the
dangertone, waits while it is hovered or holds the focus, and closes by its button or Escape, giving the focus back to where it came from. Shown while a modal dialog is open, it goes inside the dialog, since everything outside one is inert; for a design system’s dialog drawn in its own shadow root, it goes in the page’s own content the dialog shows, where the kit’s stylesheet reaches it.targetnames the element it is about: the toast goes in that element’s shadow root and wears its theme. It returns a handle withclose(), and does nothing in a server render. Two locale keys name its region and its button (notifications,dismissNotification), in the nine languages. (apartejs/aparte#279)@aparte/core,@aparte/locales -
dd2fce8: A tool can set its own time limit (
timeoutMson the tool), which replaces the client’s or the server handler’stoolTimeoutMsfor that tool;Infinitymeans no limit.A tool that runs a whole sub-agent on a slow local model, or a command with a limit of its own, was cut at five minutes like a lookup, and a host that raised the shared bound to spare it lost the bound for every other tool.
Infinity, or any delay above 2^31-1 ms, used to fire at once (a timer reads such a delay as zero): it is no limit now. A sub-agent a call opens in the background is bounded by that call’s limit. The docs now say what happens when a limit fires: the call is abandoned and the run stops, since a handler that ignores its signal may still be running. (apartejs/aparte#290)@aparte/core,@aparte/engine -
6075c93: An approval policy can rule asynchronously:
setApprovalPolicyand the server handler’sapprovalPolicymay return a promise, awaited before the call runs, pauses or is refused.Security fix included: a policy that returned a promise used to let every call run unasked in the page (the promise was taken for a ruling with no verdict, so the gate opened,
needsApprovaltools included), and was ignored on the server, where adenyon a tool with no flag let the call run. While a policy rules, the calls the model made after that one wait, as they wait for a person’s answer, so the order guarantee holds; a synchronous policy stays synchronous. A promise that rejects asks a person, with the reason on the console. A policy is asked once per call, so the ruling that paused a call is the one that answers it, and a Stop does not wait for a ruling still on its way.config.ruleOnToolCallstays synchronous and answersaskfor a policy still ruling; the newconfig.ruleOnToolCallAsyncwaits for it. The engine’sneedsApprovalpredicate may answer with a promise too. (apartejs/aparte#291)Code that CALLS a policy (one that wraps
config.getApprovalPolicy()to compose two) now gets a type whose answer may be a promise: await it, or askconfig.ruleOnToolCallAsync. A policy you write is unaffected, andcreateApprovalPolicyfrom@aparte/plugin-approvalis still typed as ruling at once.@aparte/core,@aparte/engine -
2ba627d:
new AparteConversationManager(adapter, { orderBy })orders its lists as the app chooses:'updated'(the default, unchanged),'created', or a compare function.The lists were by
updatedAt, the last change of content: a reply that ends moves its conversation up, as most chat products do. An app that keeps a conversation in its place, or orders by the person’s last message, sorted the manager’s lists again itself. A conversation list’s date groups still read each row’supdatedAt: with another order, hand it the date you order by. Opening, renaming or reloading a conversation never moved it, and still does not. The framework helpers’ lists (useConversationManagerin React and Vue, Angular’sConversationManagerService, Svelte’screateConversationManagerandcreateConversations) follow the same option, given to theirinit;manager.compare(a, b)sorts a list of the app’s own the same way. (apartejs/aparte#293)@aparte/core,@aparte/angular,@aparte/react,@aparte/svelte,@aparte/vue -
8783037: A sub-agent whose own run stops before it answers (its turn limit, a call it could not make) now ends
partial, with areasonand what it found as itsresult, and its line reads “Cut short” instead of Done.runSubAgentreported every such sub-agent asdonewith its last text, often empty after a round of tool calls, so the parent model read a finished answer and the line said Done above a transcript showing the turn limit’s error.StreamAgentStatusandAparteSubagentStatusgain'partial',agent-endgainsreason(aStreamAgentCutReason:turn-limit,timeout,no-handler,no-resolver,abortedfor a call that stopped itself, orcontextfor a host’s own loop),runSubAgentreturns them, and a background sub-agent cut short is reported to the model as such.aparte-subagent-endcarries thereasontoo. A host that matched every status exhaustively has one more to handle. (apartejs/aparte#285)@aparte/engine,@aparte/plugin-subagents -
1f24530: A sub-agent can name the model it runs on:
agent-startcarriesmodel,runSubAgentandstartSubAgentfill it from their request (or take amodelyou give), andsetupSubagents({ model: true })draws it quietly on the sub-agent’s line.A host whose sub-agents run on other models than the conversation (a small local one beside the main) had only the name to show it, “Reader · qwen3:8b”, which a host matching lines by name then had to strip. The model is kept on the segment, so a thread read back still says it. Off by default: every existing line would change.
aparte-subagent-startcarries it too, asmodel. (apartejs/aparte#286)@aparte/engine,@aparte/plugin-subagents
Patch Changes
-
e1685e0: Escape and Tab typed in a field of a web component inside a modal dialog are the dialog’s again: an open drawer or the launcher no longer takes them.
The drawer and the launcher leave a modal dialog’s keys to it, and looked for the dialog around where the key began with
closest(), which stops at the edge of the component’s own shadow root: the drawer closed, or the launcher hid the chat, on the dialog’s Escape. They now look along the key’s whole path.@aparte/core -
aee4d0c: A dialog opener or closer made of a web component (a Shoelace or Material button, or a button holding an icon component) opens and closes its dialog again.
Since the dialog wiring learned to work inside an app’s shadow root, it read the click from where it began and looked for the control with
closest(), which stops at the edge of the shadow root it starts in: a click on the label or the icon of a component button, each in the component’s own shadow root, found no opener. The control is now looked for along the click’s whole path, across every shadow root it crossed.@aparte/core -
3c2d7e3: In Safari, dragging text or a link out of the transcript no longer leaves the chat unable to follow the next reply to the bottom.
The transcript holds a press from
pointerdownto the nextpointeruporpointercancel, and WebKit sends neither after a native drag. The press stayed held for the rest of the turn, and the engine’s own settle at the end of a reply read as the reader scrolling up, which stopped the follow. A drag now ends the press, as it already does in the conversation list.@aparte/core -
adeaffe: A key that leaves
<AparteUi>’spropsis now cleared on the element: its attribute or CSS variable is removed, and its property is set toundefined.With the usual
{ ...(fetching && { loading: true }) }, the next bag has noloadingonce fetching ends, and only the keys present were written, so the attribute stayed and the skeleton rows never went away, in all four wrappers.applyElementPropstakes{ replace: true }for a bag that is the element’s whole set of props; without it, as the generated components call it with only what changed, an absent key is left alone.@aparte/core,@aparte/angular,@aparte/react,@aparte/svelte,@aparte/vue -
6962a28: A reply cut by an error keeps its last words: the text the parser was holding (the end of a code block, a closing backtick) is no longer lost.
The engine flushes the call’s text before it throws, and the client flushes on its error path too, for a runner of your own that does not.
@aparte/core,@aparte/engine -
5ed682c: A reply streamed by hand through a framework chat (
appendToSegmentin a loop) is written incrementally again, chunk by chunk, untilisStreaming: falseends it.Since 1.16’s fix for edited replies, a segment with no
isStreamingflag followed the bubble’sstreamingattribute, and every wrapper drops that attribute as soon as a reply driven by hand has a segment. Each chunk, and each frame’s re-sync, then closed the stream and drew the whole text again: an unclosed**showed raw, and a highlighter, a diagram or a formula ran once per token. An append is now a stream whatever the attribute says, and a stream already open goes on until a flag ends it. A bubble withstreaming="false"now reads as not streaming, as the bubble itself reads that value, so an edit of its finished reply is written whole.@aparte/core -
a6ed3a6: Under React, Vue, Svelte or Angular, a reply you write by hand into an empty assistant message now streams until you give it a status, as it already did without a framework: end it with
updateMessage(id, { status: 'completed' }).The bring-your-own-loop flow (
appendMessagewith no status,addSegment,appendToSegment, then a status) lost its stream as soon as the first segment arrived when the empty bubble had been painted first, which any real wait before the first token causes: a wrapper draws a bubble’sstreamingfromisAwaitingReply, which a segment turns false, and the bubble took that for the reply’s end. Every chunk after it was drawn whole, an unclosed**showed raw, and a reasoning block read finished while it was still being written. The host now marks such a shellstreamingwhen its first segment is written, and the status the app gives it ends it. A reply that already had words when a segment was added keeps the status the app gave it.@aparte/core -
2ce599e: A Stop pressed just as the reply ends no longer sends the message the person had drafted for later.
The reply could end between the press and the release: the same button turned back into Send, and the click sent the unfinished draft. A click now does what the button showed when it was pressed, so a Stop with nothing left to stop does nothing. The keyboard already refused it, since Enter neither sends nor stops during a turn.
@aparte/core -
de4b389: A modal dialog placed inside
<aparte-sidebar>keeps its Escape and Tab while the sidebar is a drawer: the drawer no longer closes behind it.A settings dialog put beside its button in the sidebar was taken for the drawer’s own content. Its Escape closed the drawer, which then made itself inert with the open modal inside it, so the page could not be used until a second Escape; Tab from the dialog’s last button went nowhere. A modal dialog anywhere on the key’s path now has the key, as one outside the sidebar already did.
@aparte/core -
a96cbe2: After a reload, resuming a reply paused on a sub-agent’s call no longer tells the model the call that opened the sub-agent was stopped.
@aparte/plugin-subagentsmarks that callawaiting-approvalwhile the sub-agent’s question is up. Loading the reply turned it intoaborted, so the resume answered it “The tool call was stopped before it ran.” for a delegation whose sub-agent was about to go on, and its line read Stopped. In a reply paused ondeferredCallsno gate of the page is open, so a waiting call is kept open and the resume hands it back open.@aparte/core -
41bcabe: A property input given
undefined,nullorfalsenow clears the element’s property:[moveTargets]="canMove ? groups : undefined"in Angular, or a key kept in an<AparteUi>bag with no value (moveTargets: canMove && groups).Only the attribute of the same name was removed, and the element went on with the old array or function: rows kept offering “Move to…”, an old
renderMetakept drawing. A key given an object or a function before is a property, and is cleared as one.@aparte/core,@aparte/angular,@aparte/react,@aparte/svelte,@aparte/vue -
c510994: A property given to an element before its definition loads (a lazily imported plugin’s
diff,comments,chat,triggers) now reaches the element once it is defined.<AparteUi>and the wrappers’ generated elements assigned it right away, so it became the element’s own property and hid the setter the definition brought, for good, although the docs promise a tag mounted before its definition upgrades on its own. The value is now kept and handed to the setter when the element is defined.@aparte/core -
a642064: Clicking a scroll-rail tick in a chat embedded in a scrolling page now scrolls only the transcript, not the page around it.
The jump used
scrollIntoView, which aligns the message in every scrolling ancestor, the page included. In a dashboard panel or on a docs page, each tick moved the whole page and pushed the chat’s own header out of view. The transcript’s surface is now scrolled by the distance to the message.@aparte/core -
27bd996: A framework chat’s re-sync now carries every field a segment changed, a text segment’s included, and a change the app wrote in place on the segment it handed over.
A reasoning block’s label, a code block’s language, an error’s details reached the bubble only when the segment was drawn anew: for a segment with text, only the text was patched. And a field written in place (
seg.status = 'resolved', idiomatic in Svelte and Vue) was compared with the bubble’s copy, which is the same object, so a resolved call kept reading as running. Each re-sync now compares with what was last handed over.@aparte/core -
53b3347: Renaming a conversation with an input method (Japanese, Chinese, Korean) no longer commits or cancels the rename on the Enter or Escape meant for the word being composed.
Enter confirms a candidate and Escape cancels a composition. Firefox sends them flagged
isComposing, and Safari sends that Enter after the composition with keyCode 229. The list took both for its own: the title was saved half converted, in the middle of the word, or the rename was thrown away.@aparte/core -
c44971e: In controlled mode (
messagesandonMessagesChange), a tool call’s new status or result, a card’s new data, and any other segment without text now show when the parent hands the message again.When the message kept the same number of segments, the wrappers’ re-sync patched only segments carrying
content: a call the parent marked resolved kept spinning “Running”, and a segment replaced under another id was ignored. The fields a segment changed are now patched, and a replaced segment draws the bubble again.@aparte/core -
628e1ce: An open
<aparte-select>(the model selector, the approval mode) now answers only the keys typed in it, and Tab closes it.It listened on the whole document: open, it took Enter, the arrows and Escape typed anywhere. Tab back to the composer left it open, and Enter there sent the message, then also switched the model. Its Escape also came after every listener on the way up, so inside a launcher the whole chat closed on the Escape meant to dismiss the list.
@aparte/core -
aa39bb9: The server handler keeps a failed sub-agent’s error text on the server: the page reads “The sub-agent failed.”, and the real message goes to the server’s log.
A sub-agent that failed on a server tool’s error (a path, a connection string) or on its model’s (a vendor message that can echo a key) ended with that text in
agent-end’serror, which went out as it was: the page drew it on the sub-agent’s line and the conversation saved it. A tool’s own failure was already masked this way; the sub-agent’s end now is too.@aparte/core -
1174c83: A tap on a kit menu item (a row’s Rename, Pin, Delete) now keeps the menu open until the tap’s click lands.
The menu closes when the focus leaves for nowhere unless a press inside it is under way, and that press ended at
pointerup. On a touch screen the tap’s click comes after the finger is lifted, and on iOS so does the compatibilitymousedown, which blurs the focused item: the menu could close before the click reached the item. A touch press now lasts until its click, or 600 ms if none comes. iOS’s event order was not measured here; the change leaves mouse presses as they were.@aparte/core -
cfef2ed: A tap on a conversation row while the app updates the list now selects that row.
The list holds the app’s render during a press so a row is not replaced under it, and lifted the hold one task after
pointerup, where a mouse click already landed. A tap’s click comes later, so the held render could replace the row under the finger first. A touch press now holds the render until its click, or 600 ms if none comes.@aparte/core -
da08615: Setting
valueon<aparte-select>from code no longer firesaparte-select-change; only a choice the person makes does. If you relied on the event after settingvalueyourself, run your handler there.The attribute set the value silently and the property announced it, so the same app echoed under Vue, Svelte 5 and a raw tag (which write the property) and not under React’s element or Angular’s directive (which write the attribute): a value loaded from a saved conversation came back as a change, and a handler saving the person’s choice saved one nobody made. Both paths now behave as a native
<select>.<aparte-approval-mode>relays only that event, so a mode set by code (getApprovalController().setMode(...)on a switch of conversation) no longer comes out asaparte-approval-mode-changeeither. (apartejs/aparte#295)@aparte/core -
7e83934: Enter or Space on the Send button sends again after a press on Stop that never became a click (the pointer slid off before the release, or a touch turned into a scroll).
The button remembers what it showed when it was pressed, so a Stop released just after the reply ended does not send the draft. That record outlived a press that produced no click, and the next activation from the keyboard was read as that Stop: the draft was not sent until a second press. The record now only counts for a click a press produced.
@aparte/core -
c3eb2f9: Editing a finished reply in place (
updateSegmentwith new text) now draws the whole text, its last characters included.A segment with no
isStreamingflag (every restored one) was read as still being written on update: the incremental parser wrote it and held back its tail, and nothing ended it since the bubble never streamed. A missing flag now follows the bubble: still writing while it streams, finished when it does not.@aparte/core -
bd46542: An Escape that cancels a word being composed with an input method (Japanese, Chinese, Korean) no longer closes a diff comment or a message edit, and no longer drops what is being written.
The diff’s comment field took every Escape as its own and let go of the form. The bubble’s inline edit checked
isComposing, which Safari does not set on the key it sends after a composition ends (keyCode 229). Both now leave a composition’s keys to the composition, as the composer, the rename and the select already do.@aparte/core,@aparte/plugin-diff -
e513b1f: The kit’s dialog attributes (
data-aparte-dialog-open,data-aparte-dialog-close, the backdrop click) now work inside an app’s own shadow root.A click from a shadow root reaches the document with the shadow host as its target, so the opener and the closer were never found, and the dialog was looked up in the document, where it is not. The click is now read where it began, and the dialog is found in the opener’s own root.
@aparte/core -
ed45742: Enter opens a closed
<aparte-select>from the keyboard, and ArrowDown opens it on the selected option; neither chooses anything on the way.The keydown that opened the list went on up to the select’s own key handler, which found the list open with the selection active: Enter chose it again and closed the list at once, firing
aparte-select-changewith the same value, and ArrowDown moved one past it. Only Space opened a select. Also, an Escape typed while the focus is on the page, the list open inside a drawer, now closes the list and leaves the drawer open: the select hears that key before any listener on the page.@aparte/core -
8d2b64a: Resizing the window or the chat no longer raises “ResizeObserver loop completed with undelivered notifications” from the composer.
The editor set its own height inside the observer that watches it, so each width change (a window resize, the launcher maximized, the drawer toggled) ended in that browser error, which monitors log for every user and dev servers show full screen. The height is now set on the next frame, and only when the width changed.
@aparte/core -
b4f313a: Removing an attachment from the keyboard now leaves the focus on the next file’s remove button, or in the editor when none is left, instead of on the page.
The strip is drawn again whole on every change, so the focused remove button was destroyed and the next Tab started again at the top of the page. A file added while a remove button has the focus keeps it on that file.
@aparte/core -
523ceef: In a right-to-left chat, a tool row’s opened detail and a reasoning block now put their indent beside their rule, on the right.
Their rule is
border-inline-start, the right edge in a right-to-left chat, but the indent came from physical shorthands that set the left padding, so the Input/Output panels and the reasoning text sat flush against the rule with an empty strip on the other side. The rename field in the conversation list had the same mismatch. All four now use logical properties.@aparte/core -
3fbaf76: In a right-to-left chat, a reasoning block written in English keeps its indent beside its rail, and the compact weather card and the link chip pad the right side.
The reasoning panel reads its own direction (
dir="auto"), so English reasoning in an Arabic chat put its indent on the left while the rail, which follows the chat, is on the right. When the two directions differ, the indent now goes on the rail’s side. The weather card’s extra space for its accent bar and the link chip’s tighter icon side were physical paddings: they are logical now.@aparte/core,@aparte/plugin-cards -
1902a42: Text a model writes after a tool call, in the same model call, now appears after the call’s row instead of being appended to the text above it.
The adapter hands over the text before a call, as it already did around an activity and as the AG-UI and n8n runners do. Seen with
@aparte/provider-scenarioand with Gemini through the AI SDK.@aparte/core -
c7334d0: The open sidebar drawer now leaves Tab and Escape to a modal dialog opened above it, and to a word being composed in its search field.
A dialog opened from the drawer (the kit’s
data-aparte-dialog-openpattern) had Tab pulled back into the drawer it covers, so Tab did nothing, and Escape closed the drawer behind the dialog. The Escape that cancels an IME composition in the drawer’s search field closed the whole drawer.@aparte/core -
edce799: Pressing the scroll-to-bottom button from the keyboard now moves the focus to the transcript as the button hides, instead of leaving it on a hidden control.
At the bottom the button turns transparent, leaves the tab order and is marked
aria-hidden, but it kept the focus. A screen reader was left on a node removed from the tree, a keyboard user had no focus ring, and Space kept pressing a control nobody could see.@aparte/core -
33e80e4: Two tool calls of one reply now keep two rows, even when a later model call repeats an earlier call’s id.
A vendor that sends no call ids has them minted per stream (openai-compat), and a server that numbers ids per response repeats them: the second call’s result was written onto the first call’s row, the second row stayed pending, and the next request filed both answers under one id. A repeated id is now renamed for the whole reply (
aparte-call-1_2), the calls a resumed run made before its pause included. An earlier reply’s ids are left alone. The suffix is_, not#: Anthropic takes only[a-zA-Z0-9_-]in a call id, and a history replayed to it after a change of model must not carry a#.@aparte/engine -
c4b8933: Two tool calls a server sends at the same
indexwith different ids are now two calls, each with its own arguments.A server that numbers
indexper chunk rather than per response sends every call at index 0 (Ollama’s /v1 has been seen to). The second call was taken for the rest of the first: one call, run with the second’s name on{}, and the first lost. A named delta with a new id now opens its own call when the index is held by a call with another vendor id. A call opened by index whose real id arrives later is still one call.@aparte/provider-openai-compat -
8ed00af: A scenario whose reply delegates twice under the same
id, in two turns, now runs the second sub-agent too.The loop names a call once per reply, so the second turn’s call is
id_2. The scenario filed its scripts per turn, the second one underid, and its handler, asked forid_2, answered “No script exists for this call”. The scripts are now named by the same rule as the loop’s, seeded with the calls already in the reply.@aparte/provider-scenario -
a4a4a07: A scripted sub-agent cut short is reported to the parent model as cut short, with what it found.
The delegate tool’s report knew only
doneandfailed: a sub-agent that endedpartial(its turn limit, a call it could not make) read “was stopped before it answered” and its text was dropped, while its line said Cut short.@aparte/provider-scenario -
84b6aee:
createApprovalPolicyis typed as ruling at once, sopolicy(call)?.verdictreads without an await.A core approval policy may now answer with a promise (apartejs/aparte#291), and the factory’s return type used to be that wider policy type, so reading the mode’s ruling by hand stopped typechecking. The policy it builds never was asynchronous; its type now says so, and it is still accepted by
setApprovalPolicy.@aparte/plugin-approval -
74ba274: An Escape that ends an IME composition in a field inside
<aparte-subagent-view closable>or<aparte-artifact-panel>no longer closes the pane.A Japanese or Chinese reader cancelling a conversion candidate in a field inside the pane (a diff comment, say) folded it mid-composition: the field now leaves that Escape to the composition, and the pane read it as its own.
@aparte/plugin-artifacts,@aparte/plugin-subagents -
5aafbdc: A sub-agent announced with no call, under the id of one that already finished, now gets its own line instead of writing over the finished one’s.
A backend that mints sub-agent ids per run (the engine’s default counter) names a resume’s first detached sub-agent like the paused run’s. A finished sub-agent never resumes, so its id announced again is a new one; only one left waiting or running goes on.
@aparte/plugin-subagents -
89fa900: A nested sub-agent’s conversation now shows both in the chat and in a view of its parent beside it, instead of moving between the two.
With
details: 'transcript', the nested sub-agent’s line is drawn inside its parent’s transcript in the chat, and again in the view where the parent is opened. Both rows got the one element kept for that sub-agent, so each update moved it into the row that asked, and one of the two was always empty while it wrote. A view of its own now keeps its own elements.@aparte/plugin-subagents -
e93fd76: Changing the language, the icons or a tool while a sub-agent is open in a view no longer empties the nested sub-agent’s conversation in the chat.
The view relabelled its rows outside its drawing, with no surface: a nested sub-agent’s row in the view asked for the chat’s element of that conversation, and moved it into the view. The chat’s row stayed empty until it was drawn again, which after the run’s end may never come. Every pass over a view’s rows now runs on that view’s surface, a line’s detail on the surface it sits in.
@aparte/plugin-subagents -
1e5b147: After a reload, the call that opened a sub-agent reads as working again once the sub-agent’s question is answered, instead of staying “awaiting approval”.
While a sub-agent asks, the plugin marks the call that opened it as waiting and gives it back its progress once the question is answered. A lane taken up after a reload did not know the mark was its own, and left it.
@aparte/plugin-subagents -
8963bfe: A sub-agent saved while it waited now goes on, on its own line, when the reply is resumed after a reload, whether the resumed stream announces it again or not.
After a reload the plugin knew no lane. Events for a sub-agent the resumed stream did not announce again were held until an announcement that never came, then dropped: the transcript kept a call that ran as waiting, then Stopped. Announced again with no call, the sub-agent got a second, empty line. The saved line is now found by the sub-agent’s id, on its call or on a segment of its own, while it was waiting or working.
@aparte/plugin-subagents -
28327d1: A view disconnected from its chat, or shown a new conversation, follows the sub-agent it is named again, on whatever call it runs.
connectSubagentViewkeeps a view on the call of the line pressed, since two sub-agents of one reply can share an id. That filter outlived the connection and the conversation: a sub-agent named on the view afterwards, on another call, was never drawn live.@aparte/plugin-subagents -
a76de60: Open on the second of two sub-agents that share an id and have no call now shows that second one, and only its line reads as shown.
Since each such sub-agent has a line of its own, the view still told sub-agents apart by the call of the line pressed, and these lines have none: Open showed the first, and both lines were marked current. A line of its own is now told apart by its own segment.
@aparte/plugin-subagents -
4a838b8: Open on a sub-agent’s line now shows that sub-agent in the view, even when another sub-agent of the reply has the same id.
A backend that mints sub-agent ids per run names a resume’s first one like the paused run’s. The view took the first sub-agent under that id, drew the other’s writes over it while it ran, and both lines read as the one shown.
connectSubagentViewnow hands the view the call of the line pressed, and only that line is marked.@aparte/plugin-subagents -
6d54761: A mention list asked of a function now loads while the app re-renders, instead of never arriving during a streaming reply.
A wrapper writes
triggerson every render, with a new array, and a chat re-renders on every token. Each write aborted the request and armed the debounce again. The same search, asked of a function, is no longer asked again.@aparte/plugin-triggers -
5ca9066: A trigger source handed anew while its list is open (a memoized declaration recomputed for another channel) is asked again, once the declarations stop changing.
Since the fix that keeps a list arriving while the app re-renders on every token, a new function for the same search was never asked: the first channel’s members stayed listed, and Enter inserted one of them. The answer on its way still arrives while the app re-renders, however slowly it re-renders and however slow the source is: a re-ask never aborts it, and the newest source is asked once that answer is in.
@aparte/plugin-triggers -
6d54761: Enter while a new search is loading now chooses a row that matches what is typed, never one left from the search before.
With a list asked of a function, the rows on screen stayed the previous search’s until the new answer arrived: “@car” and Enter took Alice, the row active for ”@”. Until the answer arrives, only the rows that still match stay.
@aparte/plugin-triggers -
9f95728: In Angular, an unset binding of an input that is on by default (
[elicitation],[submitOnEnter], a launcher’s[header], a file picker’s[multiple]) now keeps it on, as in React, Vue and Svelte.Angular’s
booleanAttribute(undefined)is false, so binding a field that is not always set turned the default off: no question presenter (every call needing approval aborted with nothing to click), Enter inserted a newline instead of sending, the launcher lost its header, and the picker took one file.undefinedandnullnow leave the element on its own default.@aparte/angular -
bd02072: A plugin component mounted before its element is defined (the spec imported at once, the element’s module loaded later) now hands its properties to the element once it is defined.
The generated component assigned each property straight onto the element. Before the upgrade, that made it the element’s own property, which hid the setter the definition brought, for good: the element rendered empty. It is held until the tag is defined, as core already does for
<AparteUi>.@aparte/react -
7633cb9: Calling the conversation helper’s
init()again while the first one is still loading no longer ends with the first manager registered on the config.With a slow store (a remote one with a long history) and an account switch, the first
init()resolved after the second and registered its manager last, so the chat persisted into the store of the account just left. A supersededinit()now registers nothing. Angular’s service already read its current manager and kept the newer one.@aparte/react,@aparte/svelte,@aparte/vue
Version-only bumps (no changes of their own): @aparte/runner-ag-ui, @aparte/runner-n8n, @aparte/provider-ai-sdk, @aparte/provider-transformers, @aparte/plugin-ask-user, @aparte/plugin-chartjs, @aparte/plugin-compaction, @aparte/plugin-echarts, @aparte/plugin-katex, @aparte/plugin-marked, @aparte/plugin-mermaid, @aparte/plugin-model-selector, @aparte/plugin-shiki, @aparte/plugin-storage-idb, @aparte/plugin-streaming-markdown, @aparte/plugin-titler, @aparte/docs-mcp.