llmemory: memoria persistente para agentes LLM en Ruby
Descubre llmemory, la gema Ruby que resuelve la amnesia de los LLM dotando a tus agentes de memoria persistente a corto, largo plazo y cognitiva para conversaciones inteligentes.
Claude Code forgets everything when a session ends. I built recall to fix that — a self-improving memory layer that captures sessions, distills durable knowledge nightly, and feeds it back automatically.
zarpay/rails-template: Opinionated, agent-native Rails template — the production Rails starter ZAR uses internally, packaged with a CLAUDE.md operating manual, 32 Claude skills, and 17 path-scoped coding rules.
Opinionated, agent-native Rails template — the production Rails starter ZAR uses internally, packaged with a CLAUDE.md operating manual, 32 Claude skills, and 17 path-scoped coding rules. - zarpay/...
danielstpaul/silas: Your Rails app is already an agent runtime — durable AI agents on Rails: exactly-once tool ledger, park-at-zero human-in-the-loop, operator inbox.
Your Rails app is already an agent runtime — durable AI agents on Rails: exactly-once tool ledger, park-at-zero human-in-the-loop, operator inbox. - danielstpaul/silas
mcheemaa/mistri: The agent harness for Ruby applications. Durable sessions, streaming, human-in-the-loop approval, compaction, structured output, sub-agents, and MCP, with zero runtime dependencies.
The agent harness for Ruby applications. Durable sessions, streaming, human-in-the-loop approval, compaction, structured output, sub-agents, and MCP, with zero runtime dependencies. - mcheemaa/mistri
Durable sessions in your own database, streaming, human-in-the-loop approval, compaction, structured output, sub-agents, and MCP. Zero runtime dependencies.
The complete toolkit for the Open Knowledge Format: an agent that authors, curates, and consumes your knowledge, a CLI and library, and a graph to explore, live or static. Open source, 100% local.
Adopting a knowledge format usually means rewriting what you already wrote, which is why adoption stalls. /okf migrate, new in 1.7.0, adopts your existing Markdown in place: frontmatter and reserved files added, every body kept verbatim. The links you wrote years ago become the graph on day 0, and produce, search, and maintain compound from there.
Hot path optimization: unsafe pointer arithmetic to eliminate bound checks the Go compiler can't remove, given you can prove they are truly unnecessary.
I’m at RubyConf this week, and it’s great!
I recently read that lobste.rs is now running on SQLite. One part from the post caught my attention:
I wish we could say in a test, “Fail if you encounter any full table scans”. Which would have caught the perf issues we experienced during the first deploy.
SQLite collects information about prepared statements and exposes those statistics though an API. The upshot of this is that we can tell whether a statement did a full table scan after executing the statement without using an EXPLAIN.