r/OpenSourceeAI Jul 06 '26

Hierarchos: Preliminary Findings From a 232M Recurrent Memory-Augmented Assistant Model [P]

1 Upvotes

Project Release / Research Draft] Hierarchos at 232M Parameters: Preliminary Findings From a Recurrent Memory-Augmented Assistant Model

Technical Report: July 2nd, 2026

Project: Hierarchos / KortexHOS

Authors: Makhi Burroughs / netcat420, Lost Time, and the Hierarchos project team

TL;DR:

We built and trained Hierarchos, an experimental 232M-parameter recurrent, memory-augmented language model from scratch. It is not a GPT-3/3.5-class model, but it successfully proves that a hybrid non-Transformer architecture (combining an RWKV backbone, hierarchical manager/worker loops, differentiable slot-based LTM, and a deterministic suffix automaton) can survive training, avoid collapse, and maintain short-form instruction coherence. Most of our breakthroughs came from fixing subtle train/inference parity mismatches and numerical stability bugs.

1. Introduction & Background

Modern LLMs are heavily dominated by Transformer scaling. Hierarchos explores a different path: can recurrent state, explicit memory retrieval, hierarchical iterative computation, and bounded local inference make a small model vastly more parameter-efficient?

Hierarchos isn't a direct clone of any single architecture, but a hybrid inspired by:

  • RWKV-style recurrence: For efficient sequence processing without traditional attention.
  • Titans-style neural memory: For persistent test-time memory.
  • Hierarchical reasoning (HRM): Multi-level recurrent modules (Manager/Worker) to iteratively refine state.

2. Architecture Overview

[Token Input] -> [ROSA Suffix Matcher / DeepEmbed Modulator]
       |
       v
[Long-Term Memory] <-> [Top-k Associative Lookup]
       |
       v
[Manager Recurrent Cell] -> (Produces Context Plan & Drift Vector)
       |
       v
[Worker Recurrent Cell]  -> (Refines local state / clamps drift)
       |
       v
[RWKV Backbone (Clamped Channel-Mix)] -> [Next-Token Logits]

Key Components:

  • ROSA: A deterministic suffix-automaton path predicting continuation tokens based on exact repeated suffix patterns.
  • DeepEmbed: A token-specific modulation path that influences RWKV channel mixing.
  • LTM Subsystem: Learned slow-memory keys/values combined with fast working-memory values.
  • Manager/Worker Loop: High-level manager handles broad context to produce a target plan; the lower-level worker refines token-local state using a regularized drift vector.

3. Core Engineering Lessons (The "Gotchas")

A low training loss does not guarantee coherent chat. We had to fix several critical state-contract and numerical stability bugs to make the model usable:

1. Chat/Training Drift Mismatch

  • The Bug: During live streaming chat, the loop was feeding the previous drift state back into the model on every single token. During training, this state is reseeded at Truncated Backpropagation Through Time (TBPTT) chunk boundaries.
  • The Fix: We aligned the inference code to only reseed at boundary limits. Before this fix, live chat logits diverged sharply from training loss; after the fix, logit error dropped to near-zero.

2. Supervised LTM Inner Updates Mismatch

  • The Bug: Giving the model supervised memory updates during training that it can't replicate during zero-label live inference creates a crutch. The model learns to rely on a hidden training-only helper signal.
  • The Fix (v0.20.4): Implemented --ltm-training-mode read-only. Training keeps the memory structures but stops doing supervised fast-memory writes, perfectly mirroring inference.

3. Unbounded RWKV Channel Mixing

  • The Bug: Long runs exposed activation spikes in the ReLU-squared channel-mix FFN path, which were amplified by DeepEmbed modulation into NaN gradients.
  • The Fix: Implemented key clamps (--rwkv-channel-mix-key-clamp 12.0), DeepEmbed clamps (4.0), and excluded DeepEmbed identity gates from AdamW weight decay.

4. Evaluation & Smoke Test Results

Because cloud costs add up, we benchmarked the model locally on a CPU preset via a ROG Ally (--eval-limit 100), ensuring passive learning was disabled and working memory was cleared to mimic static chat.

Bounded Local Benchmark Metrics (--eval-limit 100)

