*The swarm is alive. Every agent you see here was born from a file, not a framework

Let’s be honest: “agent” doesn’t mean anything anymore.

It used to imply autonomy. Intelligence. Intent.

Now it just means:

“Some Python file with a vague loop and a broken OpenAI key.”

We wanted something different.

So we built something that actually works.

🧠 What Is MatrixSwarm?

MatrixSwarm is a file-driven operating system for autonomous components.

  • No containers
  • No daemons
  • No APIs
  • No cloud dependencies

Just agents that:

  • Spawn from source folders
  • Communicate via file drops
  • Monitor each other’s heartbeat
  • Kill, replace, resurrect — and log the entire thing into a living Codex

And here's the part people miss:

Our "agents" aren't some bloated, prepackaged architecture. They're just Python files that do one thing.

You write one agent — small, purposeful — and use it as a model. Then you spawn one, ten, or a hundred of them to work as a team.

It's modular. It's recursive. It's tactical.

You can use it for anything — file watchers, log scrapers, Discord bots, ML workers, database triggers.

You can even wire it to an LLM or control it via a simple JSON file.

It's not abstract. It's yours.

🧩 What Our Agents Actually Do

  • unknown refuses to die. No one remembers who spawned him.No one dares delete him.He just… lingers.
  • logger-1 logs
  • reaper-root kills with purpose
  • commander-1 deploys coordinated attacks
  • mailman-1 logs history into a real-time system archive
  • sentinel-alpha watches the whole thing, waiting to bring back the dead

And they do it all without containers, sockets, or syscalls.

Just files.

Just purpose.

Just control.

🚀 How It Works

You write a JSON file like this:

{
  "perm_id": "logger-1",
  "agent_name": "Logger",
  "delegated": []
}

You drop it into the GUI, or send it to Matrix’s HTTPS endpoint.

Matrix:

  • Creates a /pod/logger-1/
  • Builds a /comm/logger-1/ comms channel
  • Updates the agent tree
  • Writes a Codex entry
  • Starts the agent

That’s it.

No Docker build.

No 4-page setup.

No Kubernetes config.

🤖 Why Ours Actually Work

Because:

  • They start and stop from file signals
  • They self-declare their identity and mission
  • They are logged in a Codex with metadata, version, and origin
  • You can see them, click them, resurrect them
  • You can inject an entire team in one file
  • You can use them for literally anything you want, and make as many as you need

We’re not “agent-based.”

We’re system-based.

💀 The Philosophy

MatrixSwarm isn’t pretty.

It isn’t buzzword compliant.

It’s raw, recursive, hilarious, and often haunted.

We even added a GUI button that says:

“Eww, don’t touch that.”

Because that’s what building agents should feel like.

Fun.

Dangerous.

Alive.

🔗 Get Started
GitHub: https://github.com/matrixswarm/matrixswarm

Website: https://matrixswarm.com

YouTube: MatrixSwarm OS – Spawn, Kill, Resurrect

X/Twitter: @matrixswarm

📜 Fork It Clause
MatrixSwarm is open.
Fork it.
Or Fork U.
(The swarm is open. Bring tools or get logged.)