JSPM

memoryblock is a lightweight framework for running isolated AI workspaces as local background workers. Instead of spinning up monolithic chatbots, you provision dedicated workspaces called blocks — each with its own monitor, memory, tools, and execution loop.

A devops block watches your servers. A research block scrapes and summarizes data. A home block coordinates everything. They run independently — no shared state, no crossed wires.

Terminology

Memoryblock uses specific terms that mean different things than the typical AI landscape. Understanding these will help you navigate the system:

Founder (you)
└── Block: home
    └── Monitor: 🤖 Nova  ← the AI running inside this block
        ├── Agent: "research"  ← temporary sub-task worker
        └── Agent: "writer"   ← another temporary worker

Monitors are persistent — they remember everything across sessions. Agents are disposable — they exist only for the task that spawned them.

Why Memoryblock?

Get Started in 60 Seconds

npm install -g memoryblock   # or: bun install -g memoryblock
mblk init                    # guided setup — pick your LLM provider
mblk start home              # your first monitor is running

That's it. You have a running monitor with persistent memory, file access, and a web dashboard.

Bun users: When available, mblk automatically uses Bun for ~2x faster startup. Works perfectly on Node.js too.

Talk to Your Monitor

Blocks are decoupled from the interface. Use whatever channel fits your workflow:

mblk start home                     # interactive CLI chat
mblk start home -d                  # background daemon mode
mblk start home --channel telegram  # route to Telegram
mblk web                            # web dashboard at localhost:8420

Built-In Tools

Every block ships with 30+ built-in tools — no plugins required:

Extend with Plugins

mblk add web-search     # SERP querying via Brave Search
mblk add fetch-webpage  # Extract and chunk web page content
mblk add agents         # Sub-agent orchestration
mblk add aws            # AWS service tools

Plugins auto-install if missing — when you create a block and select capabilities, memoryblock installs what's needed.

Token Efficiency

Memoryblock is designed from the ground up to minimize token consumption:

Monitor → Agent Orchestration

Monitors can spawn agents for parallel work:

Monitor: 🤖 Nova (home block)
├── create_agent("research", "Find pricing for competitor X")
├── create_agent("writer", "Draft the comparison doc")
├── query_agent("research")  → gets results
├── message_agent("writer", "Here's the data from research...")
└── terminate_agent("research")  → cleanup

Agents run in the block's agents/ directory with their own isolated context. The monitor can message them asynchronously without blocking its own conversation. Agents are ephemeral — they can't create other agents, and they have a limited tool set compared to the monitor.

Background & Scheduling

Run blocks as background daemons with built-in cron scheduling:

mblk start ops-monitor -d          # daemon mode
mblk service install                # auto-start on boot (launchd / systemd)

Your monitor can schedule its own tasks:

"Schedule a cron job: check server health every hour"
→ schedule_cron_job("health-check", "0 * * * *", "Run uptime check on production servers")

The Pulse engine runs autonomously in the background, executing instructions without consuming LLM tokens unless explicitly configured to alert the monitor.

Permissions & Security

Blocks are sandboxed by default. Elevate only when needed.

mblk superblock ops-monitor        # grant full access
mblk superblock ops-monitor --off  # revoke

Interactive tool approval: When a monitor tries to run a command, you see exactly what it wants to execute and approve or deny — in the CLI, web dashboard, or Telegram.

Commands

How It Works

~/.memoryblock/ws/
├── config.json          # global settings
├── auth.json            # provider credentials
├── founder.md           # your profile (shared across blocks)
└── blocks/
    ├── home/
    │   ├── config.json  # block settings, adapter, permissions
    │   ├── monitor.md   # monitor identity and personality
    │   ├── memory.md    # persistent context across sessions
    │   ├── session.json # crash-recovery session state
    │   ├── pulse.json   # autonomic background pulse instructions
    │   ├── agents/      # ephemeral sub-agent workspaces
    │   │   ├── research/
    │   │   │   ├── config.json  # sandboxed config
    │   │   │   ├── memory.md    # agent memory
    │   │   │   ├── inbox.md     # async messages from monitor
    │   │   │   └── logs/
    │   │   └── writer/
    │   │       └── ...
    │   └── logs/        # full conversation history
    └── ops-monitor/
        └── ...

Each block is fully self-contained. Back up a monitor by copying its folder. Move it to another server by pasting it. No databases, no migrations.

Architecture

Modular TypeScript monorepo with strict dependency boundaries:

How We Compare

What's Coming

We ship 2-3 features per release. Here's what's next:

• Add Adapters : Ollama adapter (local models), OpenRouter, DeepSeek, and Groq
• Add Tools : Vision/Image tools, Process management
• Add Plugins : Broswer plugin
• Add Channels : Discord, Slack, and WhatsApp
• MCP protocol support

Contributing & Support

We welcome PRs! See CONTRIBUTING.md.

If memoryblock is useful to you, consider sponsoring the project or giving it a ⭐.

The memoryblock Ecosystem

memoryblock is a highly modular system. Here are the official packages:

The Core

• memoryblock - CLI orchestrator and command routing.
• @memoryblock/core - Engine runtime, memory manager, gatekeeper.
• @memoryblock/types - Shared TypeScript definitions and schemas.
• @memoryblock/locale - Localization strings and utilities.

Integrations & Tooling

• @memoryblock/adapters - LLM provider adapters (OpenAI, Anthropic, Bedrock, etc).
• @memoryblock/channels - Communication channels (CLI, Telegram, Web).
• @memoryblock/tools - Tool registry and built-in definitions.
• @memoryblock/daemon - Background process spawner and manager.
• @memoryblock/api - HTTP/WebSocket API server.
• @memoryblock/web - Front-end dashboard static files.

Plugins

• @memoryblock/plugin-installer - Plugin installer and registry manager.
• @memoryblock/plugin-agents - Secondary AI agents orchestrator.
• @memoryblock/plugin-aws - AWS integrations.
• @memoryblock/plugin-fetch-webpage - Web content fetching and parsing.
• @memoryblock/plugin-web-search - Web search capabilities.

License

Distributed under the MIT License. See LICENSE for more information.