Announcing n00dles v0.1.0 — public beta

Today we're open-sourcing n00dles — the multi-agent orchestration layer we built internally, ran across two production deployments, and decided was good enough to stop keeping to ourselves. It's MIT licensed, it's on PyPI now, and pip install get-n00dles is the whole installation story.

What's actually in v0.1.0

We'd rather under-promise here than have you discover gaps the hard way, so here's exactly what's shipped in this release — sequential composition, end to end:

• The @agent decorator — your docstring becomes the system prompt, your type hints become the validated I/O contract.
• pipeline() and >> for chaining agents, plus run()/arun() to execute them.
• Provider support for every major LLM through litellm — Anthropic, OpenAI, Mistral, Gemini, Ollama, and more, switchable per agent with a string.
• Retry with exponential backoff and jitter, per-node timeouts, and fallback= agents — all configurable per agent or per pipeline.
• A SQLite state store, on by default, with checkpoint-after-every-node and resume-from-crash built in — no configuration required to get it.
• Pydantic v2 validation for structured agent outputs, with a clear AgentOutputError when a response doesn't fit.
• Structured trace events for every agent call, plus an optional OpenTelemetry exporter (pip install get-n00dles[otel]).

from n00dles import agent, pipeline, run

@agent(model="claude-sonnet-4-6")
def researcher(topic: str) -> str:
    """Research the topic. Return 3 key facts."""

@agent(model="claude-sonnet-4-6")
def writer(research: str) -> str:
    """Write a short article from the research."""

result = run(pipeline(researcher >> writer, retry=3), topic="multi-agent orchestration")

What's deliberately not in this release

v0.1.0 is sequential composition only — every pipeline is a straight line of >>. Fan-out and conditional routing, a circuit breaker, distributed state backends, and a deploy CLI are all real plans, not vague ones, but none of them are in your hands today. We'd rather ship a smaller surface that does exactly what it claims than a larger one with corners that don't quite work yet.

Why open source it now, not later

We could have kept building internally and waited for a more feature-complete release. We didn't, because the core problem n00dles solves — reliable, typed, checkpointed multi-agent execution without 4,000 lines of glue code — is already real and already useful at this scope. Waiting for fan-out and a CLI to exist before letting anyone else use the sequential core felt like optimizing for our roadmap instead of for the people who need this today.

Install it, read the five-minute quickstart, and tell us where it breaks — on GitHub or in the Discord. We're shipping this in the open from here on, changelog and all.