GISMO v0.5.0-beta.1 - The Command Center Goes Operational

Mike Burns — Thu, 19 Mar 2026 17:16:32 +0000

A few days ago I wrote about building GISMO — a local-first AI orchestration system — on a 7-year-old laptop.

v0.5.0-beta.1 just dropped. Here's what changed, and why it matters.

The short version

Phases 0 through 3 are done. Phase 4 — the interactive experience — has started. This beta is the first release where GISMO's command center starts behaving like an operator shell instead of a UI bolted onto backend plumbing.

What phases 0–3 built

Phase 0 — SQLite-backed state, queue, daemon, IPC, JSONL audit trail
Phase 1 — Ollama integration, local LLM planner, ask pipeline
Phase 2 — Deterministic risk classification (LOW / MEDIUM / HIGH), deny-by-default policy enforcement, approval gating
Phase 3 — Persistent memory store, context injection, conversation profiles

All of that is the engine. Phase 4 is what you actually drive.

What's new in v0.5.0-beta.1

Desktop command center is live

gismo app now launches a native desktop application with a three-column command center layout and a real top menu bar — File, System, Devices, Automation, Settings, Help. Settings surface includes operator-facing controls: voice selection, model selection, and more.

It finally looks like something I'd want to leave open on a second monitor.

Chat routes to real execution

This is the one I'm most pleased about.

Previously, chat requests would report success before execution actually completed. The UI was lying to you. That's gone.

Operational chat requests now route into the full pipeline:

chat input → planning → approval → queue → worker → tool/action → state update → UI refresh → spoken/text result

GISMO won't tell you something happened until it actually happened. I work around industrial robots. Silent failures and false positives are how things go wrong.

Calendar is operational

There's a Calendar tab in the app now. Calendar actions execute through the actual queue/worker/tool path — not local UI state. GISMO's calendar is part of its operational timeline, not a sticky note widget.

Truthful system surfaces

"This computer" now reflects actual host state. The network panel separates LAN state from internet reachability. The boot flow is tied to real startup state instead of a cosmetic progress bar.

GISMO should never tell you it's ready when it isn't.

What the full stack looks like right now

These pieces are working together:

SQLite-backed state, queue, runs, tasks, and memory
Local Ollama-backed GISMO model
TTS voice output
Desktop app, web dashboard, and TUI
Approval-gated planning
Queue/worker execution
Calendar and command center surfaces

What's still missing

This is a beta. Known gaps:

Device connection and capability binding still incomplete
Protocol adapters for real device control still being written
Onboarding needs full in-window polish
Daemon auto-start not wired up yet
Adaptive model policy (routing based on weak vs. strong hardware) still being refined

What's next

Device capability binding and protocol adapters
Tighter operational state model beyond generic READY
Full in-app onboarding flow
Daemon auto-start
Adaptive model policy and deterministic request routing improvements

The longer horizon is still the same: GISMO as a universal device orchestration layer. Drones, RC vehicles, industrial peripherals, humanoid robots — all operating under the same policy-gated, auditable framework that governs file operations today.

Try it

GitHub: https://github.com/GISMO-1/GISMO
Release: v0.5.0-beta.1
License: MIT

If you're building in the local-first AI space or have thoughts on device orchestration and policy models — drop it in the comments.

I'm building a personal AI that runs locally, owns nothing to the cloud, and answers only to you.

Mike Burns — Sat, 14 Mar 2026 19:53:10 +0000

I work full time running industrial robots at a glass factory.
I've been in school since 2003. I just finished.
In my spare time I've been quietly building something called GISMO.

The end game is simple: a fully local AI that knows you, runs on
your hardware, manages your digital life, executes tasks, remembers
everything — and never phones home.

Not a subscription. Not a cloud service. Not someone else's brain
that you're renting. Yours.

The problem with every AI assistant right now

Every AI assistant you use today lives on someone else's server.
It learns from you. It reports to them. You don't own it.

I run real industrial robots for a living. I know what happens when
machines do unexpected things without the operator knowing. That
experience is baked into everything I've built.

The core philosophy: policy before power. No silent actions.
Everything auditable.

What GISMO is today

GISMO (General Intelligent System for Multiflow Operations) is a
local-first autonomous orchestration system. It uses Ollama to run
a local LLM entirely on your own machine.

What's already built and working:

Local LLM brain — Ollama integration, model-agnostic, zero cloud
Durable task engine — queue, daemon, state machine, resume-safe
Full audit trail — every decision logged with receipts and hashes
Deterministic risk classification — every plan rated LOW / MEDIUM / HIGH before anything runs
Policy-gated memory — persistent SQLite memory, operator-controlled writes only
Supervisor lifecycle — up, down, recover, always-on service behavior
Windows-first — because real people use Windows
Leashed autonomy — the agent can only act through the same policy gates as the operator

Current status

✅ Phase 0 — Foundation
✅ Phase 1 — Local LLM Planner
✅ Phase 2 — Control & Guardrails
🔄 Phase 3 — Memory & Context (in progress)
🎯 Phase 4 — Interactive GISMO (the end game)

The hardware reality

I built all of this on a 7-year-old laptop while working full time.

That's part of the point. GISMO is designed to run on whatever
you have. No GPU farm. No cloud credits. Just Python and Ollama.

This is just the beginning

Phase 4 is where it all comes together. Always-on. Knows you.
Executes for you. Remembers everything. Runs locally.
Answers to you alone.

Not Alexa. Not Siri. Not Copilot. Not anyone's cloud product.

Just yours.

GitHub: https://github.com/GISMO-1/GISMO

What would you do with a personal AI that was actually yours?

DEV Community: Mike Burns