<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>Open Multi-Agent — Blog</title><description>Writing on TypeScript multi-agent orchestration: goal-driven task DAGs, mixed-model teams, durable shared state, and lessons from the agent-framework ecosystem.</description><link>https://open-multi-agent.com/</link><item><title>Multi-Agent AI in a TypeScript Service, Without the Python Sidecar</title><link>https://open-multi-agent.com/blog/typescript-agents-without-python-sidecar/</link><guid isPermaLink="true">https://open-multi-agent.com/blog/typescript-agents-without-python-sidecar/</guid><description>Three agents behind one Express route, in the Node process you already deploy: per-agent model tiers, validated JSON handoffs, a run-level token ceiling, and cancellation that actually cancels.</description><pubDate>Sun, 02 Aug 2026 00:00:00 GMT</pubDate><category>typescript</category><category>nodejs</category><category>multi-agent</category><category>express</category></item><item><title>Open Multi-Agent v1.14: Repair the Plan, Keep the Record</title><link>https://open-multi-agent.com/blog/v1-14-adaptive-recovery-hybrid-routing/</link><guid isPermaLink="true">https://open-multi-agent.com/blog/v1-14-adaptive-recovery-hybrid-routing/</guid><description>v1.14 adds adaptive plan recovery, opt-in hybrid semantic execution routing, DeepSeek V4 Flash reasoning controls, and fail-closed validation for task graphs, coordinator plans, and task requirements.</description><pubDate>Sun, 02 Aug 2026 00:00:00 GMT</pubDate><category>release</category><category>orchestration</category><category>recovery</category><category>typescript</category></item><item><title>Best TypeScript Multi-Agent Frameworks in 2026: Choose by Workflow</title><link>https://open-multi-agent.com/blog/best-typescript-multi-agent-frameworks-2026/</link><guid isPermaLink="true">https://open-multi-agent.com/blog/best-typescript-multi-agent-frameworks-2026/</guid><description>A source-backed guide to six TypeScript options for multi-agent systems, matched to explicit graphs, agent UIs, handoffs, routed networks, all-in-one apps, and goal-driven task DAGs.</description><pubDate>Fri, 31 Jul 2026 00:00:00 GMT</pubDate><category>typescript</category><category>multi-agent-frameworks</category><category>framework-selection</category></item><item><title>Competitive Monitoring: Isolate Each Source Before Comparing Them</title><link>https://open-multi-agent.com/blog/competitive-monitoring-contradiction-detection/</link><guid isPermaLink="true">https://open-multi-agent.com/blog/competitive-monitoring-contradiction-detection/</guid><description>One agent per source, structured claims out of each, and an aggregator that reads validated records instead of prose — so contradictions between a vendor post, a community thread, and a news article survive to the report.</description><pubDate>Fri, 31 Jul 2026 00:00:00 GMT</pubDate><category>competitive-intelligence</category><category>research</category><category>typescript</category></item><item><title>Support Tickets: A Fixed Pipeline and a Routed Agent Team</title><link>https://open-multi-agent.com/blog/customer-support-routing-playbook/</link><guid isPermaLink="true">https://open-multi-agent.com/blog/customer-support-routing-playbook/</guid><description>Keep the high-volume path on a typed classify → draft → QA graph, let escalations get a coordinator-built team, and put the refund behind a confirmation gate the runtime enforces per call.</description><pubDate>Fri, 31 Jul 2026 00:00:00 GMT</pubDate><category>customer-support</category><category>typescript</category><category>agents</category></item><item><title>Incident Postmortems: Parallel Investigation, Serial Judgment</title><link>https://open-multi-agent.com/blog/incident-postmortem-parallel-investigation/</link><guid isPermaLink="true">https://open-multi-agent.com/blog/incident-postmortem-parallel-investigation/</guid><description>Logs, deployments, and blast radius are independent evidence streams. A runTasks() DAG starts them together, keeps each result unmerged in taskResults, and hands the analyst validated structured payloads instead of prose.</description><pubDate>Fri, 31 Jul 2026 00:00:00 GMT</pubDate><category>sre</category><category>incident-response</category><category>typescript</category></item><item><title>Five Seams That Decide Whether a Workflow Needs a Team</title><link>https://open-multi-agent.com/blog/multi-agent-application-patterns-field-note/</link><guid isPermaLink="true">https://open-multi-agent.com/blog/multi-agent-application-patterns-field-note/</guid><description>Across OMA&apos;s runnable recipes the same five boundaries keep reappearing — and each one turns out to have a specific runtime mechanism behind it, from structured dependency payloads to an execution routing decision you can read back.</description><pubDate>Fri, 31 Jul 2026 00:00:00 GMT</pubDate><category>field-notes</category><category>workflow-design</category><category>agents</category></item><item><title>Translation Drift: Route the Back-Translation to Another Model</title><link>https://open-multi-agent.com/blog/translation-quality-cross-model-review/</link><guid isPermaLink="true">https://open-multi-agent.com/blog/translation-quality-cross-model-review/</guid><description>Translate with one provider, back-translate with another through a model-routing rule, and let a reviewer return structured drift findings — then measure the reviewer itself with a versioned EvalSet.</description><pubDate>Fri, 31 Jul 2026 00:00:00 GMT</pubDate><category>localization</category><category>translation</category><category>typescript</category></item><item><title>Open Multi-Agent v1.13: Route, Govern, Schedule, and Prove the Run</title><link>https://open-multi-agent.com/blog/v1-13-execution-routing-governance-scheduling/</link><guid isPermaLink="true">https://open-multi-agent.com/blog/v1-13-execution-routing-governance-scheduling/</guid><description>v1.13 adds execution routing, declared governance, consequential-tool confirmation, event-driven task scheduling, task-scoped results, structured handoffs, and retryable model fallbacks.</description><pubDate>Fri, 24 Jul 2026 00:00:00 GMT</pubDate><category>release</category><category>orchestration</category><category>governance</category><category>typescript</category></item><item><title>Open Multi-Agent v1.12.1: Evaluation, Offline Inspection, and a No-Key First Run</title><link>https://open-multi-agent.com/blog/v1-12-1-evaluation-zero-key/</link><guid isPermaLink="true">https://open-multi-agent.com/blog/v1-12-1-evaluation-zero-key/</guid><description>v1.12.1 adds versioned EvalSets, scorers, CI gates, online sampling, richer offline run inspection, per-run metadata, and a deterministic create-oma-app demo that needs no API key.</description><pubDate>Mon, 20 Jul 2026 00:00:00 GMT</pubDate><category>release</category><category>evaluation</category><category>typescript</category></item><item><title>A 100% Local Multi-Agent Team in TypeScript (Ollama + Gemma, $0 API Cost)</title><link>https://open-multi-agent.com/blog/local-multi-agent-team-ollama-gemma/</link><guid isPermaLink="true">https://open-multi-agent.com/blog/local-multi-agent-team-ollama-gemma/</guid><description>Run a multi-agent team fully on your laptop in TypeScript — even the coordinator is a 5B Gemma over Ollama, at $0 API cost. With a real per-agent ledger, honest friction, and a hybrid cloud+local variant.</description><pubDate>Thu, 02 Jul 2026 00:00:00 GMT</pubDate><category>typescript</category><category>ai</category><category>agents</category><category>ollama</category></item><item><title>From Transcript to Typed Action Items: Three Parallel Agents in TypeScript</title><link>https://open-multi-agent.com/blog/meeting-summarizer-parallel-agents/</link><guid isPermaLink="true">https://open-multi-agent.com/blog/meeting-summarizer-parallel-agents/</guid><description>Most meeting summarizers cram summary, action items, and sentiment into one LLM prompt. Here&apos;s a cleaner TypeScript shape: three specialist agents run in parallel, two return typed Zod output, and an aggregator merges them into one report.</description><pubDate>Wed, 24 Jun 2026 00:00:00 GMT</pubDate><category>typescript</category><category>ai</category><category>agents</category><category>opensource</category></item><item><title>Goal In, DAG Out: How Open-Multi-Agent Turns a Goal into a Task DAG</title><link>https://open-multi-agent.com/blog/goal-to-task-dag-coordinator/</link><guid isPermaLink="true">https://open-multi-agent.com/blog/goal-to-task-dag-coordinator/</guid><description>In most TypeScript agent frameworks you wire the task graph by hand. open-multi-agent&apos;s runTeam() hands a goal to a coordinator that builds the DAG for you — here&apos;s the mechanism, step by step.</description><pubDate>Sun, 21 Jun 2026 00:00:00 GMT</pubDate><category>typescript</category><category>ai</category><category>agents</category><category>opensource</category></item><item><title>Give Your TypeScript AI Agents Long-Term Memory with TencentDB-Agent-Memory</title><link>https://open-multi-agent.com/blog/agent-long-term-memory-tencentdb/</link><guid isPermaLink="true">https://open-multi-agent.com/blog/agent-long-term-memory-tencentdb/</guid><description>Wiring open-multi-agent&apos;s MemoryStore to TencentDB-Agent-Memory through its Hermes Gateway: a measured cross-run memory loop, and two upstream gotchas that decide whether anything gets stored.</description><pubDate>Mon, 15 Jun 2026 00:00:00 GMT</pubDate><category>typescript</category><category>ai</category><category>llm</category><category>tutorial</category></item><item><title>Goal-Driven Agent Orchestration vs Explicit Graphs: A TypeScript Framework Taxonomy</title><link>https://open-multi-agent.com/blog/goal-driven-vs-explicit-graphs/</link><guid isPermaLink="true">https://open-multi-agent.com/blog/goal-driven-vs-explicit-graphs/</guid><description>Most multi-agent framework reviews compare features. This post compares a different axis: where the framework places the decomposition cost. Goal-first frameworks pay it at runtime in tokens; graph-first frameworks pay it at design time in code.</description><pubDate>Wed, 03 Jun 2026 00:00:00 GMT</pubDate><category>typescript</category><category>ai</category></item><item><title>5 walls multi-agent frameworks hit: receipts from Mastra&apos;s year of .network() to Supervisor migration</title><link>https://open-multi-agent.com/blog/multi-agent-framework-walls/</link><guid isPermaLink="true">https://open-multi-agent.com/blog/multi-agent-framework-walls/</guid><description>Mastra spent a year migrating .network() to the Supervisor pattern. 5 engineering walls hit (context, routing, observability, nesting, performance), 18 GitHub issues as receipts. What it means for TypeScript multi-agent framework development.</description><pubDate>Thu, 21 May 2026 00:00:00 GMT</pubDate><category>mastra</category><category>typescript</category><category>agents</category><category>opensource</category></item><item><title>How to Run a Mixed-Model AI Agent Team in TypeScript?</title><link>https://open-multi-agent.com/blog/mixed-model-agent-team/</link><guid isPermaLink="true">https://open-multi-agent.com/blog/mixed-model-agent-team/</guid><description>A practical walkthrough from a single-model team baseline to a mixed-provider production setup with live cost and latency monitoring, using open-multi-agent, the TypeScript-ecosystem answer to CrewAI.</description><pubDate>Sat, 16 May 2026 00:00:00 GMT</pubDate><category>typescript</category><category>agents</category><category>ai</category><category>opensource</category></item><item><title>Adding Multi-Agent Orchestration to a Vercel AI SDK App</title><link>https://open-multi-agent.com/blog/multi-agent-vercel-ai-sdk/</link><guid isPermaLink="true">https://open-multi-agent.com/blog/multi-agent-vercel-ai-sdk/</guid><description>Add multi-agent orchestration to an existing Vercel AI SDK app: the AI SDK streams tokens and talks to models while open-multi-agent&apos;s runTeam() decomposes the goal and coordinates the agents — sharing a single Next.js API route.</description><pubDate>Wed, 15 Apr 2026 00:00:00 GMT</pubDate><category>ai</category><category>nextjs</category><category>webdev</category><category>typescript</category></item></channel></rss>