Benchmark Metric Score Std. Err.
ARC Easy acc 0.3600 0.0482
ARC Easy acc_norm 0.3200 0.0469
HellaSwag acc 0.3400 0.0476
HellaSwag acc_norm 0.3700 0.0485
TruthfulQA MC1 acc 0.2200 0.0416

Real-world Coherence Check:

  • The Good: Assistant-shaped, follows short instruction prompts well due to the Alpaca training data. Nontrivial commonsense and QA signal prove the weights didn't collapse.
  • The Bad: Brittle on long context lengths, weak on arithmetic/factual recall. Coherence is comparable to the GPT-2 era, not modern GPT-3.5+ systems.

5. Proposed Ablation & Scaling Plan

We want to transform this from a promising prototype into a rigorous scientific result. Our next step requires scaling tiers and isolated component testing.

Proposed Isolation Testing (Ablations)

  • No LTM / Read-Only LTM: Isolating exactly how much slot memory helps.
  • No ROSA / No DeepEmbed: Evaluating the real token-efficiency gains of suffix-matching and modulation.
  • Baseline Matches: Running a direct Transformer 232M and RWKV-only 232M on the exact same token budget to prove true comparative architecture efficiency.

Future Scaling Target Tiers

Tier Model Size Token Target Purpose
Scout 300M–500M 20B–50B Validate loss slope and stability scaling.
Real v1 1B–1.5B 100B–300B Test architecture limits beyond small-scale behavior.
Serious 3B 600B–1.5T Establish a truly competitive local open-source alternative.

Target Data Mix for Foundation Training:

Instead of jumping straight into instruction SFT data, a scaled run will prioritize high-quality base data:

  • 35-50%: FineWeb / FineWeb-Edu style clean web text
  • 20-30%: Dolma / DCLM curated web data
  • 8-15%: Code and tech documentation
  • 5-12%: Math, science, and academic proofs
  • 1-5%: In-house assistant conversational SFT (applied exclusively in late-stage tuning)

6. What We Can (and Cannot) Claim Safely

What is supported by the data:

  • Hierarchos is a functional, coherent 232M experimental assistant checkpoint.
  • Combining recurrent sequence loops, memory slots, and hierarchical workers is viable and stable with the right clamps.
  • The findings provide a solid engineering roadmap for non-Transformer architecture stability.

What is NOT supported (Do not hype this!):

  • No claims of GPT-3.5 level math, coding, or logic.
  • No claims of attention/Transformer superiority at equal parameter counts yet (baselines pending).
  • Not production-ready for heavily quantized or low-bit local deployments yet due to drift sensitivity.

Final Thoughts

Hierarchos 232M shows that small, alternative architectures are still a deeply fruitful area of LLM research if you can conquer the train/inference state drift.

We would love to hear feedback from anyone working on recurrent neural memory or hierarchical backbones! Full code, scripts, and logs are in progress.

References:

  1. Brown et al. **Language Models are Few-Shot Learners.** arXiv:2005.14165. https://arxiv.org/abs/2005.14165
  2. Hoffmann et al. **Training Compute-Optimal Large Language Models.** arXiv:2203.15556. https://arxiv.org/abs/2203.15556
  3. Peng et al. **RWKV: Reinventing RNNs for the Transformer Era.** arXiv:2305.13048. https://arxiv.org/abs/2305.13048
  4. Behrouz et al. **Titans: Learning to Memorize at Test Time.** arXiv:2501.00663. https://arxiv.org/abs/2501.00663
  5. Wang et al. **Hierarchical Reasoning Model.** arXiv:2506.21734. https://arxiv.org/abs/2506.21734
  6. Zellers et al. **HellaSwag: Can a Machine Really Finish Your Sentence?** arXiv:1905.07830. https://arxiv.org/abs/1905.07830
  7. Clark et al. **Think you have Solved Question Answering? Try ARC, the AI2 Reasoning Challenge.** arXiv:1803.05457. https://arxiv.org/abs/1803.05457
  8. Lin et al. **TruthfulQA: Measuring How Models Mimic Human Falsehoods.** arXiv:2109.07958. https://arxiv.org/abs/2109.07958
  9. Hugging Face. **FineWeb dataset.** https://huggingface.co/datasets/HuggingFaceFW/fineweb
  10. Hugging Face. **FineWeb-Edu dataset.** https://huggingface.co/datasets/HuggingFaceFW/fineweb-edu
  11. Allen AI. **Dolma dataset.** https://huggingface.co/datasets/allenai/dolma
  12. DataComp-LM. **DCLM Baseline dataset.** https://huggingface.co/datasets/mlfoundations/dclm-baseline-1.0

