What is this?
This is the ReAct loop coordinator for Astrid OS, part of the Unicity AOS project - a stateless state machine that drives the fetch-context, think, act, observe, repeat cycle that makes an agent behave like an agent.
This is the ReAct loop coordinator for Astrid OS, part of the Unicity AOS project - a stateless state machine that drives the fetch-context, think, act, observe, repeat cycle that makes an agent behave like an agent.Is this a standalone agent or a piece of a larger system?It is one 'capsule' (modular component) in Astrid OS's architecture, described as the 'shell' that coordinates five other capsules rather than doing any work itself.
It is one 'capsule' (modular component) in Astrid OS's architecture, described as the 'shell' that coordinates five other capsules rather than doing any work itself.How do I wire this into a project?There is no standalone install step - it is used internally as one capsule in the Astrid OS system and talks to the other capsules strictly over an IPC event bus.
There is no standalone install step - it is used internally as one capsule in the Astrid OS system and talks to the other capsules strictly over an IPC event bus.What other capsules does it depend on?It coordinates five companion capsules: Session (history), Identity (system prompt), Prompt Builder (merges plugin contributions), Provider e.g. Anthropic (streams LLM responses), and Tool Router (dispatches tool calls).
It coordinates five companion capsules: Session (history), Identity (system prompt), Prompt Builder (merges plugin contributions), Provider e.g. Anthropic (streams LLM responses), and Tool Router (dispatches tool calls).What does this capsule deliberately not do?It never calls LLMs, executes tools, builds prompts, or stores conversation history itself - those jobs belong to the other capsules it orchestrates.
It never calls LLMs, executes tools, builds prompts, or stores conversation history itself - those jobs belong to the other capsules it orchestrates.What exactly is a 'capsule' in this OS model?A capsule is a self-contained module that only talks to other capsules over an IPC event bus, so any single piece - orchestration, prompting, tool routing - can be swapped out independently.
A capsule is a self-contained module that only talks to other capsules over an IPC event bus, so any single piece - orchestration, prompting, tool routing - can be swapped out independently.Where does turn state get stored?Ephemeral per-turn control-flow state (not chat history) lives in the capsule's own KV store under keys like react.turn.{sessionid}, while actual conversation history stays in the Session capsule.
Ephemeral per-turn control-flow state (not chat history) lives in the capsule's own KV store under keys like react.turn.{sessionid}, while actual conversation history stays in the Session capsule.Can I swap the ReAct strategy for something else?Yes - because this capsule is pure orchestration logic, it can be replaced with a different strategy like debate, MCTS, or chain-of-verification without changing any of the other capsules.
Yes - because this capsule is pure orchestration logic, it can be replaced with a different strategy like debate, MCTS, or chain-of-verification without changing any of the other capsules.What are similar projects?PocketFlow, harness-sdk, autogen, capsule-identity, AntOmniEvo, spring-ai-alibaba, imp, codify
PocketFlow, harness-sdk, autogen, capsule-identity, AntOmniEvo, spring-ai-alibaba, imp, codifyWhich topics is it in?llm-agent, key-value, event-driven, agentic, agent-framework, autonomous-agents, orchestration, agent-orchestration, distributed-systems, multi-agent, agents, ai-agent
llm-agent, key-value, event-driven, agentic, agent-framework, autonomous-agents, orchestration, agent-orchestration, distributed-systems, multi-agent, agents, ai-agent