Hey everyone — I’m Brian Lee Baros (u/Crzbadboy77), creator of the SarahMemory AiOS and founding moderator of this community.

If you’re here, you’re part of the very first wave discovering something new:
an AI Operating System built from the ground up — local‑first, governed, self‑improving, and open‑source.

This subreddit exists for the builders, the tinkerers, the researchers, the curious minds, and anyone who believes AI should belong to the user, not the cloud.

🌐 What This Community Is About

This is the official hub for:

• SarahMemory AiOS development updates
• Architecture discussions (cognitive engine, governance, REM cycle, drivers, etc.)
• Feature requests & concept proposals
• Bug reports, testing, and feedback
• Showcases of custom frontends, integrations, and device builds
• Open‑source collaboration
• Deep technical breakdowns of how the AiOS works under the hood

Whether you’re a developer, researcher, hobbyist, or just curious — you’re welcome here.

🧠 What Makes SarahMemory Different

This project isn’t “another AI app.”
It’s the first system to introduce:

• A full cognitive architecture
• A governed execution layer (SMGET)
• A REM‑cycle dream engine for safe self‑improvement
• A local‑first model runtime
• A multi‑device OS ecosystem
• A driver layer for PLC, IoT, SIP, sensors, and more
• A media OS + avatar engine
• A self‑aware UI mapping system

If you want to explore the future of AI‑native computing, you’re in the right place.

📌 What to Post

You’re encouraged to share:

• Ideas for new AiOS features
• Technical questions
• Logs, screenshots, and experiments
• Custom drivers, addons, or UI panels
• Research related to cognition, governance, or local AI
• Hardware builds running SarahMemory
• Benchmarks, performance tests, or model comparisons
• Anything that pushes the system forward

If it helps the community grow or the OS evolve — post it.

🤝 Community Vibe

We keep things:

• Friendly
• Constructive
• Technical
• Open‑minded
• Collaborative

No ego. No gatekeeping.
We’re building something bigger than any one person.

🚀 How to Get Started

• Introduce yourself in the comments
• Share your first question, idea, or screenshot
• Invite anyone who loves local AI, OS design, or open‑source innovation
• If you want to help moderate or contribute, reach out

This is the beginning of a new category of computing — AIOS — and you’re here at the start.

🔥 Final Note

Thank you for being part of this early community.
SarahMemory AiOS is growing fast, and this subreddit will become the center of its ecosystem.

Let’s build the future of AI‑native operating systems together.

Welcome to r/SarahMemory.

SarahMemory AiOS by Brian Lee Baros , brand logo

SarahMemory AiOS — The First Fully Local, Governed, REM‑Cycle Open Source - 'FREE' - Donation Driven AI Operating System

By Brian Lee Baros — May 2026

(14 months of continuous development — 100% independent, 100% open‑source)

I built an AI Operating System that runs fully local, governs itself, manages its own cognition, and enters a REM sleep cycle where it safely hallucinates, self‑reflects, and self‑improves inside a sandbox.

This is not an agent.
Not a wrapper.
Not a chatbot.

This is a real AIOS — the first of its kind running on consumer hardware.

Nothing to sugar coat here, the system is being developed constantly and is in ver 8.0.0 framework - raw code development form, this system is a blueprint for all future Ai Operating Systems and beyond possibly even Quantum Ai Operating Systems.

1. What Is SarahMemory AiOS?

SarahMemory AiOS is a cross-platform local**‑first, decentralized, governed AI Operating System** designed to run on:

• desktops (Python, Windows/Linux/iOS/eventually soon its own Bootable OS system since it is own kernal)
• laptops
• tablets
• phones (Android/iPhones)
• LAN nodes
• hybrid cloud setups (headless Linux/Servers)
• (eventually robotics and more)

It is built around intelligence as the core, not as an add‑on. *add-on applications will be coming soon.

Key Principles

• User‑owned data
• Persistent local memory
• Model‑agnostic
• Offline‑capable
• Governed execution (SMGET)
• Self‑improving (REM engine)
• Modular, extensible, transparent

This is the opposite of cloud‑locked AI ecosystems.

2. Why Build an AI Operating System?

Because the current AI landscape is broken:

• Cloud lock‑in
• No persistent memory
• No transparency
• No local autonomy
• No OS‑level integration
• No safe self‑improvement

AI today is basically a smart webpage pretending to be a system.

SarahMemory AiOS is the next step:
AI as the OS itself.

3. Architecture Overview

