Releases: VodouAI/vodou-core
Release list
v0.6.28
v0.6.27 — install-path repair
If you installed v0.6.26 and every command came back with Not connected to Vodou, this release is the fix — and it was our bug, not anything you did.
What went wrong
The published source tree was missing its .env.example, and the installer created your .env from that file without saying anything when it wasn't there. One missing file, two symptoms that looked unrelated:
- no account keys → the account gate refused every command (
Not connected to Vodou) - no path to the memory engine's native library → semantic search crashed with an ONNX error that read like a completely separate bug
Every one of our publish gates passed. They all ask whether something forbidden got in; none asked whether something required had fallen out.
Fixed
- A fresh install starts.
.env.exampleis published again, and the installer now writes a working.enveither way — telling you plainly if it had to fall back, so a packaging mistake can never be silent again. - Every bundled app gets set up, not just the ten on a stale hardcoded list. The Kanban board's connector shipped without its dependencies and failed on first use, while the install cheerfully reported "0 need attention".
- Windows had the same hole for a different reason — its installer never created a
.envat all. - A mismatched memory library is replaced, not trusted. The installer checked only that the file existed, not that it could run on your processor.
Also
Release packaging now verifies required files are actually present in what ships, not only that forbidden ones are absent. Recorded test fixtures are no longer published — one captured a real session and carried personal details with it.
Install
curl -fsSL https://raw.githubusercontent.com/VodouAI/OS/main/install-vodou.sh | bashmacOS (Apple Silicon + Intel), Linux (x64 + arm64), Windows (x64).
Known issues
The Windows package is unsigned, so SmartScreen will warn on first run.
Alpha.
Vodou v0.6.26 Alpha
Ask for something complicated and Vodou now shows you the plan before it runs — the actual steps, what happens in parallel, and where it will need to stop and ask you a question. You can run it once, edit it, save it as a skill, or schedule it. And when a plan turns out to be a wrong guess about what you meant, there is a button that throws it away and just answers you.
Plans you can see before they run
Type a sentence — "research three competitors and put the summary in a doc" — and you get a plan card: the steps in order, the ones that run together, and the points where it will pause. Nothing executes until you say so.
- Runs can stop and ask. A plan pauses on a real question — an approval, a choice, a missing detail — and waits instead of guessing. The question follows you: the console, the browser panel, or a chat channel. Answering it resumes the run.
- "Just answer it" — the way out when the plan misread you.
- A finished run leaves a trace you can search. Phases of one job group into a single run rather than four, and the Skill Console now shows each skill's own run history.
- [Save + schedule] turns a plan you liked into a skill that runs on its own.
Also in this release
- Memory and the brain are one thing. The memory graph moved into the console as a single Memory section — one process, one place, instead of a second window on another port.
- The browser panel can save the page you are looking at, through the same form and endpoint as everything else — and it now says honestly whether the brain link is connected, rather than reporting "no" when it means "don't know".
- One rules file per AI host, from one source. The file each coding agent reads — Claude, Cursor, Gemini, Copilot, Codex — is generated from a single manual, with a guard that stops them drifting apart.
- The browser page tools ship. The Bridge extension's page tools are now a bundled server, so skills and the brain can read and act on the page you are on. It was built during this cycle and, until now, was in no release anyone could install.
Fixed
- A background job that finishes after the reply now reports back. When Vodou said "I'll report the exit code when it lands", nothing was left running to do it. Long jobs now post their result into the conversation themselves — and Vodou no longer promises a follow-up it cannot keep.
- A plan sent to a chat channel arrived twice, and the second copy was wrong. A reply meant for an approval gate could reach the model as if it were a new question.
- One failed branch of a parallel step no longer erases its siblings' results. A step that cannot start fails on its own instead of taking the run down with it.
- A declined approval no longer leaves the run marked "running" forever.
- Scheduled skills say where their output went — a run delivered to the console used to report "delivered nowhere".
- An expired login says it is expired. A credential that could not be renewed reported itself healthy.
- Memory searches stopped sending a whole document where a query belongs — about fifteen places did.
- The context a turn used survives a reload, with a per-turn budget that names what it dropped instead of dropping it silently.
- Two Vodou sessions editing the same files now warn each other.
Install
curl -fsSL https://raw.githubusercontent.com/VodouAI/OS/main/install-vodou.sh | bash
Windows: irm https://raw.githubusercontent.com/VodouAI/OS/main/install-vodou.ps1 | iex
Engine binaries: https://github.com/VodouAI/vodou-core/releases/tag/v0.6.26
Full changelog: https://github.com/VodouAI/OS/blob/main/CHANGELOG.md
Known issues
- The Windows build is unsigned — SmartScreen will warn — and is download-only: Windows installs do not auto-update.
- The browser extension updates on the Chrome Web Store's schedule, not this release's.
Alpha.
Vodou v0.6.25 Alpha
This release repairs the updater itself. If an update has ever seemed to hang, told you it crashed while it was working, or quietly left one of your tools broken — that was all real, and this fixes it.
Updates that finish what they start
A bundled tool whose folder contains a linked package — the channels integration that drives Slack, Telegram, WhatsApp and the rest — failed to copy during every update since 0.6.15, and the half-copied folder was left in place. Seven releases in a row reported the same seven words, "1 component failed", and named nothing. If your channels stopped connecting weeks ago and never came back on their own, that is why. This update repairs it.
Alongside that:
- A part of an update that fails now restores the previous copy instead of leaving that tool broken with no way back.
- The update tells you which part failed.
- The memory-graph brain now updates with everything else. It was excluded from every automatic update since it shipped, so an install that lost it could never get it back.
- These fixes apply to the update that delivers them, not the one after.
Updates that tell you the truth
Past the ten-minute mark, a perfectly healthy update printed "a previous update may have crashed — consider rolling back" every thirty seconds until it finished. A full update legitimately takes about half an hour, so most of one looked like a failure. It now reports what is actually happening.
The download used to pull ~350 MB in complete silence, with no way to tell a slow connection from a hung one — which is exactly when someone interrupts an update that was working fine. You now see how much has arrived, how fast, and how long is left. A genuinely stalled download says so instead of waiting forever.
Also in this release
- Create or pick a project folder from a browser, including folders that do not exist yet.
- The Document Library finds documents by meaning, not just by name — ask for what you remember about a document and it finds it without the title.
- Add documents by dropping in a whole folder, and browse anywhere on the filesystem rather than only your home directory.
- Model lists for every provider are current as of this build.
Fixed
- Two copies of the app no longer share one database file, and writes are no longer lost when the database is busy.
- Database corruption is noticed in minutes rather than days, and the automatic repair now acts on what it diagnosed instead of discarding it.
- A scheduled task that never actually runs now says so, instead of appearing healthy.
- Switching projects picks up a project you just created.
- Two Vodou sessions running at once no longer scramble each other's activity log.
Install
curl -fsSL https://raw.githubusercontent.com/VodouAI/OS/main/install-vodou.sh | bash
Full changelog: https://github.com/VodouAI/OS/blob/main/CHANGELOG.md
Known issues
- Updating to this version still runs the previous version's downloader, so that one last update is quiet and may still show the stale "may have crashed" notice. Every update after this one shows progress.
- The Windows build is unsigned — SmartScreen will warn — and is download-only: Windows installs do not auto-update.
Alpha.
Vodou v0.6.24
Several tools have shipped inside Vodou for months without being switched on. The task board, the memory-graph brain, the IDE memory server, Gmail and Microsoft 365 were all in the archive, all installed, and all invisible to the app — no connection, nothing under Capabilities, nothing callable. This release registers them, on new installs and on updates, and fixes the reasons a few of them could not have started even once they were.
Tools that were installed but invisible
Vodou keeps a registry of the tools it can talk to. That registry is written once, from a template, and the template's list had quietly drifted from the list of things actually being packaged. Five servers fell into the gap.
The task board was the visible casualty: a dispatched task would do its work, find it had no way to report finishing, and get reclaimed and restarted — forever. Workers can now close out their own tasks.
Updating an existing install had a second, separate hole: your registry is yours, so a corrected template never reached you. A migration now registers the same tools on update. Gmail and Microsoft 365 arrive switched off until you connect an account.
Also in this release
- Updates take effect immediately. Newly registered tools used to stay invisible for up to five minutes after an update, while the app was still reading its old list. The list is refreshed before anything reads it.
- Bundled tools run on the Node that ships with Vodou, not whatever is on the system. On machines with an older Node, or none at all, several tools simply failed to start.
- The brain console and the Vodou One shell are started, stopped and restarted properly by the service manager, and survive an update.
- macOS quarantine is cleared on first start, so a freshly downloaded build stops being second-guessed by Gatekeeper.
Fixed
- The Chrome DevTools tool was packaged one directory deeper than the app looked for it — in every release that included it — so it failed on first connection and retried in a loop.
- Your account token was written to the log in plain text every time your licence was checked, and stayed there. Tokens are masked wherever they are logged now.
- A tool server that needed a specific directory name failed to load on Linux because the name differed only in capitalisation.
Install
curl -fsSL https://raw.githubusercontent.com/VodouAI/OS/main/install-vodou.sh | bash
Engine binaries: https://github.com/VodouAI/vodou-core/releases/tag/v0.6.24
Full changelog: https://github.com/VodouAI/OS/blob/main/CHANGELOG.md
Known issues
- Model lists for Groq, DeepSeek, xAI, Mistral, Together and Kimi are about three weeks old in this build. Other providers are current.
- The Windows build is unsigned, so SmartScreen will warn, and it is download-only — Windows installs do not auto-update to this version.
Alpha.
Vodou v0.6.23 Alpha
Documents become memory. Vodou could always remember your conversations; it could not read the contract, the plan, or the spec those conversations were about. Now it can — and it can tell you which document answers a question, quote the passage, and hand it to any model on request.
The Document Library
- Ingest what you actually keep context in —
pdf,docx,pptx,xlsx,csv,epub,md,txt— from a file, a whole folder, a URL, or the page open in your browser. - Browse it at
/library— search, filter by state (broken / un-carded / watched), read the extracted text, open the original, and add documents with a paste-a-path box that shows live progress on a folder import. - Attach a document to any chat with
`@doc:<name>`— the Vodou console, Slack, Telegram, anywhere. A typo suggests the right document instead of failing silently; a document too large to attach whole says so and points at the section you want. - Vodou knows which document answers a question. Each document gets a routing card — what it is, what it answers, and what it is not about — so "what is our liability cap?" reaches the contract rather than a guess. Documents now surface in ordinary memory search for the first time.
- The panel tells you when a page relates to something you saved, and stays quiet when it doesn't — deliberately, because a chip that lights up on everything gets ignored.
- "Add to Vodou Library" in the browser — right-click any page, or use the keyboard shortcut for pages that own their right-click menu (Google Docs, Notion). Requires Vodou Bridge 0.5.97.73+.
Also in this release
- Documents are chunked as documents. A bullet in a personal note is a standalone fact; a bullet in a plan is prose. Treating them alike split one plan into 181 fragments — it now produces 50 coherent passages with nothing lost.
- Document matching is fast — ~10s to under a second, by asking the already-running memory service instead of starting a new one per question.
- One reranker per install. The background service and the command line were quietly using different relevance models, so the same question could score differently depending on which answered it.
- Contradiction detection reads across documents — a governing-law clause is compared against other governing-law clauses, not the whole corpus.
Fixed
- Two silent text-loss bugs in document import, both found by reading a stored document rather than trusting a success message: a paragraph-splitting bug dropped 940 bytes of a 9,199-byte passage mid-word, and an oversized first paragraph was never split at all.
- Pasting a bare document reference no longer confuses the router into running unrelated tools.
- Browser capture of Notion-style pages no longer welds every block into one run-on line, nor eats words inside links and buttons.
Install
curl -fsSL https://raw.githubusercontent.com/VodouAI/OS/main/install-vodou.sh | bashEngine: VodouAI/vodou-core v0.6.23 · full history in CHANGELOG.md
Known issues
- Windows is unsigned — SmartScreen will warn. Treat it as a preview.
- Model lists for six providers (groq, deepseek, xai, mistral, together, kimi) are ~3 weeks old in this build.
Alpha.
v0.6.21
v0.6.20 — Alpha
Vodou v0.6.20 — ALPHA. Still alpha: expect rough edges, and don't point it at anything you can't afford to have go sideways.
Vodou is open-core. This repo (Apache-2.0) is the full client + orchestration surface; the engine binaries ship under the EULA from VodouAI/vodou-core. Both are attached below.
265 commits since v0.6.19. This is a big one — the browser bridge went from "works on two sites" to "works on twenty-two", and the memory graph got a face.
Your AI chats become memory — on 22 sites, not 2
Save what's here used to work on ChatGPT and Claude only. It now works on all 22 supported sites: Gemini, AI Studio, Grok, Perplexity, DeepSeek, Copilot, Le Chat, Qwen, Kimi, Z.ai, T3 Chat, OpenRouter, Poe, Meta AI, Manus, You.com, Duck.ai, NotebookLM, HuggingChat and Character.AI.
Each site was verified by saving a real conversation and reading the stored text back out of the database — checking words and speakers, not turn counts. Every single site had its own defect, and none of them would have failed a count check:
- Reasoning leaks on seven sites. One stored 1,045 characters of the model's private chain-of-thought as if it were the answer — twice the length of the actual reply.
- Interface text stored as speech on six. Hidden accessibility labels ("You said"), icon names (
keep_pin,copy_all), timestamps, model badges. - Broken conversation identity on three. One site gave every unsaved chat the same id, so each save silently overwrote the last.
- Missing or invented turns on four. One virtualized list dropped 3 of 8 messages; another stored every user turn twice; another captured alternate replies the user never kept.
- Private data captured as a message on one — your own account name.
Under the hood that's one parameterized extractor driven by per-site selector data, plus a new import lane in the engine, so a site that changes its markup is a data fix rather than a release.
Auto-attach memory when you send (opt-in, off by default)
Turn it on per site and pressing send pauses, appends relevant memory to the bottom of your message, and sends it as one prompt. With it on, Vodou acts on your behalf — the panel says so plainly, and the privacy policy was updated to match. Off by default, and off means nothing is ever sent for you.
Your message is never lost: a failed lookup, an empty result, a failed insert and a hang all still send exactly what you typed.
One in-page control instead of two
The two floating discs merged into a single mark that fans open into the actions available on that site. Progress and results now report on the button rather than in a box beside it.
The Brain — the memory graph, visible
- The stars, and how they connect — the graph as something you can actually look at.
- Latest view — the newest memory lit up with its context in rings.
- Chronicle — pick a day and see what it connects to.
- Relations that say how two names are related, not just that they co-occurred; and entity typing so a name is understood rather than guessed from its shape.
The capture feed
Every captured conversation, every provider, on one wall — with the model that answered, a link back to the original thread, and a way to delete anything that shouldn't be there.
The extension became a proper product
The popup is gone; the toolbar icon opens a side panel that holds the memory picker, activity log and every setting. Per-site toggles for both capture and insert across all 22 sites. A capture kill switch that a provider objection can actually reach. Pairing that links straight to where the code lives.
The store build reads only — outgoing request bodies are never modified.
Onboarding
The browser lane can be acted on now: an install path, live detection when the extension connects, and proof it actually captured something. A lane fixed by an environment variable states the value and names the variable instead of showing a checkbox you can't move.
Memory quality
- Imports stopped re-extracting the same fact once per monthly file.
- Pasted console output is no longer stored as durable memory.
- The extractor understands dates.
- Self-healing brain: better default embeddings with a probe-gated swap, plus scheduled dedup and self-test.
- Guest memory is scoped to the room's vault, and the bootstrap leak is closed.
Platforms
Prebuilt bundles for macOS (Apple Silicon + Intel), Linux (x64 + arm64) and Windows x64.
Windows is untested at runtime and unsigned — SmartScreen will warn, and it hasn't been verified on a real Windows machine. Treat it as a preview.
Install
curl -fsSL https://raw.githubusercontent.com/VodouAI/OS/main/install-vodou.sh | bashOr download a bundle below and run ./install-prebuilt.sh.
Known rough edges
- Windows: unsigned, runtime unverified.
- The in-page Save button reads the messages currently rendered on the page. On very long threads that's what's loaded, not the entire history — provider exports and the paginating backfill still cover the rest.
- Auto-attach finds each site's send control by its accessible name; a site that ships an unlabelled button may need a one-line addition.