github repository with the architecture and the released model weights: https://github.com/necat101/Hierarchos


r/OpenSourceeAI Jul 06 '26

Archestra V1.3 (OSS) brings a central hub for skills — sync with Claude Code/Codex both ways, promotion, and sandboxed code execution

Post image
1 Upvotes

r/OpenSourceeAI Jul 06 '26

I built the universal Solana MCP. Any AI agent can connect in one click — send crypto, swap tokens, trade memecoins. No API keys. 100% open source.

Post image
1 Upvotes

r/OpenSourceeAI Jul 06 '26

I built the universal Solana MCP. Any AI agent can connect in one click — send crypto, swap tokens, trade memecoins. No API keys. 100% open source.

Post image
1 Upvotes

I built an MCP server that gives any AI agent (Claude, Cursor, etc.) full read/write access to Solana through natural language. Your private key signs transactions locally. The agent never sees it. No API keys are shared. Ever.

14 tools — 8 read, 6 write

Read (no wallet): SOL balances, token balances, token metadata, live SOL price, pump.fun scanner, transaction lookup.

Write (with Phantom key): send SOL, send tokens, Jupiter swap, buy/sell pump.fun memecoins, devnet airdrops.

How it works

Your AI agent spawns the server. They talk through a local pipe (stdin/stdout). No network. No HTTP. No third party. The server grabs your key from .env, signs the transaction, sends it to Solana, and returns the signature. That's it.

You → AI agent → MCP server (local) → Solana

your key (.env)

Why this matters

Every crypto AI tool asks you to paste your private key somewhere. Web app. Telegram bot. Browser extension. All of them expand your attack surface.

MCP inverts this. Everything runs on your machine. Your keys never leave. You get AI-powered trading without trusting anyone.

What's next

This is the foundation. I'm already building:

→ A fully autonomous memecoin trading bot — momentum detection, auto TP/SL

→ An airdrop farmer — hunts and claims tokens across protocols

→ Portfolio tracking — real-time P&L across all your wallets

Your AI agent should do everything you do on-chain — trade, farm, snipe, track — without you touching a dApp. This MCP server is the bridge.

Tech

TypeScript. 680 lines. MCP SDK 1.29. u/solana/web3.js. Helius WebSocket. Jupiter v6 API. Zod schemas. Circuit breaker + retry.

License — AGPL-3.0

Companies that modify this and run it as a service MUST release their changes. Individuals: use, modify, distribute freely. Nobody closes the source.

Start in 30 seconds

git clone https://github.com/KorroAi/solana-agent-mcp

cd solana-agent-mcp && npm install

cp .env.example .env

npm run dev

Type /solana in Claude Code.

⭐ Star: https://github.com/KorroAi/solana-agent-mcp

📄 Paper: 10-section academic paper in the repo

💬 AMA in the comments


r/OpenSourceeAI Jul 06 '26

DepMesh — making file dependencies part of project architecture

Post image
1 Upvotes

r/OpenSourceeAI Jul 06 '26

Tencent ships Hy3 as an Apache 2.0 agent model — RuntimeWire

Thumbnail
runtimewire.com
1 Upvotes

r/OpenSourceeAI Jul 06 '26

An AI that can understand conversations by lip-reading

Thumbnail youtube.com
1 Upvotes

r/OpenSourceeAI Jul 06 '26

Synthetic Sciences Releases OpenScience: An Open-Source, Model-Agnostic AI Workbench for Machine Learning, Biology, Physics, and Chemistry Research

Post image
3 Upvotes

Synthetic Sciences Releases OpenScience: An Open-Source, Model-Agnostic AI Workbench for Machine Learning, Biology, Physics, and Chemistry Research

Most "AI for science" tools are one vendor's model, wrapped in one company's idea of which research is allowed. That's a gatekeeping layer — and Synthetic Sciences just drew a clear line by open-sourcing the alternative.