SarahMemory AiOS includes:

3.1 Cognitive Architecture

• Multi‑lane reasoning (Analyst, Skeptic, Optimizer, Engineer, Governor)
• Cognitive graph (MeaningGraph‑like memory linking)
• Meta‑cognition (confidence, contradiction detection)
• Curiosity engine (gap detection + safe experiments)
• Semantic compression
• Ingress router and Cognitive Axis allows for (natural language → subsystem routing)

SarahMemory AiOS Cognitive Triforce

3.2 Governed Execution Layer — SMGET

SMGET = SarahMemory Governed Execution Technology

It enforces:

• sandbox‑first execution
• no hallucinated file writes
• no unauthorized system actions
• rollback‑ready operations
• strict policy enforcement
• assurance gate verification

SarahMemory AiOS , SMGET ensures safety

This is OS‑level AI safety, not prompt‑level safety.

3.3 Local‑First Model Runtime

• Supports 25+ models
• Multi‑stack (reasoning, coding, audio, video, embeddings)
• Automatic hardware ranking
• Token compression engine (10,000 → ~100 tokens)
• CUDA, CPU‑only, multiple fallback modes
• Built In File Manager , Virus/Malware Detector
• Backup/Restore system
• Self-Aware
• Self Evolution
• Self Diagnostics
• MCP Diagnostics
• Database bloat prevention
• P2P file transfer - Server API/MCP is a oneway broker for security
• VoIP video calling - coming soon
• SarahNet - allows each copy to become its own private node.

3.4 Device & Driver Layer

Over 30+ drivers, including:

• PLC/SCADA
• IoT/MQTT
• SIP/Telephony
• Cameras, microphones, HID
• Storage, networking, sensors
• Arduino/Uno

3.5 Avatar & Media OS

• 2D avatar (3D coming)
• MultiMedia pipeline [Create and Edit] (Image, Music, Video) with the SarahMemory CanvasStudio core files)
• Recording, animation, gesture engine
• LAN‑offloaded compute

4. The REM‑Cycle Dream Engine (Breakthrough)

This is the part that makes SarahMemory AiOS a true AIOS.

When idle, the system enters REM sleep, where it:

1. Generates hallucinated “dreams”
2. Scores them for risk
3. Runs them in a sandbox
4. Extracts useful learnings
5. Applies metadata‑only improvements

This is safe, governed self‑improvement.

4.1 Real Dream Categories (from logs)

• Self‑Study — map its own codebase
• Performance — find speed improvements
• Research — identify missing capabilities
• Learning Hygiene — dedupe memory entries
• Avatar Behavior — tune timing and interaction

4.2 Governance

Every dream passes:

• Governance Gate
• Assurance Gate
• Sandbox Trial
• Rollback Layer

Medium‑risk dreams require user approval.

4.3 What REM Does NOT Do

• No core file writes
• No unknown execution
• No external network calls without permission
• No bypassing governance

This is safe autonomy, not runaway AGI.

5. REM‑Cycle Diagram (ASCII)

Code

                   ┌──────────────────────────┐
                   │   SarahMemory AiOS Idle   │
                   └──────────────┬───────────┘
                                  │
                                  ▼
                     ┌────────────────────────┐
                     │   REM Dream Generator   │
                     │ (hallucinated ideas)    │
                     └──────────────┬─────────┘
                                    │
                                    ▼
                     ┌────────────────────────┐
                     │   Governance Gate       │
                     │  (risk scoring, policy) │
                     └──────────────┬─────────┘
                                    │
                     ┌──────────────┴──────────────┐
                     │                               │
                     ▼                               ▼
        ┌──────────────────────┐         ┌────────────────────────┐
        │  Sandbox Execution    │         │   Deferred (User Req.) │
        │ (no core file writes) │         │   Medium‑risk dreams   │
        └──────────────┬───────┘         └────────────────────────┘
                        │
                        ▼
          ┌────────────────────────────┐
          │  Assurance Gate (Verify)   │
          └──────────────┬────────────┘
                         │
                         ▼
          ┌────────────────────────────┐
          │ Metadata‑Only Learning     │
          │ (indexes, maps, heuristics)│
          └────────────────────────────┘

6. Real REM Logs (Summary)

From the logs:

• 5 dreams generated
• 4 auto‑applied (metadata‑only)
• 1 deferred (requires user)
• 0 core file modifications
• All sandbox trials passed
• Assurance Gate confidence: 0.92

This is the first documented case of a consumer‑hardware AIOS performing safe REM‑cycle cognition.

7. Why This Matters

SarahMemory AiOS proves:

• AI can self‑improve safely
• AI can run fully local
• AI can be governed at the OS level
• AI can operate across devices
• AI can be transparent and user‑owned

This is the beginning of AI‑native computing.

Not apps.
Not agents.
Not wrappers.

Operating systems built around intelligence.

8. What’s Next

• 3D avatar engine
• SCADA/IoT expansion
• Telecom/SIP automation
• Self‑generating UI panels
• Bootable AiOS builds
• Automatic model update/rollback
• Full mesh networking

9. Final Thoughts

I built this system alone over 14 months.
No funding.
No team.
No corporate backing.

Just engineering, obsession, and a belief that AI should belong to the user, not the cloud.

Here is a current and actual Screenshot of the system.

SarahMemory AiOS screenshot 05-07-2026 while running locally

SarahMemory AiOS is real.
It’s running today.
And it’s open‑source.

*Updates are done frequently on GitHub and Updates are posted in the README.MD

If you want to follow, contribute, or test — welcome aboard.

SarahMemory AiOS VS Code Extension

SarahMemory-first VS Code chat, workspace, runtime, and built-in Chat participant integration for a running SarahMemory AiOS instance.

What this build does

This revision makes SarahMemory a first-class part of VS Code in two surfaces:

• a dedicated SarahMemory Activity Bar sidebar chat/runtime surface
• a built-in VS Code Chat participant available as u/sarahmemory

It also:

• launches python SarahMemoryMain.py automatically when VS Code starts
• seeds VS Code settings automatically with SarahMemory defaults
• defaults the SarahMemory API base URL to http://127.0.0.1:8000
• sends active file content and workspace file context automatically with chat requests
• surfaces SarahMemory health, routing, notes, and runtime diagnostics live in the sidebar UI
• discovers local model folders under C:\SarahMemory\data\models and exposes them in a quick-swap selector
• discovers API key presence from .env and OS environment variables so you do not need to re-enter them in the extension
• provides a terminal-task launcher and an agent-task chat launcher inside the SarahMemory chat surface
• contributes a sticky chat participant with slash commands:
  • u/sarahmemory /health
  • u/sarahmemory /models
  • u/sarahmemory /agent
  • u/sarahmemory /terminal

Important runtime note

This extension uses your SarahMemory runtime as the chat backend. The sidebar chat replies through SarahMemory, and the built-in VS Code Chat participant routes prompts into SarahMemory as well, and Swap between Cloud-Based API's, the Local API and Different Local Models instantly.

Visual Studio Code -SarahMemory AiOS extension - can even launch SarahMemory AiOS from the VS Code Terminal

https://preview.redd.it/z1m4ok7q3tzg1.jpg?width=3840&format=pjpg&auto=webp&s=72641c62e590a6e65dcd07513fcad35a25b6e1d0

SarahMemory AiOS Visual Studio Code Extension allows you to hot swap Cloud based API's

SarahMemory AiOS , Visual Studio Code extension allows to hotswap Local Models on your own PC system.

This is the future of computing.

https://github.com/Brian-Baros/SarahMemory

r/SarahMemory

#thesarahmemoryproject

This is a free, open-source and donation driven project, please feel free to donate, that will assist in continuing development.

Donations <-Click here to Donate

SarahMemory AiOS banner

LICENSE (SMLC v1.0)

https://github.com/Brian-Baros/SarahMemory/blob/main/LICENSE

https://preview.redd.it/epo1m8iieszg1.png?width=2172&format=png&auto=webp&s=db2214d4185cb08c8d2e7191d69f8247793e31ce

I built an AI Operating System that runs fully local, governs itself, manages its own cognition, and enters a REM sleep cycle where it safely hallucinates, self‑reflects, and self‑improves inside a sandbox.

This is not an agent.

Not a wrapper.

Not a chatbot.

This is a real AIOS — the first of its kind running on consumer hardware.

1. What Is SarahMemory AiOS?

SarahMemory AiOS is a local‑first, decentralized, governed AI Operating System designed to run on:

• desktops
• laptops
• tablets
• phones
• LAN nodes
• hybrid cloud setups

It is built around intelligence as the core, not as an add‑on.

Key Principles

• User‑owned data
• Persistent local memory
• Model‑agnostic
• Offline‑capable
• Governed execution (SMGET)
• Self‑improving (REM engine)
• Modular, extensible, transparent

This is the opposite of cloud‑locked AI ecosystems.

2. Why Build an AI Operating System?

Because the current AI landscape is broken:

• Cloud lock‑in
• No persistent memory
• No transparency
• No local autonomy
• No OS‑level integration
• No safe self‑improvement

AI today is basically a smart webpage pretending to be a system.

SarahMemory AiOS is the next step:
AI as the OS itself.

3. Architecture Overview

SarahMemory AiOS includes:

3.1 Cognitive Architecture

• Multi‑lane reasoning (Analyst, Skeptic, Optimizer, Engineer, Governor)
• Cognitive graph (MeaningGraph‑like memory linking)
• Meta‑cognition (confidence, contradiction detection)
• Curiosity engine (gap detection + safe experiments)
• Semantic compression
• Ingress router (natural language → subsystem routing)

3.2 Governed Execution Layer — SMGET

SMGET = SarahMemory Governed Execution Technology

It enforces:

• sandbox‑first execution
• no hallucinated file writes
• no unauthorized system actions
• rollback‑ready operations
• strict policy enforcement
• assurance gate verification

This is OS‑level AI safety, not prompt‑level safety.

3.3 Local‑First Model Runtime

• Supports 25+ models
• Multi‑stack (reasoning, coding, audio, video, embeddings)
• Automatic hardware ranking
• Token compression engine (10,000 → ~100 tokens)
• CUDA, CPU‑only, fallback modes

3.4 Device & Driver Layer

Over 30+ drivers, including:

• PLC/SCADA
• IoT/MQTT
• SIP/Telephony
• Cameras, microphones, HID
• Storage, networking, sensors

3.5 Avatar & Media OS

• 2D avatar (3D coming)
• Media pipeline
• Recording, animation, gesture engine
• LAN‑offloaded compute

4. The REM‑Cycle Dream Engine (Breakthrough)

This is the part that makes SarahMemory AiOS a true AIOS.

When idle, the system enters REM sleep, where it:

1. Generates hallucinated “dreams”
2. Scores them for risk
3. Runs them in a sandbox
4. Extracts useful learnings
5. Applies metadata‑only improvements

This is safe, governed self‑improvement.

4.1 Real Dream Categories (from logs)

• Self‑Study — map its own codebase
• Performance — find speed improvements
• Research — identify missing capabilities
• Learning Hygiene — dedupe memory entries
• Avatar Behavior — tune timing and interaction

4.2 Governance

Every dream passes:

• Governance Gate
• Assurance Gate
• Sandbox Trial
• Rollback Layer

Medium‑risk dreams require user approval.

4.3 What REM Does NOT Do

• No core file writes
• No unknown execution
• No external network calls without permission
• No bypassing governance

This is safe autonomy, not runaway AGI.

5. REM‑Cycle Diagram (ASCII)

Code

                   ┌──────────────────────────┐
                   │   SarahMemory AiOS Idle   │
                   └──────────────┬───────────┘
                                  │
                                  ▼
                     ┌────────────────────────┐
                     │   REM Dream Generator   │
                     │ (hallucinated ideas)    │
                     └──────────────┬─────────┘
                                    │
                                    ▼
                     ┌────────────────────────┐
                     │   Governance Gate       │
                     │  (risk scoring, policy) │
                     └──────────────┬─────────┘
                                    │
                     ┌──────────────┴──────────────┐
                     │                               │
                     ▼                               ▼
        ┌──────────────────────┐         ┌────────────────────────┐
        │  Sandbox Execution    │         │   Deferred (User Req.) │
        │ (no core file writes) │         │   Medium‑risk dreams   │
        └──────────────┬───────┘         └────────────────────────┘
                        │
                        ▼
          ┌────────────────────────────┐
          │  Assurance Gate (Verify)   │
          └──────────────┬────────────┘
                         │
                         ▼
          ┌────────────────────────────┐
          │ Metadata‑Only Learning     │
          │ (indexes, maps, heuristics)│
          └────────────────────────────┘

6. Real REM Logs (Summary)

From the logs:

• 5 dreams generated
• 4 auto‑applied (metadata‑only)
• 1 deferred (requires user)
• 0 core file modifications
• All sandbox trials passed
• Assurance Gate confidence: 0.92

This is the first documented case of a consumer‑hardware AIOS performing safe REM‑cycle cognition.

7. Why This Matters

SarahMemory AiOS proves:

• AI can self‑improve safely
• AI can run fully local
• AI can be governed at the OS level
• AI can operate across devices
• AI can be transparent and user‑owned

This is the beginning of AI‑native computing.

Not apps.
Not agents.
Not wrappers.

Operating systems built around intelligence.

8. What’s Next

• 3D avatar engine
• SCADA/IoT expansion
• Telecom/SIP automation
• Self‑generating UI panels
• Bootable AiOS builds
• Automatic model update/rollback
• Full mesh networking

9. Final Thoughts

I built this system alone over 14 months.
No funding.
No team.
No corporate backing.

Just engineering, obsession, and a belief that AI should belong to the user, not the cloud.

SarahMemory AiOS is real.
It’s running today.
And it’s open‑source.

If you want to follow, contribute, or test — welcome aboard.

This is the future of computing.

https://github.com/Brian-Baros/SarahMemory

https://preview.redd.it/v36fvy3wlrzg1.png?width=3840&format=png&auto=webp&s=37abe4b1d6efe11862e946f97f560def565a08b9

The screenshot isn’t a mockup.
It isn’t generated.
It isn’t a concept.

It’s a live shell capture of the SarahMemory AiOS system — a fully local, fully autonomous, AI‑native operating system I’ve been building for the last 14 months.

I’m currently pushing the limits of a single workstation UI just to fit all the active subsystems on screen at once:
Model Weight Controller
Deep Learning Engine
Cognitive Trace / Thinking Process
Governance & Assurance Gate
Subject Boxes / Concept Generator
Research Browser
Media Player
Avatar Engine (2D now, 3D coming)
SarahNet (multi‑node communication)
This isn’t a chatbot.
This isn’t an agent wrapper.
This is an AI Operating System.

What SarahMemory AiOS Can Do Today
Runs 100% locally
Reads and processes all local files, images, and data
Has a functional REM/Sleep Mode where it hallucinates, self‑reflects, and self‑tunes inside a sandbox
Performs self‑diagnostics, self‑optimization, and environmental learning
Uses a strict governance + assurance gate to filter hallucinations into useful improvements
Includes a growing library of 30+ device drivers, including PLC/SCADA integrations
Has a dedicated logic/physics/mathematics engine (SarahMemoryLogicCalc.py) that already surpasses what most universities teach at the undergraduate level

Why This Matters
The world is still trying to bolt AI onto legacy operating systems.
But Windows, macOS, and Linux were never designed for:
autonomous reasoning
vector memory
multimodal cognition
self‑improving systems
distributed intelligence
AI isn’t a feature anymore — it’s the foundation.
SarahMemory AiOS is my attempt to build the next era of computing for the generation growing up in an AI‑first world.

Open‑Source & Growing
Yes — this is real, it’s open‑source, and it’s evolving fast.
I’m building it alone right now, but the vision is bigger than me.
If you’re interested in:
AI systems
OS design
SCADA/IoT integration
autonomous agents
cognitive architectures
open‑source AI infrastructure
…then this project is for you.

The future of computing won’t be defined by apps.
It will be defined by AI operating systems.
And SarahMemory AiOS is one of the first.

I’m a Gen‑X engineer who grew up on cassette‑tape storage, TRS‑80s, Apple IIs, DOS 6.22, WWIV BBS systems, and 386 hardware. I’ve watched every major computing era unfold in real time.

And here’s the truth:

The classic OS model is done.

Windows, macOS, Linux — they’re incredible, but they were built for a pre‑AI world. They’re trying to bolt intelligence onto architectures that were never designed for it.

AI isn’t a plugin.
AI isn’t a chatbot.
AI isn’t an “agent.”

AI is the new kernel.

That’s why I’m building SarahMemory AiOS — a fully AI‑native operating system with:

• vectorized memory
• autonomous modules
• REM‑style self‑improvement cycles
• distributed cognition
• multimodal pipelines
• a real boot sequence
• a real OS architecture
• open‑source code
• and a long‑term roadmap

This isn’t another “AI wrapper.”
This is an attempt to build the next generation of operating systems from the ground up.

If you want to help, contribute, test, or just follow the journey, the project is open on GitHub. I’m building this alone right now, but I believe the future belongs to AIOS — not chatbots, not agents, not wrappers.

If you’re tired of the hype and want to build the real future, welcome aboard.

The SarahMemory AiOS is now building and using REM sleep to enhance coding while the system is in Idle, Self-programming, Self-refinement, Self-diagnostics, and much much more. r/SarahMemory