unicity-aos/capsule-react

ReAct loop coordinator. Stateless state machine for reasoning-and-action cycle. Part of Unicity AOS.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 32 minutes ago
Type:Library / SDKCategory(s):Agent Frameworks & SDKsAI Agents & LLM Apps
Added to GitGenius on September 13th, 2026
Created on March 16th, 2026
Open Issues & Pull Requests: 1 (+0)
GitHub issues: Enabled
Number of forks: 13
Total Stargazers: 5,044 (+0)
Total Subscribers: 2 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 7.5 hours
Mean response time: 28.5 hours
90th percentile: 2.1 days
Tracked items: 2

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 0
Closed in 7 days: 0
Avg open age: N/A days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Capsule React is a ReAct loop coordinator that orchestrates the reasoning-and-action cycle for an AI agent through a stateless state machine.

The tool solves the problem of coordinating multiple specialized components in an agentic system. Rather than embedding orchestration logic within a single monolithic service, Capsule React acts as a pure control flow engine that drives the cycle of fetching context, reasoning, acting, and observing. It coordinates five separate capsules over an IPC event bus: Session for conversation history, Identity for system prompt construction, Prompt Builder for merging plugin contributions, a Provider for LLM streaming, and Tool Router for dispatching and collecting tool results. The tool itself contains no inference logic, prompt building, tool execution, or message storage—it only manages the flow between these specialized components.

Adoption makes sense for teams building agentic systems within the Astrid OS framework who want to experiment with different orchestration strategies without rewriting supporting infrastructure. Because the tool is purely a control flow coordinator, swapping it out for alternative approaches like debate loops, Monte Carlo tree search, or chain-of-verification strategies changes agent behavior without touching any other component. This modularity is valuable for research and iterative development of reasoning patterns. The tool maintains ephemeral per-turn state in a capsule KV store for correlation and turn tracking, while delegating conversation history persistence to the Session capsule.

The project maintains a minimal, focused codebase that reflects its narrow responsibility. Development activity shows steady attention to the core orchestration logic without scope creep into adjacent concerns like LLM integration or tool execution.