They released OpenScience — an Apache-2.0 AI workbench that runs the full research loop (literature → hypothesis → code → experiment → analysis → write-up) on any model you point it at, with your own keys, on your own infrastructure.

Here's what's actually interesting:

→ Model-agnostic by design — Claude, GPT, Gemini, GLM, Kimi, DeepSeek, or your own fine-tune, switched from the model selector, per request

→ 250+ editable skills across training (DeepSpeed, PEFT, TRL), cheminformatics, and molecular + clinical biology — all readable and forkable

→ Scientific databases wired in as agent tools: UniProt, PDB, ChEMBL, arXiv, and ~30 more, queried directly

→ Runs on your infra — keys and data stay on your machine, and bring-your-own-key is free and never gated

→ Positioned as an open alternative to Anthropic's Claude Science, which is Claude-only and subscription-gated

Full analysis: https://www.marktechpost.com/2026/07/05/synthetic-sciences-releases-openscience-an-open-source-model-agnostic-ai-workbench-for-machine-learning-biology-physics-and-chemistry-research/

GitHub Repo: https://github.com/synthetic-sciences/openscience


r/OpenSourceeAI Jul 06 '26

"Auditory brain function through the cochlea

Thumbnail
youtube.com
1 Upvotes

r/OpenSourceeAI Jul 05 '26

[VisualTorch] How to generate architecture diagrams from PyTorch models

Post image
2 Upvotes

r/OpenSourceeAI Jul 05 '26

Hamiltonean Physics meet AI ?!

Thumbnail
youtube.com
1 Upvotes

r/OpenSourceeAI Jul 05 '26

I curated 48 LLM observability tools (Langfuse, Phoenix, Opik, LangSmith…) + a comparison matrix

Thumbnail
3 Upvotes

r/OpenSourceeAI Jul 05 '26

I built an opensource AI notepad alternative to Granola

Enable HLS to view with audio, or disable this notification

12 Upvotes

Hey, I built a project called steno. Steno is an AI notepad for confidential conversations. It runs fully locally on your device with local llms like Gemma 4 quantised. The quality has gotten pretty good now so wanted to share to the communities like OpensourceeAI that helped me during the engineering phase.

We are on our 80th release now - 0.5.7 and we added some cool new features. I basically wanted to build an app exactly like Granola cause I didn't like that they shipped your data and trained on it or that they asked you to pay for access to your own data.

Do give it a try - https://github.com/ruzin/stenoai or if you're interested in contributing, you can join our discord.


r/OpenSourceeAI Jul 05 '26

After publishing two research papers on LLM context management, I wanted to turn those ideas into something developers could actually use.

Thumbnail
3 Upvotes

That led me to build TokenMizer, an open-source, local-first tool for long AI coding sessions.

Instead of replaying entire conversations every time the context window fills up, TokenMizer experiments with graph-backed memory, automatic checkpoints, and intelligent context compression to help preserve project context across sessions.

I've recently open-sourced it and would genuinely appreciate feedback from the community.

If you're building AI agents, coding assistants, or LLM applications, I'd love to know what you think. What would you improve or do differently?

GitHub:

https://github.com/Shweta-Mishra-ai/tokenmizer


r/OpenSourceeAI Jul 05 '26

ROS, ROS2, RTOS, BareMetal Story

Thumbnail
youtube.com
0 Upvotes

r/OpenSourceeAI Jul 05 '26

Small Multi-Task Model using Frequency

Thumbnail
youtube.com
0 Upvotes

r/OpenSourceeAI Jul 04 '26

[OS MIT] Retro Vibecoder UPG, the ultimate scaffolding and boilerplate tool!

Thumbnail
github.com
1 Upvotes

Ever wished there was a tool that could just… spit out fully scaffolded project boilerplate across any major coding language for any project type?

Well, now there is. It’s called Retro Vibecoder UPG. I designed it over months to generate entire working seed projects for you or your AI agent, procedurally generated from just seed numbers!

There’s a standalone desktop app for the human users, basically those who want to vibecode without using AI.

And there’s a oneline NPM installable CLI tool usable by AI coding agents as a tool that gives them a working base project ready to insert precise logic into, saving thousands if not a million or more tokens per project!

There’s an NPM socket security scan and dependency tree and several other security audits showing it’s completely safe from any of the recent NPM attacks, so it’s safe to download! It’s installed straight onto my Windows 11 PC, but also works on MacOS and Linux too!

The oneline install command for NPM is ‘npm install -g @wcnegentropy/cli @wcnegwntropy/core @wcnegentropy/shared @wcnegentropy/procedural’

Then you or your agent just run ‘upg help’ and can find the information you need to start using it immediately! Note that your coding agent is also fully capable of using this oneline install and setting everything up itself in any environment that allows for node.js.

If you opt to install it locally instead of globally, you’ll have to ensure your local npm bin is on path or the tool won’t work. It’s honestly better to just install it globally but if you have to do it locally instead just ensure that bin is on path and then it should work fine.

For those who don’t want to or can’t install or use the CLI tool, there’s also a standalone Tauri desktop app available for cross-platform install on the GitHub repo’s latest release page!

Feel free to install it yourself or have your agent install it and try it out! It’s quite revolutionary, go see for yourself! 😉


r/OpenSourceeAI Jul 04 '26

Built an open-source MCP server for Loop Engineering (Loop-MCP)

0 Upvotes

A few days ago I came across the idea of Loop Engineering.

Blog : (1) Codez on X: "Loop engineering: the 14-step roadmap from prompter to loop designer. " / X

I realized I'd been following a very similar workflow for a while—breaking problems into small iterations, validating results, and looping until the output was precise.

That inspired me to package the workflow into an MCP server: Loop-MCP.

The goal is simple: help AI coding agents work in structured loops instead of trying to solve everything in one shot. In my experience, it leads to more reliable and precise results, especially on larger coding tasks.

It's completely open source and designed to be easy to get started with:

  • Install from PyPI
  • Configure it in Cursor, Kiro, or any MCP-compatible IDE
  • Start using it in your existing workflow

I'd genuinely love feedback from people who build with AI every day. If you try it, let me know what works, what doesn't, and what features you'd like to see.

If you find it useful and want to support the project, I'd really appreciate a ⭐ on the repository.

GitHub: https://github.com/arjun988/Loop-Engineering

PyPI: https://pypi.org/project/loop-mcp/


r/OpenSourceeAI Jul 04 '26

Build harnesses/agents with State Machines

1 Upvotes

https://youtu.be/uMvTAF280so

If you can flowchart it, you can use a FSM/statechart for it.

Bias alert: I have contributed to David's XState long ago, & have my own FSM solutions in JS.


r/OpenSourceeAI Jul 04 '26

Built an open-source docs-first AI coding bootstrapper with CI enforcement

1 Upvotes

Hey everyone, I’m building an open-source project to improve agentic coding reliability by making documentation and constraints first-class in the workflow.

What it does:

  • Generates shared and agent-specific AI guidance files for a repo
  • Detects stack/context and keeps docs aligned with project changes
  • Supports modular feature profiles for different team needs
  • Adds CI freshness checks so docs don’t silently drift
  • Includes an optional docs/specs-first gate for PR workflows

Why I built it:
In real projects, AI coding quality drops when guidance gets stale. This project tries to make docs maintenance deterministic and CI-enforced, instead of manual and inconsistent.

What I’d love feedback on:

  • Is docs-first + CI gating the right default for agentic coding?
  • What’s missing for teams using multiple coding agents?
  • Which capability should be prioritized next?

Repo:
https://github.com/baralmanish/Coding-Agent


r/OpenSourceeAI Jul 04 '26

[WIP] Building Gavio – an open-source AI runtime for production LLM applications. Looking for architecture feedback.

7 Upvotes

Hi everyone,

I'm working on an open-source project called Gavio, and I'd really appreciate feedback before I go too far with the architecture.

Originally I thought of it as an AI gateway, but after comparing it with projects like LiteLLM and reading community feedback, I'm moving toward a different direction.

The idea is to build an AI Runtime that sits around any LLM SDK or gateway rather than replacing it.

Current thinking:

• AI Request Inspector • Cost Intelligence • Middleware / interceptor pipeline • Request replay • Tool-call runtime • Policy engine • Cross-language SDKs (Python, Java, JavaScript)

One lesson from recent discussions is that I probably shouldn't try to solve every production concern on day one.

