mem

How it works

What axs mem puts into a session, and how memories are saved.

Memories come to the agent

Agents rarely search for what they do not know they are missing, so axs mem pushes memories in at the right moment:

WhenWhat the agent gets
Session startYour always-on rules
First work on a project, server or toolThe memories of that project, server or tool
Every promptThe memories that match it
After changes to infra, deploy files or servicesThe memories that may now be outdated

The agent can also search on its own with memory_search and read a memory in full with memory_get.

Lessons are saved while you work

When you correct the agent, axs mem asks it at the end of its answer to save the lesson as a short memory. It checks for near-duplicates first and updates those instead. Memories with secrets are refused.

You can tell it directly too: "remember that we deploy with make release" or "forget that".

A memory

  • Type: rule, preference, procedure, fact, incident, project, lesson or log.
  • Scope: global, or what it is about, such as project:billing-api or host:web-1.
  • Space: your private space or a team space.
  • Always on: a few rules can go into every session. When an agent writes one, it waits in To confirm until a person confirms it.

Every change is kept in the history of the memory and can be undone in the dashboard. Memories can carry files such as logos, images or PDFs (up to 25 MB each).

Changelog

Teams with the changelog turned on keep a shared log of what was built: after a push the agent adds an entry with changelog_log (title, type feature, improvement or fix, projects and short bullets), one per feature per day. changelog_list reads it by day or range, project, person or type, and searches it:

  • query: words that must all be in an entry, "a phrase" in quotes.
  • version: entries whose title names a version, such as 2.12.90 or a range 2.12.90..2.12.121.

A search without a day looks through the whole changelog and answers with the newest 50 hits.

When axs mem is down

Your agent keeps working without memories: every hook gives up after a few seconds. Rule checks pause too, unless an owner sets When axs mem is unreachable to Block risky commands in the team settings.

On this page