I’m building STELE , a scoped memory substrate for AI agents. Go binary, SQLite by default, MCP-native (46 tools), no cloud required. It’s at the point where the core works and I need people breaking it in ways I haven’t thought of. What STELE does in 30 seconds: Gives AI agents persistent, feedback-driven memory with four scope levels ( agent / team / project / global ), graph-linked procedural workflows, provenance tracking, and multi-agent coordination — all over MCP from a single binary. Query recall benchmarks at ~42ms p50. Measured artifacts are in the repo. Also comes bundled with UI that provides most of the capabilities of the MCP/SDK in an easy-to-use interface. Full reference docs here. How you can help: User Feedback Single-agent users — Hook STELE into your existing agent setup and tell me what breaks, what’s confusing, or what’s missing from the DX. Even “I couldn’t figure out how to do X” is valuable. Multi-agent builders — The scoping model ( agent → team → project → global ), SSE streaming via stele.watch , and peer-to-peer coordination through shared memory are the pieces I most need stress-tested. If you’re running agent swarms, orchestrators, or any multi-agent pattern, I want to hear how it holds up. Edge case hunters — Large memory volumes, concurrent writes, long-running sessions, weird scope configurations. Try to make it fall over. SDK feedback — Go, Python, and JS SDKs ship today. If your language isn’t covered or the existing SDKs have rough edges, issues are welcome. Retrieval tuning — The feedback loop (success reinforces, failure demotes, time decays) and budget-aware query packing work, but there’s room to make them smarter. If you have ideas or experience with relevance scoring, I’d love the input. Workflow/procedure patterns — Procedural memories with versioning and graph edges are powerful but still evolving. If you have use cases for executable workflows stored as memory, let’s figure out what the right primitives are together. Documentation — Reference docs exist. Tutorials and guides for common patterns do not. If you get STELE working and want to write up how you did it, that would be awesome. Integration patterns — If you get STELE working with a specific framework, orchestrator, or agent platform, share it. These real-world integration examples are what the project needs most right now. Feedback of any kind: What’s the first thing that confused you? Did you experience platform specific issues? What did you expect to exist that didn’t? What would make you actually use this in a real project? Getting started: GitHub: github.com/sincover/stele Docs: sincover.github.io/stele/reference.html This isn’t a finished product asking for stars. It’s an active build looking for user feedback. If agent memory is a problem space you care about, come help shape this while the architecture is still malleable. Open an issue or just drop your experience in the comments. All of it helps. submitted by /u/sincover
Originally posted by u/sincover on r/ClaudeCode