Nothing has shipped publicly.
This is the build, by date.
No installer has been released to anyone. What follows is when each part of the app landed, taken from the project’s own records, newest first.
The first public release.
PlaceholderFirst release entry.
Version, date, what is in it and what is known not to work. Written by the owner when it exists. Code signing, an updater and a download host come first.
Version 0.4.0. The browser pane can capture and go full screen.
The browser pane gained Ask, Save, Capture and full screen. A connection can be marked as the agent’s own account, and Stop now reaches a read that has stalled. More.
Versions 0.2.0 to 0.3.0: the first installed build.
The first build installed on the owner’s own machine, not released to anyone. Only one copy runs at a time, and an installed build writes a local log. The app can connect to MCP servers on your own network, and companions say whether a program is attached right now. More.
Your data survives an upgrade, and can be restored.
Before any upgrade the database is copied, and the newest five copies are kept. Each upgrade step is one transaction, and a database newer than the app is refused rather than read. Back up my data and Restore are on Settings.
Spreadsheets, carousels and Canvas tools.
A sheet is a fourth kind of document and exports as .xlsx, with a cell that starts with = kept as a live formula. A carousel is a deck that declares its shape. The Design Canvas got a tool row and a Tweaks window you can move. More.
Contacts at scale, Today as a status page, and deals.
Contacts became a list with a reading pane, imported from a Google or Outlook CSV of up to 20,000 rows and edited in bulk. Today opens on figures: balance, a week’s spend, connections and the index. The browser pane got tabs, find and zoom. Sponsorship deals got their own tab, dated on the Calendar. More.
The business half, and a graph of everything.
A business is a folder of files: contacts, deadlines on the Calendar, expenses with receipts filed beside them, invoices under a brand, quotes, hours and credit notes. The knowledge graph draws everything the app knows as one picture. A conversation can carry a dollar ceiling, and has none unless you set one. More.
A file editor that can be undone.
Saving a file is undoable and notices when something else changed it first. Notes link with [[links]], and an Obsidian vault opens as it is. More.
Triggers, and the agent working a real website.
An automation can start when a file lands in the project or a new item arrives from a connected server, not only on a clock. On a live site, the agent opened a page, read it, filled a four-field form and submitted it in the browser pane, with the owner watching. More.
Today, the month Calendar, and the retro themes.
Today became a tab of its own. A month Calendar shows what you owe, what the app has promised to run and, if you connect one, your own calendar. The window took on its current look, the Phosphor and Cassette themes.
MCP connections, and the companion door.
VectorBrain can connect to MCP servers, local or at an address with sign-in, and its agents call their tools by name. The same day, Claude Code, Codex and Claude Desktop got a door into the app. More.
Panes: every open conversation on screen at once.
Open conversations can sit side by side, and Ctrl+1 to Ctrl+9 reach one by its number. The stage became a drawer.
Documents open on the Canvas.
Markdown, text and PDF files render on the Canvas, Word files, sheets and decks open as a reading of themselves, and words in an HTML design can be edited by clicking them.
Automations.
An automation is a message you would have typed, kept with a time to send it. An agent can write one, and you edit it on its card before you sign it. More.
Crews that work at once.
A crew runs every member together and reports back in order. A member can be limited to a lane of files, and researchers may read the web. The owner ran the first real team job the same day. More.
The browser pane, and files in and out.
A real browser pane over the stage that the person and the agent share: looking never asks, acting always does. Files can be copied in from any disk, a folder can be opened read-only, and each model gets a reply budget sized to it. More.
Agents and crews.
An agent is a folder you wrote, with its own searchable notes. A crew is a permission you sign, and a lead can hand work to its members. More.
Work, Design and Build.
Design became the third mode, with a Live preview and PPTX export. The agent could read pages that only exist once their scripts run, and the Studio started offering exactly what each model can make. More.
Project memory, and the Canvas.
A project got a memory in four places, and a run could read the web. The app began to make things, each with a way back, and a document could leave as a real file. More.
The first commit, and the core.
One command bus with two front doors, the person and the agent. Streaming models with a readable cost, an agent loop with a gate that asks before it acts, files confined to the project, documents that keep every version, and a project index that can answer a question. More.
The details,
for the careful.
Has VectorBrain been released?
No. Nothing has been released publicly. The build’s version number is 0.4.0, set on 2026-09-25, and no build has been published.
When did work on VectorBrain start?
The first commit is dated 2026-08-14. There were 400 commits between then and 2026-09-25.
When will the first public version come out?
No date has been set. Code signing, an updater and a download host all come before it, and none exists yet. Where the download stands
Where do these dates come from?
From the desktop project’s own progress record and its commit history. Each entry is the day the work landed in the build, not a release date.
Is there a public repository or release notes feed?
No. The project has no public repository yet, so this page is the record.