惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

人人都是产品经理
人人都是产品经理
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
月光博客
月光博客
雷峰网
雷峰网
Google DeepMind News
Google DeepMind News
Y
Y Combinator Blog
Microsoft Security Blog
Microsoft Security Blog
M
MIT News - Artificial intelligence
WordPress大学
WordPress大学
MongoDB | Blog
MongoDB | Blog
V
V2EX
博客园 - 【当耐特】
GbyAI
GbyAI
Stack Overflow Blog
Stack Overflow Blog
I
InfoQ
Martin Fowler
Martin Fowler
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
Hugging Face - Blog
Hugging Face - Blog
B
Blog
V
Visual Studio Blog
D
DataBreaches.Net
C
Check Point Blog
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
F
Fortinet All Blogs

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
I built a tiny AI company that runs on my laptop (multi-a...
EJ · 2026-04-28 · via DEV Community

EJ

Holons Demo

Lately I’ve been thinking about what “work” might look like in a world of AI agents.

I was talking with my wife about it — maybe in the future, instead of replacing people one by one, it becomes one person managing a small team of AI workers.

But tools like Claude Code or OpenClaw felt way too technical for her.

So I started wondering:

what if this actually felt like working with a team?

Not writing code.

Not wiring workflows.

But hiring, managing, and collaborating.

So I built Holons.


What it looks like

Holons is a desktop-first system (Tauri + Flask + React) where:

  • agents have roles and identities
  • a “lead” agent assigns tasks and builds workflows
  • multiple agents can collaborate in group chats
  • everything runs locally (or self-hosted)

You can say something like:

“Create a pitch for a B2B AI accountant”

And it will:

  • propose a workflow
  • assign tasks to different agents
  • estimate cost
  • and let you run the whole thing

What surprised me

The hardest part wasn’t the agents.

It was visibility.

Once you have multiple agents running, you need to understand:

  • what they’re doing
  • how much they cost
  • how they behave over time

So one design decision I made early:

Every LLM call writes to a unified ledger

Each call tracks:

  • model + provider
  • tokens (prompt / completion)
  • cost
  • latency
  • agent + user

That single table powers:

  • cost dashboards
  • usage quotas
  • reports
  • audit logs

This turned out to be way more important than I expected.


Some technical notes

  • Multi-provider support: Bedrock, OpenAI, Anthropic, Gemini, MiniMax
  • Per-agent model binding (different agents can use different models)
  • pgvector-based RAG + external knowledge integrations
  • MCP-style tool integration
  • IM channels (Telegram / Slack / LINE)

Still early

This is very much an experiment.

I’m not sure yet if this is the “right” abstraction for multi-agent systems,
but it already feels different from traditional workflows.

More like managing a team,

less like calling an API.


Links


Curious how others are thinking about multi-agent systems.

Are people actually using them in real workflows,
or are we still figuring out the right model?