init.luau
Versions
Every version of this package its world published, newest first by when it first appeared. A version published again later keeps its place.
dotbot panel: a row the drawing stamp kept is the subtree it was again. View.palette() returns one table while the editor's palette is one table (it laid DotBot's look over a fresh copy on every call, so every stamp holding the palette read as changed and every transcript row and agent card was drawn again on every render); a row's work-card slice is kept while its nodes and its place in the card are unchanged; and the Agents heading states no usage for agents that have used nothing (zero#23134). plugin.wasm and plugin.yaml unchanged
01M6KZZ05FADZZ06AYB5R9STNJ0879e7de63Browse filesCompare with previousCompare from hereMerge the pinned DotBot chain (dotbot19849-pin, through OrigoZero/DotBot#792) into main, which holds the panel restyle (world PR #1). The panel keeps main's restyle and gains the chain's community setting and composer attachments; the README carries both. plugin.wasm is left out of this commit only because the merge check reads a wasm's bytes as conflict markers; the next commit adds the build of DotBot main 78df2495 --- dotbot: plugin.wasm built from DotBot main 78df2495 (OrigoZero/DotBot#791, which holds #792 and #781; wasm32-wasip2 release, sha256 fc5e1b2a73a5bec5892543b8d2647b2d9c3a96d7d044f1a10f9b19f684a698d8, 52338364 bytes): a ChatGPT reply's reasoning is kept and sent back on the next request (DotBot#759), and start_agents can give each agent a model and an effort of its own. On the merge above; plugin.yaml and the panel unchanged by this commit
01M6JVSTTRR1RJG4SHFDTJY9SK48721d35b4Browse filesCompare with previousCompare from heredotbot: the composer takes files: the attach button, Ctrl+V of an image and a drop on the panel attach through one path, a thumbnail or name beside the input, removable, sent with the next turn (zero#19620, zero#22096, on dotbot21911-pin)
01M68YFV99H3DDAEQNCHJ6XSAN93c8655e8fBrowse filesCompare with previousCompare from hereDotBot panel: each turn's usage line stays with its turn, a compact footer, resizable agents, and DotBot's own look - view.mergeRows: a live row the stored history does not hold (a turn's usage line) is drawn after the stored row it followed, not after the whole history, so the lines no longer stack above each new message. - Agents: one line per agent (dot, state, name, what it is doing, time, stop, open), opened to its task, usage and pictures on a press; the section is about three agents tall and resizable by dragging its top edge; the agents' total usage sits on its heading. - Composer footer: one line (context against the window, the bar with its handle, an info button whose hover, or press, shows where it compacts and what the last turn and conversation used). - Transcript: a turn's thinking and tool calls drawn as one rounded card; tool calls as a dot, name and what they were called on; usage line names the payer only when it changes. - Look: View.palette() lays DotBot's colours and radii over the editor's palette; JetBrains Mono for code, tool names and figures. - dotbotPanelPreview.module: draws this world's panel over a fake plugin with example data, to see a change before it is published. - dotbotPanel.testSuite: mergeRows regression cases, tested against this world's view.module. - READMEs for the plugin, the panel, view and transcript brought up to date. --- World settings: bind with no startup scene This world holds plugins and no scenes, and had no .world_settings of its own. An engine seeds one from its default template, whose startup_scene is scenes.main; that ref resolves to nothing here, and the engine refuses every push from the world while it does. Cleared, the world binds with no scene, which is what a plugin world needs.
01M5NJMMSWACM1A65NS5K16GEV8e0a17057eBrowse filesCompare with previousCompare from heredotbot: the open panel shows the message a turn started elsewhere answers (zero #19466): a turn the panel did not start (a run the engine starts with a prompt, the page's agent_prompt, the engine waking the agent) shows its message as it starts, above what the turn says, once, in that turn's conversation, which the panel moves to, letting go of the rows of the conversation it showed; an engine delivery reads as the engine's row; Source.messageRows. plugin.wasm built from DotBot main 539f9e5f (OrigoZero/DotBot#656: every turn opens its events with user_message; wasm32-wasip2 release, sha256 ea4458c4...27817, 50977623 bytes); plugin.yaml unchanged --- dotbot: the panel's builds stay small in a long conversation (OrigoZero/DotBot#652), and the model a conversation runs on stays named in its composer (zero #19469). A history read again translates the messages from the first one that differs from the last answer and keeps the rows of every message before it, so a turn's end costs that turn's messages (a 2,068-message conversation's build after a history read: 130 to 172 ms before, 6 to 14 ms; 4,507 messages: 527 to 595 ms before, 11 to 21 ms); a call settled by a result read later is settled in a copy, so a list handed out stays as handed out; the transcript groups each ended turn once; a row's key is made once per row and trims in one pass; the agents, accounts and models lists are made once per answer; Source.model names a model the offer read now lacks by the record an earlier answer gave, else its id. On top of 01M57TE9R8E9 (zero #19466); plugin.wasm and plugin.yaml unchanged
01M57XN845DT23D9PQESA4MBA2e0d0c28c9fBrowse filesCompare with previousCompare from heredotbot: a queued agent's card says how long it has waited to start instead of a running time, and each card draws its task, current step and result or error on one line each (zero #19167); panel only (view, transcript, panel modules and READMEs); plugin.wasm unchanged (DotBot main 277ea257)
01M53NV8GX8H26HXYRGWA6CRXX27a78e70f8Browse filesCompare with previousCompare from heredotbot: a turn starts agents that work at once, each a caller of its own on the engine, and the panel shows them (OrigoZero/DotBot#584, closes DotBot#524 #219); plugin.wasm built from DotBot main 277ea257 (carries #578 59f5bd4c and #580), wasm32-wasip2 release, sha256 0a1d8acd...8d52d9, 50114599 bytes; plugin.yaml exposes subagents and stopSubagent; panel: agent cards (state, current call, time, tokens, pictures, stop), the agent's own transcript, the Working row naming the agents a wait is on, an agents usage line (service, source, view, transcript, panel modules and READMEs)
01M53HNAS8B4PR7N0748D224R7948dfc375bBrowse filesCompare with previousCompare from heredotbot: the panel shows each conversation's input tokens, output tokens and cache hit rate for the latest turn and the whole conversation (zero #19064), and a thumbnail of every picture a tool call returned at that call, larger on click (zero #19067); a turn the plugin woke into keeps the stored history on screen; plugin.yaml exposes toolImage. Panel and plugin.yaml only; plugin.wasm unchanged (DotBot main a935c7b1 carries DotBot#568)
01M52WHWHHETE5EB5T6ATHR6D51753331336Browse filesCompare with previousCompare from heredotbot panel: the Show earlier messages row is kept like any other transcript row, so a delta rebuilds only the row it lands in (zero #18123)
01M4QW0P9YC57W7N6218Q9PTRP226716bca0Browse filesCompare with previousCompare from heredotbot panel: the transcript is rebuilt row by row and draws a page of 40 rows behind Show earlier messages; the service mirror holds each read until a change marks it stale (a turn's end, a turn in an unlisted conversation, refresh), so an idle panel asks the plugin nothing (zero #18123, #18127)
01M4QTY3BTXSCZZ3SSCCCZ9JWA3f5bbf023bBrowse filesCompare from here