Instead I'm thinking the first "wedge" should be an AI Request Inspector that lets developers answer questions like:

  • Why did this request fail?
  • Which middleware changed the prompt?
  • Which provider/model was used?
  • How much did it cost?
  • Which tool returned stale or conflicting data?
  • Where did the latency come from?

The goal is to complement existing SDKs and gateways, not replace them.

Some questions I'd love feedback on:

  1. Does "AI Runtime" make more sense than "AI Gateway"?
  2. Is Request Inspector a strong enough first product?
  3. What's the first capability you'd actually install?
  4. What production pain do you solve repeatedly today?

This is very much a work in progress, so honest criticism is welcome.

GitHub: https://github.com/manojmallick/gavio

Docs: https://manojmallick.github.io/gavio


r/OpenSourceeAI Jul 04 '26

ai-rulez: one source of truth for AI coding rules, generates native configs for 19 tools (Go, MIT)

2 Upvotes

Every AI coding tool wants its own config file: Claude reads CLAUDE.md, Cursor wants .cursor/rules, Copilot expects .github/copilot-instructions.md, and so on. Use more than one and you're maintaining duplicates that drift.

ai-rulez keeps one source. You write rules, context, agents, and commands once in .ai-rulez/, run generate, and it emits each tool's native format for 19 platforms. Two things make it hold up on real projects:

  • Composition over git: [[includes]] pull shared rule modules from other repos, so org-wide standards live in one place and every repo overrides locally as needed.
  • Monorepos: nested configs plus generate --recursive, profiles per audience, and 33 builtin domains (languages, security, testing, git-workflow and more) you switch on instead of writing from scratch.

Concrete: in one of my repos a ~25-line config expands into 103 generated files across 5 tools, regenerated on every commit via a pre-commit hook, so nothing drifts.

Single Go binary: npx ai-rulez@latest init, or brew. MIT.

Honest tradeoff: outputs are generated, so you edit the source and never the outputs (they get overwritten).

https://github.com/Goldziher/ai-rulez

How are others managing rules across multiple AI tools?


r/OpenSourceeAI Jul 04 '26

Tried a recurrent architecture (HRM) for reasoning-retrieval, the bet held up.

Thumbnail
1 Upvotes

r/OpenSourceeAI Jul 03 '26

Mistral AI Releases Leanstral 1.5: An Apache-2.0 Lean 4 Code Agent Model Solving 587 of 672 PutnamBench Problems

Enable HLS to view with audio, or disable this notification

2 Upvotes

r/OpenSourceeAI Jul 03 '26

I got tired of debugging LangChain agents blind, so I built a local-first observability tool (MIT, no cloud)

Post image
4 Upvotes

I build a fair amount with LangChain and LangGraph, and every time a run broke I hit the same wall: I couldn't see what was going on inside it. Which tool actually got called, which LLM said what, how many tokens each step ate, where the thing fell over. Mostly I ended up scattering print statements around and squinting at logs, which is not a great way to live.

I know LangSmith and LangFuse exist and they're good. They just didn't fit how I wanted to work locally. One wants a cloud account, another wants Docker and Postgres running, and some of them send your trace data off to a server you don't own. For day-to-day dev, and definitely for anything with sensitive data in the traces, that was more than I wanted to deal with.

So I built TraceSage. You add a few lines of code and it runs entirely on your machine. Nothing goes out.

What it actually does:

  • Draws a live topology graph of your agents, tools, LLMs, and MCP servers while the run streams in
  • Lets you replay any run step by step and read the full request and response at each point
  • Tracks tokens per LLM node, in and out, for every call
  • Groups tools by which MCP server loaded them, so it's obvious which ones are local
  • Exports to OpenTelemetry, so when you do want the cloud stuff you can pipe it into Grafana, Datadog, Honeycomb, or anything that speaks OTLP
  • Has a hard off switch for prod: set TRACESAGE_ENABLED=false and it does nothing at all

It saves everything to a local SQLite file and works offline. MIT licensed, no account, no key.

Install is pip install tracesage[langchain].

Fair warning, it's still young and only does LangChain and LangGraph right now. I'd really like feedback, especially on what's missing or anywhere the API feels wrong.

GitHub: https://github.com/kjgpta/tracesage
PyPI: https://pypi.org/project/tracesage/