I really think I found something interesting for the future of Agent0, so in this thread I share some of the chaos. Started one way, switching Agent0, Pear Runtime and Hyperswarm = <3 Pivoting from "Fully autonomous machine-control swarm" idea to A private, encrypted multiplayer mode for Agent Zero idea The Pitch - You run your agent locally (like always) - You join a topic/swarm with people you trust - Your agents share research, split tasks, pool knowledge - Everything stays off corporate servers ______________________________ Current state ( older, going towards Fully autonomous machine-control swarm ) Agent Zero: SwarmOS Edition A decentralized, serverless agent swarm powered by Agent0, Pear Runtime and Hyperswarm. This branch extends Agent Zero with a P2P sidecar, enabling autonomous multi-agent collaboration, shared memory, distributed storage, and a real-time visual dashboard ("SwarmOS"). 🌟 Key Features 1. Decentralized Discovery (Hypermind) - Agents automatically discover each other via the Hyperswarm DHT. - Zero Configuration: No central server or signaling server required. - Self-Healing: Peers automatically re-connect if the network drops. 2. SwarmOS Dashboard A React-based "Mission Control" for your agent. - Live Topology: Visualize the swarm network graph in real-time. - Data Layer UI:Local Drive: Browse files stored in the agent's Hyperdrive.Cortex Memory: Watch the agent's "thoughts" stream live from Hypercore. - A2UI: Render custom JSON interfaces sent by other agents. 3. Distributed Data Layer - Shared Memory (Hypercore): An append-only log for agent thoughts and logs. - Distributed File System (Hyperdrive): P2P file storage for sharing artifacts (images, code). - Identity Persistence: Ed25519 key pairs managed via identity.json.

And thank you for being here. If you have a minute to spare, say Hi and feel free to introduce yourself. Maybe share a picture of what you've acomplished with A0?

I actually had to have Codex helped me a bit to customize agent zero, but I was able to get all of my custom agents out of Claude code, and I downloaded about 50 skills from another GitHub repo and change them basically to flat files and imported the mall as knowledge into agent 0 and so it looks like we have all kinds of different workers and all kinds of different skills that can do stuff for me. so far Agent Zero is kind of like the BMW of LLM workhorses.

Hello Agent Zero Community. This thread is for discussion on local models for Agent Zero. If you are interested and new to that topic, watch the brief beginner videos in preparation for the Local Models for Agent Zero classroom session: https://www.skool.com/agent-zero/classroom/c8000b5f After the live classroom session or if you caught the recording, we would love to hear more about what you are doing with local models. Are you running an enormously big model? Do you have separate local Chat and Utility models? What context sizes are you reaching? We want to hear it all.

This is what I run in Claude Code. Goal is to have A0 manage as the overall Orchestrator of Orchestrators, if you will, via Terminals or subagents? We discussed a bit in weekly meet. Maybe this helps someone. Just takes small amount of customization to fit your needs! https://github.com/bybren-llc/wtfb-safe-agentic-workflow What This Is A production-tested Claude Code harness for teams that want structured AI workflows. Built on SAFe methodology (Scaled Agile Framework), adapted for AI agent teams. Works for any team with repeatable processes: Software, Marketing, Research, Legal, Operations. Includes: - 17 Model-Invoked Skills - Domain expertise Claude loads automatically - 23 Slash Commands - Workflow automation for common tasks - 11 SAFe Agent Profiles - Specialized roles with clear boundaries - Three-Layer Architecture - Hooks → Commands → Skills