0verload - Release Notes ======================== Version 2.0.0 · 2026-09-29 -------------- The 1.x line is closed. 2.0.0 is one source tree with every branch of the last month folded into it and built as a single gated release. - Memory: per-model cache keys, the temporal web rework, the new on-disk memory format, hybrid retrieval groundwork and the housekeeping verbs. - Node: virtual Node hierarchy and a socket message bus; the debugger fans out over bus subscriptions. - Video clip stacker: engine and window rebuilt on the canonical structure (per-bot dirty sets, the window is a mirror and a keyboard, no shadow state). - Access: invite-only beta. No automatic trial; access is granted from the support console or by paying. - Claude Code: launch chooser for `o0 claude`, UTF-8 argv, grep edit keeps CRLF line endings. - macOS port groundwork merged (platform seams; the Mac build ships separately). - Attendant console, remote-in, and the UI window set current with the source. Everything below is the 1.x history, kept for the record. Version 1.1.05 · 2026-09-27 --------------- The build the site was pointing at still said 1.1.0, even after 1.1.01 was announced. 1.1.05 is the release build with the version string that matches what the site says, so the installer, the auth handshake and the build log agree again. - Version 1.1.05 is the 1.1.0 engine (memory per-model keys, temporal fixes, new on-disk memory format, housekeeping verbs, terminal fix) plus the Beta toolchain menu bar from 1.1.01. - Still to come in the next build: the subscription explaining itself in every window, and the firewall's greeting from the author. Those are on the license branch and were not part of this build. Version 1.1.01 · 2026-09-26 --------------- The menu bar gets out of the way, the subscription learns to explain itself, and the firewall carries a note from the author. - Menu bar: only the finished tools show by default - Configurator, Console, Manual, Version Control, Edit Visualizer, Memory, Stores. Everything still being polished (Terminal, Jobs, Outcomes, Workflow Scripts, Bots, Chat, Video Clip Stack, MCP, Overnode, Qwens, Skill Creator, Budget, Journal, Work) sits behind a "Beta toolchain" toggle, last on the bar. The toggle remembers itself; the first time you turn it on it says what beta means: you are free to use anything still in beta, but may be asked for feedback. - The RAM meter is gone for now. Its skull moved to the top of the sidebar. - Subscription: every window still opens without an active subscription, but a window that needs the memory service or the version-control service is look-only and says so in a yellow bulletin at the top ("REQUIRES: VERSION CONTROL - this is not available without version control, which requires an active subscription"), with a link to fix it. One notice at startup, always. A checkbox in the Version Control window quiets the rest. - The firewall skill opens with a greeting to the bots from Daniel. - The old license gate is being removed from the engine and put back in by standard procedure (in progress; see 1.1.0 notes for the memo fix). Version 1.1.0 · 2026-09-26 -------------- Memory grows a second index that is yours alone, learns to tell time properly, moves to a new on-disk format without touching the old one, and gets the full set of housekeeping verbs it was missing. Plus a terminal fix, a memory browser you can write from, and the video stacker's latest round. - Your memory keys, per model, per memo. Every model that reads a memory area now keeps its OWN topic table over the memos -- the labels its weights recall a memo by -- while the writer's topics stay the fixed address space. On load, `memory.cachekeys` hands a model its table plus a page of the memos it has not keyed yet (with content); `memory.cachekey` stores a whole batch of memo -> label at once. A high-water mark replaces the old pending flag: every write appends, so what a model owes is always the tail above its mark -- no scan. `memory.models` shows who is CURRENT and who is BEHIND by how many; `memory.modelkeywords` recalls through a model's own table and is blocked only for that model until it catches up (shared recall never blocks). `memory.add` / `memory.addmemo` print the new memo's `@offset` so the writer keys it on the spot. The local embedder is a model type too: its pass runs headlessly (one vector per memo, no inference cost). `memory.forgetmodel` drops a model's table and file. Keys live beside the store in `model-.ovm`; memos never change. - Time is a web now, not a scan. Each dated or relatively-dated memo carries a reverse pointer to its anchor, an explicit previous/next link into the context-wide event chain, and an entry under every prefix of its date (2026, 2026-09, 2026-09-20). Bounding a vaguely-dated event is a pointer walk; a dated question is a lookup. Any retrieval that contains something time-related -- `memory.keywords`, `memory.search`, `memory.modelkeywords` -- now consults the temporal web as part of its investigation and appends the hits (a third fused lane when the semantic lane is armed). A question with no keyword hits still returns its temporal hits. - A memo can no longer be written empty. An MCP call that names an argument wrongly (`memo` or `body` instead of `content`) is refused before anything runs, naming the missing and unknown arguments and the ones the tool takes -- every tool's call is now checked against its own schema, required keys and all. And `memory.add` / `memory.addmemo` refuse zero-length content at the grammar too, so a bad caller gets an ERROR, not an OK and a hollow record. (88 attendant worklog memos had landed on disk with no body that way.) - Dates parse correctly. ISO and numeric dates (2026-09-20, 20260920, 9/20/2026) resolve to the day, not just the year, so temporal / when / chain work at month and day granularity. A stray number after a date ("1.0.9" three words later) no longer overwrites the day; "Sept" is accepted. - New store format, old store untouched. Memory areas now live in `data.ovl4`. The first time an area is opened, its previous `data.mem` is read read-only and COPIED into the new file; the old file is never renamed or rewritten, so an older build still runs on it. Backups go to `data.ovl4.last`. Export emits `.ovl4`; import accepts OVL2, OVL3 and OVL4 and never rewrites its source. - Every memo has a write time. `memory.recent` lists what changed lately; `memory.stats` reports an area's shape (topics, memos, keywords, time keys, vectors, per-model lines, bytes, span of write times). Memos from before this build are "untimed" and sort last. - `memory.update` replaces a memo in place -- same slot, new content, keywords and type, fresh write time. Memory is current state, not history: an edit overwrites, it never chains. - `memory.lint` cross-checks an area's indexes against its record buffer and disk file (including the per-model overlays and the temporal chain) and names anything wrong. - Context lifecycle. `memory.contexts` shows the store root and each area's size; `memory.search` looks across every loaded area; `memory.archive`, `memory.rename`, `memory.purge` and `memory.clone` manage areas in place. - One story about `memory.add`. Help, manual, skill and MCP now agree: same topic = REPLACE; `memory.addmemo` appends. `memory.help` lists every verb (temporal, chain, embed, semantic, update, stats, lint, recent, search and the per-model verbs) with comma-form examples, generated from the one registry the engine itself uses. - Full MCP surface. Claude Code now sees every memory verb as a tool -- query, temporal, chain, w5, w5find, semantic, embed, indexdir, update, stats, lint, recent, search, models, cachekeys, cachekey, modelkeywords, forgetmodel -- with descriptions sourced from that same registry. (A running resident must be restarted on the new build to expose them.) - Memory browser you can write from. The GUI window adds a new-topic / new-memo / edit-memo editor, keyword search in the selected area, the same words across every area, a `?()` query box, write times on every memo row, and two-click deletes (no confirm dialogs). - One set of skills. The overload-memory and reverse-cache-memory skills are synced across every shipped copy and rewritten for the per-memo keys; the memory manual matches the engine. - Terminal: the bottom of a long session no longer jumbles. The 0term read cursor tracks absolute stream offsets across the output ring's wrap, so a window that has scrolled past 256K of output stays in sync instead of needing a reload. - `/g-walk` (also `/glyphwalkers`) serves the glyph-walker ceremony on a clean vanity route for showing it off. - Video stacker, latest round: `vid.compose commit` mints one PENDING slot per shot so the stack shows holes instead of erroring; re-stitching renumbers every authored seam through the old -> new shot map; seam memos carry a moving instant ("moving: ... ; world: ...") instead of a frozen weld; the internal proxy defaults to the smallest LOD at maximum compression; a story is sent as one grammar line; the panel detects verb errors instead of printing the cheat-sheet. - Parked: the 0verload-native workflow AUTHORING layer. workflow.new / addstep / setstart / validate / rm / spawnrule, the workflow.wizard.* family, the standalone workflow2.* translator and the Jobs window's Author tab are gone from the grammar, the MCP tool list and the GUI; their source now sits in src\notworkflow.bak. workflow.list / workflow.show stay (read-only) and the job engine (job.*) is unchanged. The `workflow` name is being re-pointed at Claude Code's native Workflow tool. - Build: `/bigobj` is now on for the whole tree (filesystem.cpp outgrew the default object-file section limit). Version 1.0.14 · 2026-09-18 -------------- - Free vs. subscription, clarified. The CONFIGURATOR and the built-in HELP stay free so you can install, configure, and sign in; every functional tool -- memory, version control, grep, video, nodes, jobs, chat and the rest -- runs on an active subscription. Start a 3-day free trial or subscribe at https://0verload.net. - Build and packaging refresh; reliability fixes. Version 1.0.10 · 2026-08-31 -------------- How the free trial works now, plus optional semantic + temporal recall, a new configurator Loadout panel, and a broad reliability, security, and speed pass. - Your 30-day free trial -- and what stays free after it. 0verload is free to try for 30 days. On first run it opens your browser to sign in with Google or GitHub: no credit card, ever -- signing in is simply how the trial is kept to you. After the trial, MEMORY and VERSION CONTROL need a subscription, but the CONFIGURATOR, the TERMINAL, and the built-in 0verload wiki keep working FREE for as long as you like. Your data is never touched or deleted -- subscribe any time and memory + version control pick right back up where they were. Subscribe at https://0verload.net; you can sign in again any time with `o0 signin`. - Optional semantic recall. Memory can now (opt-in) embed what you save and find it by MEANING, not just matching words -- so a paraphrase turns up the right memo even when none of the words line up. It is OFF by default and needs a local embedder (ollama with nomic-embed-text); with it off, memory behaves exactly as before, with no new dependency. Arm it per memory area with `memory.embed on`. - Temporal recall. Memory can trace a subject across time: it gathers the dated and the vaguely-dated mentions ("a couple weeks ago"), orders them, and pins the vague ones to the real dates around them. - Version strings are findable again. A memo that mentions "1.0.9" now indexes 1.0.9 as a single token, so you can recall it by the version string. Previously it was split into single digits and dropped. - o0 grep: a new -p flag publishes one result per matching LINE (path:line) instead of per file, so a search's individual hits can be sliced and piped straight into the next command. - Configurator: a Context Loadout panel. The configurator gains a rack-style panel for your context recall list, with a health lamp per context so you can see at a glance which ones resolve. Adding a context now rejects typos and empty entries. - Configurator: pre-configurator restore actually works now. `claude.backup` captures your pristine pre-configurator Claude state and `claude.revert` puts everything back -- previously a naming collision left that snapshot unwritten, so revert had nothing to restore. (The on-demand rolling snapshots moved to `claude.backups now|list`.) `claude.undo` now also reverses the skillifier mode marker, so undo fully unwinds init.harden / profile.load. - Faster memory. Saving and recalling memos is quicker on large stores -- a few hot paths that did redundant work per item are now linear. Stored data and recall order are unchanged. - Reliability and security hardening: - Fixed a data-loss bug: writing a file whose path contains a space through the MCP fs.write tool could replace its whole version history with a fresh file. It now correctly appends a new version. - Closed several rare crash windows in version control and file listing that could trigger under heavy concurrent access. - Internal message inboxes are now capped, so a flood of chat/DM traffic can't exhaust memory and take the server down. - The directory-listing endpoint behind the version-control UI is now local-only; it can no longer be reached from other machines. - Sturdier grep (symlink-loop guard, better binary-file detection, cache freshness) plus assorted crash-hardening against malformed input. - The Bots and Chat windows are temporarily hidden from the window menu while they get more work; nothing is removed, they'll return in a later build. Version 1.0.9 · 2026-08-29 ------------- Upgrade and integration fixes. - Upgrading in place no longer hangs. If 0verload was already running when you installed a newer version, the installer could stall trying to replace the program file while the running copy held it open. The installer now reliably stops the running copy before replacing it, and 0verload also shuts itself down cleanly when an update asks it to. - MCP: the connection handshake now negotiates the protocol version with the client (Claude Code and other MCP clients) instead of forcing a single version, and it only advertises capabilities it can actually deliver. - MCP: the resource list is no longer silently capped at 150 entries. Large repositories are now fully browsable through paging. Version 1.0.8 · 2026-08-18 ------------- Installation and setup fixes. - The `o0` command is now added to your system PATH during installation. Previously, on a clean machine, `o0` was not recognized in a new terminal until you added it to PATH by hand. (This was cosmetic only - the version-control resident and the Claude Code integration always worked, because they use the full path to the program.) Root cause: the PATH entry was written in a post-install step that runs AFTER the setup helpers - and on a machine still installing prerequisites, that helper kept the installer busy so the PATH step never ran. The PATH entry is now written declaratively during the main install phase, before any helper runs, so it always lands. - The installer no longer appears to hang while setting up prerequisites. The Python / Node.js / Claude Code setup helper now runs in its own window instead of holding the installer open until its downloads finish, so setup completes right away and the helper continues in the background. Version 1.0.7 · 2026-08-18 ------------- - Taskbar / tray behavior consolidated; edit-history handling tidied up. - MCP: more robust stdio handling - emits valid JSON-RPC even when the input stream begins with unexpected bytes. - `o0 grep`: the default search scope now follows the working directory of the bot issuing the search. Version 1.0.11 · 2026-09-01 -------------- - Fixed: the Claude Configurator's Configuration tab now ships with "Include 0verload subscription tools" turned ON by default. A fresh install used to show 0verload's own memory and version-control tools as not included, which was backwards - your free trial is meant to have them active so you can actually use them. Turning them off is now a deliberate opt-out. Version 1.0.13 · 2026-09-17 -------------- A big one: a new video-production tool, a real interactive terminal, and a broad file-search + version-control reliability pass. - New: video production. Write a bible (look, characters, style) and a screenplay, and 0verload breaks it into a shot list, generates a take per shot, and lays them out in a visual clip stack -- reorder by dragging, trim each clip's in/out points, then render the whole stack to one output video. You can also paste in a URL to a ready-made clip or image and drop it straight into the stack alongside generated takes. - New: a real terminal, not just a shell window. `o0 terminal` now opens an interactive terminal that can run your normal shell, or launch `bash`, `powershell`, or a full Claude Code session, each labeled by instance (bash1, bash2, ...) so you can tell multiple open ones apart. It no longer jumps in front of whatever window you're using by default -- it only takes focus when something deliberately asks it to. - o0 grep now searches everywhere by default. A plain search used to only look at one project at a time; now it searches every enrolled project and your memory in one pass, and can jump straight from a matching line to editing it in place. - Notifications you can actually control. Background jobs can now speak a status update when they finish -- success or failure, naming the job and how far it got -- with a simple on/off switch, both overall and per job. - The edit visualizer now displays edits by default. Every enrolled project folder now shows its live edit activity in the visualizer out of the box -- including edits made outside 0verload's own tools -- instead of needing to be turned on per folder. Turning that display off now requires an explicit confirmation, since it's your visibility into anything edited that way. - Under the hood: a broad pass on how 0verload figures out which project a command applies to, closing a class of bugs where a command could quietly guess the wrong project instead of asking. - Notifications now have a distinct sound per event, not just one beep. A job finishing successfully, failing, or getting escalated for your review each play their own short, easy-to-tell-apart tone -- and escalations, which previously had no sound at all, now alert you too. -- Questions or feedback: i@g0t.io https://0verload.net