The office floor: a living pixel-art plan of where every intern works — watch them pick activities, wander, and get sent home.
Windows port progress: Apple-only sources gated, a headless Windows entry point, and CI building BlazeBot with Swift on Windows.
Sign-in controls centred during onboarding.
0.12.1 Beta
Sign-in polish
The account sign-in section is centred during onboarding.
0.12.0 Beta
The X Desk — admin only
An admin-only company: niche research, content drafting with draft review, and isolated VPS desktop controls.
BlazeBot accounts now carry a role; admin desks answer to it.
0.11.0 Beta
Bots on a schedule, and a whole company at once
Give any Bot standing work on a schedule, or raise an entire team of specialists in one click.
Routines: daily, weekly, every N minutes or hours, or once at a fixed time. When one fires it lands in the chat as if you had typed it, so handoffs and approval cards still apply.
Routines pause with a reason if their chat or Bot disappears, catch up correctly after the app was closed, and never fire twice.
Companies: pick Startup crew, a shop, or a minimum pair, and the whole team is created with standing rules per seat.
The company lead takes the brief first and delegates by @mentioning the right specialist.
Firing a Bot got a proper warning screen: the blob, exactly what will be deleted, and Keep Bot as the default.
Sign-in polish: centred auth buttons, your email remembered on the sign-in sheet, and Bot memory commits when you click away.
0.10.0 Beta
Your own BlazeBot account
Sign up and sign in with an email and a password — no BlazeAPI account needed.
Choose “Sign up with email” during setup, or “Sign in with email” from the account menu.
We email you a 6-digit code from code-noreply@blazeapi.org to confirm the address. It can take a minute, and it may land in spam or junk while our mail server builds its reputation.
Forgot your password? The same sheet sends a reset code, and resetting signs every other device out.
Passwords are hashed with scrypt on our servers; the session token stays in your Mac's Keychain.
Linking a BlazeAPI account still works exactly as before, and the two can be used together.
Updates close Settings before quitting, so an open settings window can no longer hold an update hostage.
0.9.1 Beta
The sandbox, properly locked down
Same machines, stricter rules: the cloud VM is now agent-only, sessions are signed, and the browser is free for everyone.
The VM is agent-only — no human shell access. Your Bots run in it from BlazeBot; people don't get a terminal.
Every session carries a token the service mints at sign-in, so a leaked id alone opens nothing and nothing works outside the signed-in flow.
The VM runs with capabilities dropped and privilege escalation blocked, and its network is fenced off from our host and private ranges — internet yes, everything else no.
Destructive commands (whole-filesystem deletes, fork bombs, disk formats, sandbox escapes) are refused by name, with the reason told to the agent.
Allocation is a fixed pool. VMs sleep after 30 idle minutes, Pro preempts a free slot when the pool is full, and everyone else sees “We are currently at free capacity, please buy a plan or have the bot use your device”.
The cloud browser is free for every signed-in account, and agents drive it from the app.
Star, heart and bolt left the character picker (ghost stays) — bots saved with them keep rendering.
0.9.0 Beta
Full VM operations, a cloud browser, and the web sandbox
The folder chip in any chat now offers Run in the Cloud VM: the Bot's shell and files execute in a disposable machine on our servers.
VM work never asks permission; the machine is thrown away when you're done.
A cloud browser runs on our servers and the Bot drives it instead of your screen, mirrored through the its-screen panel.
The in-app updater always jumps straight to the newest build, and the releases page leads with a latest button too.
0.8.1 Beta
Watch it work — on its own screen
When a Bot uses the computer, a corner panel mirrors exactly what it is looking at, frame by frame — the way you would watch a coworker's screen over their shoulder, without them taking over yours.
A live preview panel beside the transcript — every screenshot the Bot takes streams in, scaled down, with a live pulse.
It appears the moment the Bot starts looking around and closes with one click; it interrupts nothing.
Frames are shown live and never stored — the transcript keeps the tool rows, the panel keeps the view.
0.8.0 Beta
A bigger shelf, a better memory, and a laptop of their own
The directory grows to 35 premade interns — finance, ops and people join the shelf — and Bots learn to remember and to own a computer.
35 presets: new Finance shelf led by Market Analyst, a trading professional that writes theses with invalidations (paper only, always), plus Risk Skeptic, Expense Auditor and Ledger Keeper
Memory: teach a Bot a fact in Settings and it carries the fact into every conversation — one-on-one and in groups
Its own laptop: every Bot owns a private folder, and a direct chat works there when no project folder is picked — its own computer, its own files
Four new characters: star, heart, ghost and bolt join the blob family — original silhouettes, and they morph like all the rest
0.7.0 Beta
Your Bots, reporting where your team lives — plus a Windows beta
Link Discord or Telegram and your interns post what they are up to right there. And BlazeBot for Windows ships today, beta.
Discord link: paste a channel webhook and hires, renames and updates post straight into your server
Telegram link: paste a BotFather token, send /start, and the reports land in your chat — /status answers with the live roster
Custom colours: a spectrum picker joins the eleven swatches, so a Bot can be any colour at all
Profile pictures: the Generate tab is gone and Upload works — pick an image, BlazeBot crops and stores it
Windows beta: the installer lives on the download page, built and smoke-tested by CI
Google, Canva, GitHub, Notion and Linear move to “coming soon” while messaging gets the spotlight; real brand icons everywhere in Connections
Panels slide: settings panes and the account menu move cleanly instead of snapping
0.6.0 Beta
Premade interns, and sign-in that just works
The Bot directory puts twenty curated interns on a shelf — hire one in a click. Google and Canva now connect in one click too.
Bot directory: open it from the sidebar's grid button, the menu bar or the palette — browse by category, search, and Hire
Twenty premade interns across Work, Writing, Engineering, Money, Life and Research: Chief of Staff, Humanizer, Code Auditor, Fact Checker, Meal Planner and more — each arrives with its own standing rules
Directory hires are name-first like every other Bot: the name decides the job, the rules sharpen it, the look comes from the name's seed
One-click connect: Google and Canva sign-in uses BlazeBot's own app — click Connect, approve in the browser, done. No client IDs, no console
Canva scopes corrected to the real ones (design listing, export, profile) and its redirect now uses the localhost spelling Canva expects
Using your own developer project still works — it moved under “Use my own app instead” in Settings › Connections
0.5.0 Beta
Your interns, plugged into your tools
Connect Google, Canva, GitHub, Notion and Linear in Settings › Connections, and Bots gain real tools for each one.
Google: search and read Drive files, see the week's calendar, create events, search Gmail
Canva: list your designs and export them as PDFs
GitHub: search issues and pull requests, read files, open issues
Notion: search and read the pages you share with it
Linear: list issues and create new ones
Google and Canva sign in through your browser (OAuth); tokens live in the Keychain and refresh themselves
Reading a connected service is free; anything that changes something — an issue, an event, a calendar entry — asks first
Bring your own model — and updates that install themselves
Use BlazeBot with your own API keys, skip sign-in if you just want to look around, and never download an update by hand again.
New Settings › Providers: add any OpenAI-compatible service — OpenAI, OpenRouter, Groq, Together, DeepSeek, Mistral — or a model running on your Mac with Ollama or LM Studio
Your keys go straight into the macOS Keychain and are only ever sent to the provider you added
A Test button checks the URL, key and model with a real request before you save
Switch between BlazeAPI and your own providers any time in Settings › Models
“Skip for now” at sign-in — then sign in later from the sidebar, the account menu or Settings
Real auto-updates: BlazeBot checks for new builds, downloads them, verifies the SHA-256 checksum and relaunches itself