mem

Rules and guards

Rules your agents follow, and guards they cannot get around.

Memories tell the agent what to do. Rules make sure it happens: they run in the hooks, before and after the agent acts, so the agent cannot skip them.

What a rule does

ActionEffect
BlockThe command or edit does not run
Ask firstThe agent stops and asks you; it goes on only after you say so
RemindThe agent gets a message right when it matters
Add memoriesPuts chosen memories into the session
NoteRecords the event, nothing else

A rule can match commands (git push), files, tools or words in the prompt, and run every time, once per answer, once per session, once per command or file, or once per person.

Examples

  • Never restart, stop or kill containers, services or the host.
  • Dropping a database needs my OK.
  • terraform destroy only when I asked for it.
  • Editing secret files needs my OK.
  • No co-author or AI lines in commits.

Add them from Ready rules under Rules or write your own.

Procedures

A procedure is a checklist for a recurring task, such as a release or a server launch. You give it start words and steps; each step is done when something happens: a command that succeeds (git push), a tool call, a skill, an edited file, or a note another rule records.

  • When a prompt holds a start word, or the agent does what starts it (a skill, a command, an edited file), the agent gets the checklist and the procedure's memories.
  • Every step is checked off from what the agent really does. A command that fails does not count.
  • After each step the agent sees where it stands: api-release: Tests done (3/5 required), next: Push.
  • If the agent wants to stop with required steps open, it is held once per run and told which steps are missing. Optional steps never hold it.
  • Saying the start words again in the middle of a run keeps the done steps; a finished run starts over.

Owners add and edit procedures under Rules, Procedures. Agents can propose one from chat; it works once the owner confirms it.

Rules and procedures for a space

A rule or procedure can belong to a team space: it then holds only for the people who can read that space. Ask your agent for it in chat ("only in the Backend space"), or add it on the space's Rules tab. Rules for the whole team stay on the Rules page.

Trial run

Before you save a rule, Trial run shows how often it would have fired in the last 7 days of your team's sessions.

Activity

Every time a rule blocks, asks, reminds or adds memories, axs mem logs it for 30 days: the rule, the person, the repo, the client and what it matched (only a command's first words or a file pattern like **/prod/*.env, never the full command). Under Rules, each rule shows how often it fired, and Activity lists the latest hits; click a count to see only that rule. Owners see the whole team, members their own.

Team rules

In a team, rules a member or an agent proposes wait for an owner in To confirm. A rule can apply to everyone or only to one person.

axs mem's own rules

The pushes on How it works are rules too. Under Rules, axs mem you can turn each one off or limit it to the main agent or to subagents.

On this page