NewsWorld
PredictionsDigestsScorecardTimelinesArticles
NewsWorld
HomePredictionsDigestsScorecardTimelinesArticlesWorldTechnologyPoliticsBusiness
AI-powered predictive news aggregation© 2026 NewsWorld. All rights reserved.
Trending
StrikesIranMilitaryFebruarySignificantEvacuationTimelineStatesFacePotentiallyTargetsIsraelCrisisDigestTensionsEmbassyWesternIranianTuesdayEmergencyRegionalLaunchesSecurityConducts
StrikesIranMilitaryFebruarySignificantEvacuationTimelineStatesFacePotentiallyTargetsIsraelCrisisDigestTensionsEmbassyWesternIranianTuesdayEmergencyRegionalLaunchesSecurityConducts
All Articles
Show HN: OpenSwarm – Multi‑Agent Claude CLI Orchestrator for Linear/GitHub
Hacker News
Published about 3 hours ago

Show HN: OpenSwarm – Multi‑Agent Claude CLI Orchestrator for Linear/GitHub

Hacker News · Feb 26, 2026 · Collected from RSS

Summary

I built OpenSwarm because I wanted an autonomous “AI dev team” that can actually plug into my real workflow instead of running toy tasks. OpenSwarm orchestrates multiple Claude Code CLI instances as agents to work on real Linear issues. It: • pulls issues from Linear and runs a Worker/Reviewer/Test/Documenter pipeline • uses LanceDB + multilingual-e5 embeddings for long‑term memory and context reuse • builds a simple code knowledge graph for impact analysis • exposes everything through a Discord bot (status, dispatch, scheduling, logs) • can auto‑iterate on existing PRs and monitor long‑running jobs Right now it’s powering my own solo dev workflow (trading infra, LLM tools, other projects). It’s still early, so there are rough edges and a lot of TODOs around safety, scaling, and better task decomposition. I’d love feedback on: • what feels missing for this to be useful to other teams • failure modes you’d be worried about in autonomous code agents • ideas for better memory/knowledge graph use in real‑world repos Repo: https://github.com/Intrect-io/OpenSwarm Happy to answer questions and hear brutal feedback. Comments URL: https://news.ycombinator.com/item?id=47160980 Points: 8 # Comments: 0

Full Article

OpenSwarm Autonomous AI agent orchestrator powered by Claude Code CLI OpenSwarm orchestrates multiple Claude Code instances as autonomous agents. It picks up Linear issues, runs Worker/Reviewer pair pipelines to produce code changes, reports progress to Discord, and retains long-term memory via LanceDB vector embeddings. Architecture ┌──────────────────────────┐ │ Linear API │ │ (issues, state, memory) │ └─────────────┬────────────┘ │ ┌─────────────────────┼─────────────────────┐ │ │ │ v v v ┌──────────────────┐ ┌──────────────────┐ ┌──────────────────┐ │ AutonomousRunner │ │ DecisionEngine │ │ TaskScheduler │ │ (heartbeat loop) │─>│ (scope guard) │─>│ (queue + slots) │ └────────┬─────────┘ └──────────────────┘ └────────┬─────────┘ │ │ v v ┌──────────────────────────────────────────────────────────────┐ │ PairPipeline │ │ ┌────────┐ ┌──────────┐ ┌────────┐ ┌─────────────┐ │ │ │ Worker │──>│ Reviewer │──>│ Tester │──>│ Documenter │ │ │ │ (CLI) │<──│ (CLI) │ │ (CLI) │ │ (CLI) │ │ │ └────────┘ └──────────┘ └────────┘ └─────────────┘ │ │ ↕ StuckDetector │ └──────────────────────────────────────────────────────────────┘ │ │ │ v v v ┌──────────────┐ ┌──────────────────┐ ┌──────────────────┐ │ Discord Bot │ │ Memory (LanceDB │ │ Knowledge Graph │ │ (commands) │ │ + Xenova E5) │ │ (code analysis) │ └──────────────┘ └──────────────────┘ └──────────────────┘ Features Autonomous Pipeline - Cron-driven heartbeat fetches Linear issues, runs Worker/Reviewer pair loops, and updates issue state automatically Worker/Reviewer Pairs - Multi-iteration code generation with automated review, testing, and documentation stages Decision Engine - Scope validation, rate limiting, priority-based task selection, and workflow mapping Cognitive Memory - LanceDB vector store with Xenova/multilingual-e5-base embeddings for long-term recall across sessions Knowledge Graph - Static code analysis, dependency mapping, and impact analysis for smarter task execution Discord Control - Full command interface for monitoring, task dispatch, scheduling, and pair session management Dynamic Scheduling - Cron-based job scheduler with Discord management commands PR Auto-Improvement - Monitors open PRs and iteratively improves them via pair pipeline Long-Running Monitors - Track external processes (training jobs, batch tasks) and report completion Web Dashboard - Real-time status dashboard on port 3847 i18n - English and Korean locale support Prerequisites Node.js >= 22 Claude Code CLI installed and authenticated (claude -p) Discord Bot token with message content intent Linear API key and team ID GitHub CLI (gh) for CI monitoring (optional) Installation git clone https://github.com/unohee/OpenSwarm.git cd OpenSwarm npm install Configuration cp config.example.yaml config.yaml Create a .env file with required secrets: DISCORD_TOKEN=your-discord-bot-token DISCORD_CHANNEL_ID=your-channel-id LINEAR_API_KEY=your-linear-api-key LINEAR_TEAM_ID=your-linear-team-id config.yaml supports environment variable substitution (${VAR} or ${VAR:-default}) and is validated with Zod schemas. Key Configuration Sections Section Description discord Bot token, channel ID, webhook URL linear API key, team ID github Repos list for CI monitoring agents Agent definitions (name, projectPath, heartbeat interval) autonomous Schedule, pair mode, role models, decomposition settings prProcessor PR auto-improvement schedule and limits Agent Roles Each pipeline stage can be configured independently: autonomous: defaultRoles: worker: model: claude-haiku-4-5-20251001 escalateModel: claude-sonnet-4-20250514 escalateAfterIteration: 3 timeoutMs: 1800000 reviewer: model: claude-haiku-4-5-20251001 timeoutMs: 600000 tester: enabled: false documenter: enabled: false auditor: enabled: false Usage # Development npm run dev # Production npm run build npm start # Background nohup npm start > openswarm.log 2>&1 & # Docker docker compose up -d Project Structure src/ ├── index.ts # Entry point ├── core/ # Config, service lifecycle, types, event hub ├── agents/ # Worker, reviewer, tester, documenter, auditor │ ├── pairPipeline.ts # Worker → Reviewer → Tester → Documenter pipeline │ ├── agentBus.ts # Inter-agent message bus │ └── cliStreamParser.ts # Claude CLI output parser ├── orchestration/ # Decision engine, task parser, scheduler, workflow ├── automation/ # Autonomous runner, cron scheduler, PR processor │ ├── longRunningMonitor.ts# External process monitoring │ └── runnerState.ts # Persistent pipeline state ├── memory/ # LanceDB + Xenova embeddings cognitive memory ├── knowledge/ # Code knowledge graph (scanner, analyzer, graph) ├── discord/ # Bot core, command handlers, pair session UI ├── linear/ # Linear SDK wrapper, project updater ├── github/ # GitHub CLI wrapper for CI monitoring ├── support/ # Web dashboard, planner, rollback, git tools ├── locale/ # i18n (en/ko) with prompt templates └── __tests__/ # Vitest test suite Discord Commands Task Dispatch Command Description !dev <repo> "<task>" Run a dev task on a repository !dev list List known repositories !tasks List running tasks !cancel <taskId> Cancel a running task Agent Management Command Description !status Agent and system status !pause <session> Pause autonomous work !resume <session> Resume autonomous work !log <session> [lines] View recent output Linear Integration Command Description !issues List Linear issues !issue <id> View issue details !limits Agent daily execution limits Autonomous Execution Command Description !auto Execution status !auto start [cron] [--pair] Start autonomous mode !auto stop Stop autonomous mode !auto run Trigger immediate heartbeat !approve / !reject Approve or reject pending task Worker/Reviewer Pair Command Description !pair Pair session status !pair start [taskId] Start a pair session !pair run <taskId> [project] Direct pair run !pair stop [sessionId] Stop a pair session !pair history [n] View session history !pair stats View pair statistics Scheduling Command Description !schedule List all schedules !schedule run <name> Run a schedule immediately !schedule toggle <name> Enable/disable a schedule !schedule add <name> <path> <interval> "<prompt>" Add a schedule !schedule remove <name> Remove a schedule Other Command Description !ci GitHub CI failure status !codex Recent session records !memory search "<query>" Search cognitive memory !help Full command reference How It Works Issue Processing Flow Linear (Todo/In Progress) → Fetch assigned issues → DecisionEngine filters & prioritizes → Resolve project path via projectMapper → PairPipeline.run() → Worker generates code (Claude CLI) → Reviewer evaluates (APPROVE/REVISE/REJECT) → Loop up to N iterations → Optional: Tester → Documenter stages → Update Linear issue state (Done/Blocked) → Report to Discord → Save to cognitive memory Memory System Hybrid retrieval scoring: 0.55 * similarity + 0.20 * importance + 0.15 * recency + 0.10 * frequency Memory types: belief, strategy, user_model, system_pattern, constraint Background cognition: decay, consolidation, contradiction detection, and distillation (noise filtering). Tech Stack Category Technology Runtime Node.js 22+ (ESM) Language TypeScript (strict mode) Build tsc Agent Execution Claude Code CLI (claude -p) via child_process.spawn Task Management Linear SDK (@linear/sdk) Communication Discord.js 14 Vector DB LanceDB + Apache Arrow Embeddings Xenova/transformers (multilingual-e5-base, 768D) Scheduling Croner Config YAML + Zod validation Linting oxlint Testing Vitest State & Data Path Description ~/.openswarm/ State directory (memory, codex, metrics, workflows, etc.) ~/.claude/openswarm-*.json Pipeline history and task state config.yaml Main configuration dist/ Compiled output Docker docker compose up -d The Docker setup includes volume mounts for ~/.openswarm/ state persistence and .env for secrets. License MIT


Share this story

Read Original at Hacker News

Related Articles

Hacker Newsabout 4 hours ago
Jane Street Hit with Terra $40B Insider Trading Suit

Article URL: https://www.disruptionbanking.com/2026/02/24/jane-street-hit-with-terra-40b-insider-trading-suit/ Comments URL: https://news.ycombinator.com/item?id=47160613 Points: 10 # Comments: 0

Hacker Newsabout 4 hours ago
Show HN: ZSE – Open-source LLM inference engine with 3.9s cold starts

I've been building ZSE (Z Server Engine) for the past few weeks — an open-source LLM inference engine focused on two things nobody has fully solved together: memory efficiency and fast cold starts. The problem I was trying to solve: Running a 32B model normally requires ~64 GB VRAM. Most developers don't have that. And even when quantization helps with memory, cold starts with bitsandbytes NF4 take 2+ minutes on first load and 45–120 seconds on warm restarts — which kills serverless and autoscaling use cases. What ZSE does differently: Fits 32B in 19.3 GB VRAM (70% reduction vs FP16) — runs on a single A100-40GB Fits 7B in 5.2 GB VRAM (63% reduction) — runs on consumer GPUs Native .zse pre-quantized format with memory-mapped weights: 3.9s cold start for 7B, 21.4s for 32B — vs 45s and 120s with bitsandbytes, ~30s for vLLM All benchmarks verified on Modal A100-80GB (Feb 2026) It ships with: OpenAI-compatible API server (drop-in replacement) Interactive CLI (zse serve, zse chat, zse convert, zse hardware) Web dashboard with real-time GPU monitoring Continuous batching (3.45× throughput) GGUF support via llama.cpp CPU fallback — works without a GPU Rate limiting, audit logging, API key auth Install: ----- pip install zllm-zse zse serve Qwen/Qwen2.5-7B-Instruct For fast cold starts (one-time conversion): ----- zse convert Qwen/Qwen2.5-Coder-7B-Instruct -o qwen-7b.zse zse serve qwen-7b.zse # 3.9s every time The cold start improvement comes from the .zse format storing pre-quantized weights as memory-mapped safetensors — no quantization step at load time, no weight conversion, just mmap + GPU transfer. On NVMe SSDs this gets under 4 seconds for 7B. On spinning HDDs it'll be slower. All code is real — no mock implementations. Built at Zyora Labs. Apache 2.0. Happy to answer questions about the quantization approach, the .zse format design, or the memory efficiency techniques. Comments URL: https://news.ycombinator.com/item?id=47160526 Points: 18 # Comments: 1

Hacker Newsabout 5 hours ago
Tech Companies Shouldn't Be Bullied into Doing Surveillance

Article URL: https://www.eff.org/deeplinks/2026/02/tech-companies-shouldnt-be-bullied-doing-surveillance Comments URL: https://news.ycombinator.com/item?id=47160226 Points: 34 # Comments: 1

Hacker Newsabout 6 hours ago
Banned in California

Article URL: https://www.bannedincalifornia.org/ Comments URL: https://news.ycombinator.com/item?id=47159430 Points: 119 # Comments: 109

Hacker Newsabout 6 hours ago
Origin of the rule that swap size should be 2x of the physical memory

Article URL: https://retrocomputing.stackexchange.com/questions/32492/origin-of-the-rule-that-swap-size-should-be-2x-of-the-physical-memory Comments URL: https://news.ycombinator.com/item?id=47159364 Points: 8 # Comments: 0

Hacker Newsabout 7 hours ago
First Website

Article URL: https://info.cern.ch Comments URL: https://news.ycombinator.com/item?id=47159302 Points: 27 # Comments: 3