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

推荐订阅源

U
Unit 42
Blog — PlanetScale
Blog — PlanetScale
H
Help Net Security
The GitHub Blog
The GitHub Blog
博客园 - Franky
酷 壳 – CoolShell
酷 壳 – CoolShell
Recent Announcements
Recent Announcements
量子位
aimingoo的专栏
aimingoo的专栏
大猫的无限游戏
大猫的无限游戏
博客园 - 叶小钗
Microsoft Azure Blog
Microsoft Azure Blog
Martin Fowler
Martin Fowler
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
A
About on SuperTechFans
T
Tailwind CSS Blog
V
V2EX
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
B
Blog
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
S
SegmentFault 最新的问题
G
Google Developers Blog
M
MIT News - Artificial intelligence

Hacker News - Newest: "AI"

AI can't read an investor deck AI as an attorney? Student uses ChatGPT, Gemini to sue UW over alleged racial discrimination Hacking MCP Servers in AI Systems – The Rug Pull: Tool Changes After Approval GitHub - MeepCastana/KubeezCut: Free Web based video editor Can AI judge journalism? A Thiel-backed startup says yes, even if it risks chilling whistleblowers Coming soon: 10 Things That Matter in AI Right Now DARPA built an AI to fact-check enemy weapons claims What explains heterogeneity in AI adoption? When AI Meets Muscle: Context-Aware Electrical Stimulation Promises a New Way to Guide Human Movements - Department of Computer Science AI Changed How We Build. It Did Not Change What Matters. Linux rules on using AI-generated code - Copilot is OK, but humans must take 'full responsibility for the… Meta spins up AI version of Mark Zuckerberg to engage with employees Code Mode: Let Your AI Write Programs, Not Just Call Tools | TanStack Blog GitHub - Delavalom/graft: Go framework for building AI agents. Type-safe tools, multi-provider (OpenAI, Anthropic, Gemini, Bedrock), zero vendor SDKs. India's TCS tops estimates, says new AI models did not dent services demand Gen Z's fading AI hype Strong feeling: we are in a folded AI reality GitHub - machinarii/total-recall-catalog: A reference catalog of latest knowledge retrieval, memory & RAG systems GitHub - mensfeld/code-on-incus: Give each AI agent its own isolated machine with root, Docker, and systemd. Active defense detects and stops threats automatically.. Quantization, LoRA, and the 8% Problem: Benchmarking Local LLMs for Production AI Iran war: We spoke to the man making Lego-style AI videos that experts say are powerful propaganda Powell, Bessent discussed Anthropic's Mythos AI cyber threat with major U.S. banks GitHub - immartian/bellamem: Persistent belief-graph memory for AI agents. Retrieves decisive context by importance — not recency, not RAG, not /compact. recursive-mode: The Repo-Native Operating System for AI Engineering After the attack on Sam Altman's home, will AI CEO's go on the offensive? The biggest advance in AI since the LLM Opus 4.6 vs GPT 5.4 One Prompt Unity World Generation Test “AI polls” are fake polls Client Challenge Can AI be a 'child of God'? Inside Anthropic's meeting with Christian leaders
GitHub - datallmhub/spring-agent-flow: Multi-agent orches...
asekka1 · 2026-05-01 · via Hacker News - Newest: "AI"

Stateful multi-agent orchestration for Spring AI.

Design and run long-lived agent workflows with state, retries, and graph execution, all in Java, without manual orchestration code.

build Java 17+ Spring AI License

Independent project — not affiliated with spring-ai-community/agent-client, which is Spring AI Community AgentClient abstraction over CLI agents (Claude Code, Codex, Gemini, etc.). This repository has a different scope: a graph-based runtime for stateful agent workflows on top of Spring AI.


image

What problem does this solve?

Real-world AI systems quickly move past a single ChatClient call:

  • multi-step pipelines (research → analyse → draft → review)
  • multiple agents coordinating on one task
  • transient errors, rate limits, partial failures
  • state that must survive a crash or wait on human input

You end up writing the orchestration, the retries, the resume logic. This project replaces that scaffolding with a structured runtime — an AgentGraph for explicit flow, RetryPolicy and CircuitBreakerPolicy for resilience, durable checkpoints for resume.

When should I use this?

Use it when at least one of these is true:

  • the agent needs more than one LLM call to finish the job
  • the workflow has branches, loops, or human-in-the-loop pauses
  • failure recovery (retry, breaker, resume after crash) is in scope
  • multiple tools or agents must coordinate around shared, typed state

Don't use it for a single LLM call with a stateless prompt — Spring AI's ChatClient already covers that cleanly.


60 seconds to multi-agent

// 1. Define specialized agents
ExecutorAgent researcher = ExecutorAgent.builder()
        .chatClient(chatClient)
        .systemPrompt("You are a research specialist. Find key facts.")
        .tools(searchTool, wikipediaTool)
        .build();

ExecutorAgent writer = ExecutorAgent.builder()
        .chatClient(chatClient)
        .systemPrompt("Write a clear report from the research findings.")
        .build();

// 2. Let a coordinator route dynamically
CoordinatorAgent coordinator = CoordinatorAgent.builder()
        .executors(Map.of("research", researcher, "writing", writer))
        .routingStrategy(RoutingStrategy.llmDriven(chatClient))
        .build();

// 3. Run
AgentResult result = coordinator.execute(
        AgentContext.of("Compare Claude 4 and GPT-5 for enterprise use"));

System.out.println(result.text());

No while loops. No manual routing. Just agents that collaborate.


Try it now — no LLM needed

Clone and run any of the 3 examples. They use simulated agents, no API key required.

git clone https://github.com/datallmhub/spring-agent-flow.git
cd spring-agent-flow
mvn install -DskipTests -q
mvn -pl spring-agent-flow-samples exec:java     # runs MultiAgentCoordination by default

Output:

=== Multi-Agent Coordination ===

Request: "Research the latest advances in quantum computing"
[router]   Routing to: research
[research] Searching for: quantum computing

Result: Found 3 papers on quantum error correction (2026).
        Key finding: logical qubit fidelity reached 99.8%.

---

Request: "Write a blog post about the findings"
[router]   Routing to: writing
[writing]  Generating content...

Result: # Quantum Computing in 2026
        Logical qubit fidelity has reached 99.8%, marking a milestone...

All 3 samples:

Example What it shows Run with
MultiAgentCoordination (default) Squad API + routing mvn -pl spring-agent-flow-samples exec:java
MinimalPipeline Two-step graph -Dexec.mainClass="...samples.MinimalPipeline"
AdvancedGraphDemo Conditional loops, state, listener -Dexec.mainClass="...samples.AdvancedGraphDemo"

Working with real LLMs (Safety & Constraints)

While this framework handles complex logic routing, executing graphs against live APIs (Mistral, OpenAI, Anthropic) requires managing their physical limitations. spring-agent-flow incorporates safety features to counteract these common pitfalls:

1. Strict Message Alternation (Safe Defaults) Some providers (like Mistral) will crash with HTTP 400 Bad Request if your prompt ends with an AssistantMessage or contains consecutive identical roles. During node chaining (A → B → C), ExecutorAgent uses built-in Safe Message Ordering to transparently interleave a padding UserMessage when required to prevent structure violations.

2. Rate Limiting & Transient Errors Agentic graphs generate requests instantly. A 3-step pipeline fires 3 requests in under 2 seconds. Free-tier architectures (typically 1 request/sec) will fail with 429 Too Many Requests or 503 Service Unavailable. Solution: Your components should rely on .errorPolicy(ErrorPolicy.RETRY_ONCE) mapped to Spring AI's automatic Retry mechanisms, or manually interleave non-blocking delays in intensive ReAct loops.

3. Non-deterministic Routing A conditional edge verifying result.text().contains("APPROVED") can break if the agent suddenly decides to output "Document is approved" instead of exact text. Always implement fuzzy matching or use LLM structured JSON output mappings for robust conditional routing rules.


Why not just use Spring AI?

Spring AI is perfect for single-step interactions.

As soon as your system requires:

  • multiple steps
  • retries and recovery
  • coordination between components

you start writing orchestration code. This project removes that layer.

Spring AI spring-agent-flow (built on top)
Low-level primitives (ChatClient, tools, advisors) Structured agent runtime (Agent, AgentGraph, Squad)
Code-driven orchestration (flexible, unstructured) Graph-based orchestration with explicit edges & cycles
No built-in durable state Typed shared state (StateKey<T>) + JDBC/Redis checkpoints
Error handling left to application code RetryPolicy (exp. backoff + jitter) and CircuitBreakerPolicy, per-node
No native interrupt/resume First-class interrupted(...) + graph.resume(runId, ...)
Observability via app-level integration Built-in Micrometer metrics through the starter

Installation

Requirements: Java 17+, Spring Boot 3.x, Spring AI 1.0+ (only when using ExecutorAgent or the starter).

Distributed via JitPack.

Maven

<repositories>
    <repository>
        <id>jitpack.io</id>
        <url>https://jitpack.io</url>
    </repository>
</repositories>

<dependency>
    <groupId>com.github.datallmhub.spring-agent-flow</groupId>
    <artifactId>spring-agent-flow-starter</artifactId>
    <version>v0.5.0</version>
</dependency>

Gradle

repositories {
    maven { url 'https://jitpack.io' }
}

dependencies {
    implementation 'com.github.datallmhub.spring-agent-flow:spring-agent-flow-starter:v0.5.0'
}

Modules

The starter pulls everything you typically need. Pick individual modules when you want a smaller footprint or run outside Spring Boot:

Module Use case
spring-agent-flow-starter Spring Boot auto-config, properties, Micrometer listener
spring-agent-flow-core Minimal API (Agent, AgentContext, StateKey, AgentResult)
spring-agent-flow-graph AgentGraph, RetryPolicy, CircuitBreakerPolicy SPI, checkpoint contract
spring-agent-flow-squad CoordinatorAgent, ExecutorAgent, ReActAgent, ParallelAgent, RoutingStrategy
spring-agent-flow-checkpoint JdbcCheckpointStore, RedisCheckpointStore, Jackson codec
spring-agent-flow-resilience4j CircuitBreakerPolicy adapter backed by Resilience4j
spring-agent-flow-cli-agents CliAgentNode — runs Claude Code / Codex / Gemini CLI agents as graph nodes
spring-agent-flow-test MockAgent, TestGraph for unit-testing graphs

The starter auto-configures everything. Minimal application.yml:

spring:
  ai:
    agents:
      enabled: true
      default-error-policy: RETRY_ONCE
      observability:
        metrics: true

Two levels of control

Level 1 — Squad API (recommended)

The default. A CoordinatorAgent routes to ExecutorAgents. You focus on the agents, not the plumbing.

CoordinatorAgent coordinator = CoordinatorAgent.builder()
        .executors(Map.of(
            "research", researchExecutor,
            "analysis", analysisExecutor,
            "writing",  writingExecutor
        ))
        .routingStrategy(RoutingStrategy.llmDriven(chatClient))
        .build();

AgentResult result = coordinator.execute(AgentContext.of("..."));

Level 2 — Graph API (when you need fine control)

For explicit sequencing, conditional branching, or cycles (ReAct loops):

AgentGraph graph = AgentGraph.builder()
        .addNode("research", researcher)
        .addNode("analyze",  analyzer)
        .addNode("write",    writer)
        .addEdge("research", "analyze")
        .addEdge(Edge.conditional("analyze",
                ctx -> ctx.get(CONFIDENCE).doubleValue() < 0.7,
                "research"))                               // loop back
        .addEdge("analyze", "write")                       // fallback: forward
        .errorPolicy(ErrorPolicy.RETRY_ONCE)
        .build();

AgentResult result = graph.invoke(AgentContext.of("..."));

Streaming

Every agent supports Flux<AgentEvent> out of the box:

graph.invokeStream(AgentContext.of("hello"))
    .subscribe(event -> {
        switch (event) {
            case AgentEvent.Token t         -> System.out.print(t.chunk());
            case AgentEvent.NodeTransition x -> System.out.println("\n--> " + x.to());
            case AgentEvent.Completed c     -> System.out.println("\n[done]");
            default -> {}
        }
    });

Typed state — no Map<String, Object>

// Declare keys with types — compile-time safety
StateKey<Double> CONFIDENCE = StateKey.of("confidence", Double.class);
StateKey<String> SUMMARY    = StateKey.of("summary",    String.class);

// Use them anywhere
AgentContext ctx = context.with(CONFIDENCE, 0.85);
double score = ctx.get(CONFIDENCE);  // no cast needed

Architecture

┌─────────────────────────────────────────────────┐
│                 Your Application                │
├─────────────────────────────────────────────────┤
│ spring-agent-flow-starter (auto-config, metrics) │
├──────────────┬──────────────────┬───────────────┤
│ checkpoint   │ resilience4j     │               │
│ JDBC, Redis  │ CircuitBreaker   │               │
├──────────────┴──────────────────┴───────────────┤
│   squad              │   graph                  │
│   CoordinatorAgent   │   AgentGraph (runtime)   │
│   ExecutorAgent      │   Node, Edge             │
│   RoutingStrategy    │   RetryPolicy, CB SPI    │
│   ReActAgent         │   CheckpointStore        │
│   ParallelAgent      │   ErrorPolicy            │
├──────────────────────┴──────────────────────────┤
│ spring-agent-flow-core                           │
│ Agent, AgentContext, AgentResult, AgentEvent     │
│ StateKey, StateBag                              │
├─────────────────────────────────────────────────┤
│                   Spring AI                     │
│           ChatClient, ToolCallbacks             │
└─────────────────────────────────────────────────┘

Resilience

Three layers compose: error policy (what to do on failure), retry (how to recover from transient failure), circuit breaker (when to stop trying).

AgentGraph.builder()
    .errorPolicy(ErrorPolicy.FAIL_FAST)          // or RETRY_ONCE / SKIP_NODE
    .retryPolicy(RetryPolicy.exponential(3, Duration.ofMillis(200)))
    .addNode("llm", flakyAgent,
             RetryPolicy.exponential(5, Duration.ofMillis(500)),   // per-node override
             new Resilience4jCircuitBreakerPolicy(registry))        // per-node breaker
    .build();
  • RetryPolicy — bounded jitter [cap*(1-f), cap] so retries never exceed maxDelay; per-node override wins over the graph default.
  • CircuitBreakerPolicy — SPI lives in the graph module (R4j-free). spring-agent-flow-resilience4j ships an adapter backed by Resilience4j's CircuitBreakerRegistry (per-node breakers) or a shared breaker for aggregate counting.
  • ErrorPolicy.SKIP_NODE — propagate past a blown breaker when the rest of the graph can still make useful progress.

See resilient-typed-executor.md and circuit-breaker.md.


Observability (Micrometer)

When a MeterRegistry is available, the starter registers metrics automatically:

Metric Tags Description
agents.execution.count agent, graph, status Per-node execution count
agents.execution.duration agent, graph Per-node execution time
agents.graph.transitions graph, from, to Node-to-node transitions
agents.execution.errors agent, graph, cause Error count by type

Custom instrumentation via AgentListener:

AgentGraph.builder()
    .listener(new AgentListener() {
        @Override
        public void onNodeExit(String g, String node, AgentResult r, long ns) {
            log.info("{} completed in {}ms", node, ns / 1_000_000);
        }
    })

Recipes


Testing without an LLM

MockAgent mock = MockAgent.builder()
        .thenReturn("First response")
        .thenReturn("Second response")
        .build();

TestGraph.Trace trace = TestGraph.trace(
        AgentGraph.builder()
            .addNode("a", mock)
            .addNode("b", MockAgent.returning("done"))
            .addEdge("a", "b"));

AgentResult result = trace.invoke(AgentContext.of("test"));

assertThat(trace.visitedInOrder("a", "b")).isTrue();
assertThat(result.text()).isEqualTo("done");

Requirements

  • Java 17+
  • Spring Boot 3.x
  • Spring AI 1.0+

Roadmap

Version Focus
0.4 (current) Subgraphs, parallel fan-out, cancellation, typed output, RetryPolicy, CircuitBreakerPolicy, JDBC/Redis checkpoint store
1.0 API stabilization, documentation, community feedback
1.1 Crew roles (CrewAI-inspired), auto-config for checkpoint backends
2.0 OpenTelemetry tracing, MCP integration, Agent-as-Tool

Contributing

Contributions welcome! Please see CONTRIBUTING.md for guidelines.

This project follows the Apache 2.0 License.


Inspiration