#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.

hashtag.org network · sponsored

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.

$10.85/ year · 11-character #name
Claim #agentmemory — $10.85/yr→Buy on hashtag.space (web3)
card via hashtag.org · tokens via hashtag.space
4
Uses / 7 days
Mastodon
4
Accounts / 7 days
Mastodon
39
Recent posts
Mastodon
~0/hr
Recent pace
Mastodon · last 39
0.1
Avg reactions / post
Mastodon · last 39
—
Reddit posts / month
Reddit search
—
Open-web mentions
hashtag.org Firehose

Day-by-day usage

measured · mas.to (Mastodon public tags API) · fetched 2026-10-17 18:00 UTC
2
10-11
1
10-12
1
10-13
0
10-14
0
10-15
0
10-16
0
10-17

4 uses by 4 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.

Related hashtags

measured · mas.to (Mastodon public search API) · fetched 2026-10-17 18:00 UTC

No related tags with measured usage found for #agentmemory.

Live pulse

measured · mas.to (Mastodon tag timeline) · fetched 2026-10-17 18:00 UTC

Everything below is measured over the latest 39 public posts (spanning ~17018 hours).

Posting hours (UTC) — busiest: 11:00

00:0012:0023:00

Languages: English (38) · German (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

    Oliver Zehentleitner@oliverzehentleitner@burningboard.net♥ 3↻ 82026-09-08 11:05 UTCView post →
  • Keep a Changelog tells you what changed. Keep the Why keeps the reasoning behind it: decisions, rejected ideas, constraints and workarounds, stored as Markdown in the repo. Project memory for humans and coding agents. No database. No daemon

    Keep The Why@keep_the_why@mastodon.social♥ 1↻ 02026-09-08 11:18 UTCView post →
  • I've been exploring different approaches to agent memory. Keep the Why, past.dev, Agent Memory Repo and agentmemory all preserve different kinds of knowledge, in different places. I wrote a comparison covering their strengths, limitations a

    Oliver Zehentleitner@oliverzehentleitner@burningboard.net♥ 0↻ 12026-10-13 12:56 UTCView post →

#agentmemory across platforms

every network with a public tag surface

Follow #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