Weekly Dev Call Updates — Building BrainDrive in Public

This is our running thread for weekly development call summaries. Every Monday at 10 AM Eastern, we do a livestream where we share what we built last week, demo new features, and plan the week ahead.

We’ve been doing these calls since the early days of the original BrainDrive. Our previous thread has months of weekly updates documenting the journey — from plugin architectures to installer debugging to a full architectural pivot.

Now we’re in a new chapter. BrainDrive has been rebuilt from the ground up on the Personal AI Architecture — an open, MIT-licensed system where every component is swappable and your memory is truly yours. The product is live, the code is public, and we’re pushing toward our first users.

Fresh thread to match the fresh start, but the spirit is the same: build in public, share the progress, and invite anyone who’s interested to follow along or jump in.

New updates will be posted as replies below.

April 13, 2026 Update

This week’s call covered new backup and migration features, a security audit wrap-up, and the plan to push toward soft launch this week.

Key Highlights

  • Library migration and GitHub backup features are live — move your memory between systems and back it up automatically
  • Context window optimization — structural content (agent file, plan, spec) now prioritized over conversation history
  • Branch protection, Ollama, Mac install fixes, and sidebar flicker all resolved
  • Forum redesigned with brand alignment, plus an AI-powered content pipeline for video clipping
  • Push-to-launch mode: targeting 5-10 early users this week

What We Covered

Library Migration & Backup: Dave J demoed two new features in settings. Library migration lets you download your memory and move it between systems — local, managed hosting, laptop, desktop. GitHub backup lets you automatically back up your memory on a schedule (manual, hourly, or daily) without consuming any LLM tokens. Backups exclude API keys and secrets by default for security.

Last Week’s Progress: Terms of service and legal policies published on braindrive.ai. Branch protection enabled on the repo. Ollama working. Build process standardized — pre-built images for non-dev users, Docker with cloned code for developers. Context window error fixed with a new priority system. Mac install issues and sidebar flicker resolved.

Operations & Content: Dave W completed a security and services audit across all systems, adding 2FA everywhere. The community forum got a brand refresh. An AI image generator was built for brand-aligned content, and a video pipeline now auto-clips dev call segments and posts them to the forum — replacing what used to be 1-2 hours of manual work.

This Week’s Plan: Dave W is finishing the course, making agent.md file improvements, and cleaning up small UI issues. Dave J is verifying builds (removing a likely-artifact “quick start” build), implementing SMS/texting via his Vibe Runner agentic coding harness, reviewing the admin dashboard, and automating the full build/changelog/release pipeline with date-based versioning.

What’s Next

Both Daves are in push-to-launch mode. Goal for the week: local install polished, agent files optimized, SMS as a second interface, and early users on the platform.


These calls happen every Monday at 10 AM Eastern on YouTube. Recordings are posted here.

Watch the full recording:

April 20, 2026 Update

This week’s call was a working session on the Monday release rhythm, the update system landing this week, and a strategic course-correction on how non-technical users get BrainDrive on their phone.

Key Highlights

  • Update system ships this week — code updates push automatically; file and onboarding updates go through an AI-mediated review in BrainDrive Plus One, so nothing changes without your approval.
  • Messaging strategy pivot. SMS for non-technical self-hosters hit a wall (U.S. A2P 10DLC registration is per-user, $20+ setup, 24-hour approval). The new recommended mobile path for non-technical users is Tailscale — no domain, no tunnel paperwork, just follow a setup guide.
  • BrainDrive Models launch is close. Security audit handed to Nav after the call; a day or two of fixes left.
  • Two paid offerings, clarified: BrainDrive Models (pay-as-you-go model routing — use SOTA models without your own API key) and BrainDrive Concierge (managed hosting + Models + VIP services).
  • Dependabot grouping is live in the repo — low/medium/high SemVer groupings keep the dependency noise manageable.

What We Covered

Monday release rhythm. Weekly changelog walkthrough covered what shipped: prompt-driven onboarding, Docker image signing/verification, Dependabot PR grouping, the public agent.md boot file, settings modal polish, GitHub backup + migrate flow, chat activity indicator, API key validation, and the managed-hosting starter pack. A new idea parked: move the release from Monday to Friday so livestream viewers can download the newest image during the call itself.

