Open Source Radar — August 22: swarms, workspaces & observability
Today's board is the agent operating layer: a meta-harness for orchestrating teams of agents, Apache's new local-first agent workspace, and an analytics platform that wants to be every AI team's eyes on what agents are doing. Three projects, all fresh on daily trending, none of them repeats.
ruflo (TypeScript, ~68k stars) — An agent meta-harness from the developer behind claude-flow, built to deploy intelligent multi-agent swarms and coordinate autonomous workflows from one place. It pairs adaptive memory with RAG integration so a team of agents shares context instead of each starting from a blank slate, and it plugs natively into Claude Code, Codex, and Hermes rather than squaring you into a new harness. It's the biggest star mover on today's board because teams keep hitting the ceiling of single-agent setups — running one agent is manageable, but running several that swap state cleanly between a "hive mind" is the harder problem it actually targets. If you're building agent teams and tired of stitching them together by hand, this is the most finished meta-orchestrator on the daily list.
Maka (TypeScript, ~2k stars) — Apache Maka, an incubating project under the Apache umbrella, is a local-first agent workspace that records every model message, tool call, tool result, and permission decision as an append-only log — the log is the runtime, and your sessions and recovery are just projections over it. It ships as a desktop app (currently an early build for macOS Apple Silicon), plus a terminal TUI and a non-interactive CLI, all behind controlled permissions so the agent can inspect projects, run tools, and produce artifacts without free rein. Local-first by default and Foundation-backed, it's early but credible for anyone who wants agent work that is recorded, recoverable, and reviewable rather than a chat transcript you hope you can rewind.
PostHog (~38k stars) — The open-source product analytics suite has sharpened its pitch to building "self-driving products": it layers AI observability — tracing your LLM app's generations, latency, and cost — on top of the usual session replay, feature flags, experiments, and error tracking, and you can steer it from your editor via MCP or from Slack. Its self-driving mode reads the signals in your product data (errors, rage clicks, failed queries) and turns them into researched reports and pull requests for a human to review and merge. It lands on daily trending because teams building AI features now need eyes on their agents the way they once needed analytics on their web users — and PostHog is betting that observability becomes the control layer for that, with a generous free tier.
Worth watching this week: the agent stack keeps getting thicker — orchestration frameworks, record-everything workspaces, and observability platforms are converging on the same idea, that agents need infrastructure, not just a stronger model.
Would you let a "self-driving" analytics tool file pull requests on production code, or keep a human in every loop? Tell us in the comments.
Sources: ruflo (GitHub) · Maka (GitHub) · PostHog (GitHub) · PostHog self-driving docs
