Activity, over time
Daily GitHub activity and social mentions.
Mentions
Daily posts linking to this repository
Attention
Daily stars & forks
Star accumulation
Cumulative stars
Pull requests
Daily opens & merges
Conversations
Daily issues & comments
Community
Daily accounts & reviews
Trending history
Daily top 10 · last 90 days · UTC
Mentions
Stars
Forks
Contributors
Latest stargazers
The last 10 distinct accounts we observed this year.
Most active participants
PR, issue, comment & review events in the past year.
Packages
| Package | Version | Downloads · 30d | Trend · 30d |
|---|---|---|---|
| — | — | — |
Live mentions badge
Show how many posts mention your project in the last 30 days.
Live mentions · last 30 days
Mentions
What agent loop are you using for Jev-style decision models + an LLM? ReAct is a common agent loop. What's the standard for System One decision models (Jev or a local alternative) + an LLM + tool calling? The examples I've been reading seem to split in two directions: confidence cascades in REFLEX and JevAgentHarness, and planner + chooser in the Hermes/Astra + Jev Minecraft agents. Is there an accepted pattern yet, or are these still separate approaches? I'm interested in the control loop: who creates the candidate actions, when the LLM replans, and when a low-confidence decision falls back to it. For anyone using local decision models alongside a larger LLM, what architecture has actually been useful? Papers or public implementations would help. References: REFLEX: arxiv.org JevAgentHarness: arxiv.org Hermes + Jev: teknium1/hermes-and-jev-play-minecraft Astra + Jev: rmalde/minecraft-agent English wording refined with AI.
Is there a standard architecture for decision models (Jev) + LLM + tool calling? ReAct is a common baseline for an LLM agent loop. What's the equivalent when you combine a fast decision model such as Jev, an LLM, and tool calling? I'm looking at this for game-agent experiments, where the world keeps running while the agent thinks. I'm trying to understand which parts of the loop should belong to each model. The examples I've been reading seem to follow two patterns: - Confidence cascades: a decision model handles bounded choices, with an LLM fallback when confidence is low (REFLEX and JevAgentHarness). - Planner + chooser: an LLM plans or proposes actions, and Jev picks bounded actions (Hermes/Astra + Jev in Minecraft). Is there an accepted architecture or name for this combination yet? In particular, how do you decide when to replan, who generates the candidate actions, and when a tool decision should fall back to the LLM? Public implementations or papers would help. This is a technical reference request for my own experiments; I'm not collecting personal data or monetizing responses. References: REFLEX: arxiv.org JevAgentHarness: arxiv.org Hermes + Jev: teknium1/hermes-and-jev-play-minecraft Astra + Jev: rmalde/minecraft-agent English wording refined with AI.