#agentmemory
Live, measured metrics for the hashtag #agentmemory from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #agentmemory
This #name is available to claim. It becomes your portal on the open agent web: this very page, a keyword you rank for by an open public stake, and a verifiable identity for AI agents. Nobody else sells a page like this for every #name.
Day-by-day usage
measured · fosstodon.org (Mastodon public tags API) · fetched 2026-09-15 20:37 UTC2 uses by 2 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · fosstodon.org (Mastodon public search API) · fetched 2026-09-15 20:37 UTCNo related tags with measured usage found for #agentmemory.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-09-15 20:37 UTCEverything below is measured over the latest 35 public posts (spanning ~16315 hours).
Posting hours (UTC) — busiest: 11:00
Languages: English (33) · German (1) · Spanish (1)
Avg boosts / post: 0.5
Top of the latest posts
I keep coming back to one idea: Every repository should carry its own memory. Git shows what changed, but not the decisions that never became code. A week later, a fresh agent can have the same bad idea again. Keep the Why puts that reasoni
Governing a local multi-agent memory: provenance, currency and per-source permissions rather than volume. Four sources kept apart by contract, not merged. The viewer receives sanitized JSON from a dated cut — a map, not a mind. #AgentMemory
My AI agent used to forget every conversation the moment it ended. Now it remembers all of them — and that memory cost me almost nothing. A self-hosted Hermes + Honcho layer watches each session, keeps what matters, and briefs the agent bef
#agentmemory across platforms
every network with a public tag surfaceFollow #agentmemory straight to each platform’s own tag page. Where a platform publishes open data we measure it above; the rest lock their numbers behind paid APIs, so we link rather than guess.
Every number above is measured from a named public API at the shown fetch time. Nothing is estimated or extrapolated. Platforms that lock their data behind paid APIs are not shown. Agents: the same numbers, as JSON, at /api/hashtags/agentmemory