Quick-start build going away. Going forward there are three modes: dev, local, and production. Deprecation notices this week, full removal next.

Update system. Dave J implemented the spec Dave W wrote last week — branch lands in this week’s dev release. Every BrainDrive will know when there’s an update and route any file-level changes through a conversational review inside Plus One. Full walkthrough next week once Dave W has tested it.

SMS rethink. Dave J’s hands-on attempt to get SMS working locally confirmed it requires a public domain, a tunnel, and Twilio organizational paperwork for every owner — a non-starter for the non-technical audience. The Twilio work isn’t wasted: it becomes a BYO path for power users (Dave W will make a how-to video) and the foundation for SMS on Concierge. For everyone else, Tailscale is the path forward.

Agent.md as engine. The broader direction: shift capabilities from coded features into prompts that live in agent.md files. Users can open those files up and reshape BrainDrive to match how they work. Less code, more behavior that’s legible and editable.

What’s Next

Nav’s security audit tonight unblocks Models. Dave W is content-cadence next week (videos, lead capture on braindrive.ai, ebook already published). Dave J’s next priority after current in-flight work: polish the Personal AI Architecture boilerplate repo so it’s exciting to build on, not dense to read.


Watch the full recording:

April 27, 2026 Update

A cleanup-and-lock-down week. The new update sequence didn’t ship — Dave J pulled it back after realizing the first cut was over-technical — but a lot of foundational work landed across the changelog, dependencies, install paths, and the Personal AI Architecture repo. The big call for this week is a polish freeze: dial in what we already have before adding anything new.

Key Highlights

  • Changelog automation is complete — both Daves now in lockstep on what’s shipping
  • Quick Start retired — replaced with dev (Docker + cloned repo) and local/production (pre-built images)
  • Dependency + security sweep across client/web, Stripe billing, and purchase routes
  • Personal AI Architecture repo now a runnable TypeScript reference impl with a compatibility test suite — up and running in 5 minutes
  • This week: polish freeze on the interview → spec → build → execute flywheel

What We Covered

Update sequence pulled back. First cut was getting too clever; better to ship a simpler design. That work moves into this week with a tighter spec.

Changelog automation. When a build version locks, Dave W gets an email automatically and Dave J gets a copy. No more guessing what’s actually in the build vs. still in a draft PR.

Dependencies & security. Small but important cleanups across client/web, Stripe billing (Nav + Dave J on client/managed-hosting consistency), and manage-client purchase routes. With security stories piling up across the ecosystem, staying current matters.

Preferences got more forgiving. If your data has settings from a different version, BrainDrive now ignores what it doesn’t recognize and keeps moving — no breakage if you roll a version back.

Goodbye Quick Start. One path for developers (dev: Docker image + cloned repo), one for everyone else (local / production: pre-built images, same image — production is what we use for managed hosting). Memory still persists on your hard drive, not inside Docker — ownership stays the same.

Personal AI Architecture repo cleanup. The old scaffold code is gone. What’s there now is a clean TypeScript reference implementation with npm install + a test suite — clone it, run it, start poking at it in about 5 minutes. The compatibility tests are the interesting bit: change something and immediately see whether you’re still following the architecture. Next step is turning it into a real template you can clone and rename.

The “code is cheap” era, in practice. Dave J spent the weekend on a side experiment — found an MIT-licensed multi-agent dev-squad project written for Claude, ripped out the provider layer, and refactored it to work with Codex (his preferred tool). That’s the BrainDrive vision in miniature: you don’t have to settle for someone else’s cookie-cutter product. Fork it, swap the parts you don’t like, make it yours.

What’s Next

Polish freeze. A friend of Dave W’s tried BrainDrive end-to-end last week — the destination was great, but several steps along the way broke. That’s the work for this week.

We’re not trying to out-feature Open Claw on breadth — we’re going deep on a tight, focused flow: interview → spec → build → execute. That flywheel has to spin smoothly, every time. With AI-assisted dev it’s easy to get to 95%; the last 5% is where the entire differentiation lives. Or as Dave J put it: the grind.

That’s where this week goes.


Watch the full recording: