Tinytasktree – Behavior-tree-style task orchestration for LLM agents
Behavior-tree orchestration for agents when LangGraph and AutoGen already exist.
OxyJen is an open-source Java framework for orchestrating LLM workloads with graph-style execution, context-aware memory, and deterministic retry/fallback. It treats LLMs as native nodes (not helper utilities), allowing developers to build multi-step AI pipelines that integrate cleanly with existing Java code.
Graph-based LLM pipelines for Java, but LangChain4j already dominates and covers the same use cases more maturely.
Java/JVM backend engineers, enterprise AI pipeline builders, Java microservices teams
LangChain4j · Spring AI
OxyJen's approach is different. It's a graph-based orchestration framework(currently sequential) where LLMs are treated as native, reliable nodes in a pipeline, not as magical helper utilities. The core idea is to bring deterministic reliability to probabilistic AI calls. Everything is a node in a graph based system, LLMNode, LLMChain, LLM api is used to build a simple LLM node for the graph with retry/fallback, jitter/backoff, timeout enforcements(currently supports OpenAI).
PromptTemplate, Variable(required/optional) and PromptRegistry is used to build and store reusable prompts which saves you from re writing prompts.
JSONSchema and SchemaGenerator is used to build schema from POJOs/Records which will provide Json enforcements on outputs of these LLMs. SchemaNode<T> wraps SchemaEnforcer and validator to map LLM output directly to the classes. Enforcer also makes sure your output is correct and takes maximum retries.
Currently working on the Tool API to help users build their custom tools in Oxyjen. I'm a solo builder right now and the project is in its very early stage so I would really appreciate any feedback and contributions(even a small improvement in docs would be valuable).
Behavior-tree orchestration for agents when LangGraph and AutoGen already exist.
Quoracle forces you to stop trusting one model and instead runs every decision through an explicit consensus pipeline, with per-model conversation history persisted to Postgres and a LiveView dashboard for realtime inspection. Agents can spawn children recursively and communicate via messages, which makes it a neat sandbox for studying emergent behaviors or building robust multi-model workflows — heavy, opinionated, and clearly aimed at folks who want to experiment rather than ship a lightweight chatbot.
Claude agent orchestration for Laravel, but multi-agent automation exists in CrewAI, Autogen.
AgentForge packs provider adapters (Claude, GPT‑4, Gemini, Perplexity), token-aware rate limiting, retry/backoff, and a MockLLMClient for tests into a tiny dependency surface — the 15KB footprint and 2 dependencies is an attention-grabber. The 3‑tier Redis cache and benchmark claims (huge latency/memory wins vs LangChain, 88% cache hit) make it a tempting low-overhead alternative, though you should validate provider feature parity and benchmarks against your workload.
Backpressured pipeline with 60-80% dedup savings beats chatty multi-agent frameworks.
AgentForge compresses common production patterns—token-aware rate limiting (token-bucket), retry+exponential backoff, prompt templates and cost tracking—into a tiny async core and lets you flip providers with one parameter. The multi-agent mesh and ReAct loop bits are the most interesting engineering bets here, and the repo includes benchmarks and a Streamlit demo, but it lives in a crowded space next to LangChain and similar toolkits so real differentiation will come from adoption and edge-case robustness.