What memory is
Memory is FixControl's behavioral layer. It's a small set of rules and context that gets pasted into every agent prompt, before the agent sees the user request or the issue. Memory doesn't change what an agent can do — it changes how it decides and how it answers.

You manage memory at /memory. You'll find two tabs (Global and Project), an editor, and a panel of auto-detected suggestions you can accept or reject.
Global vs project memory
There are two scopes:
- Global memory — applies across the entire tenant. Every agent, every issue, every project sees these rules. Use it for organization-wide policy: tone of voice, prioritization rules, hard prohibitions.
- Project memory — only injected for issues linked to that specific project. Use it for project-specific conventions: deploy procedures, known API quirks, ownership per component.
Global memory is injected first, project memory next. The two are additive — project memory does not replace global memory, it extends it.
Writing a good memory entry
Good memory is short, normative, and context-free. One rule, one point. An example of a solid global rule:
Triage critical bugs within 1 hour — Any bug with priority critical must be assigned to a person and classified within one hour of arrival. Reason: prevent production impact from going unnoticed.Avoid vague phrasing ("be careful"), long explanations, or historical context. If a rule describes a change ("we don't do X anymore"), write it directly as the current norm ("do Y").
How agents use memory
On every agent run, FixControl assembles a memory block from all active, non-superseded entries and gives it to the agent before it looks at the request. As a result:
- Agents follow your rules without you having to repeat them in every request.
- Behavior stays consistent across the Ticket Analyst, the Operations Coordinator, and any custom agents.
- FixControl tracks how often each rule actually gets used, so cold rules can be pruned later.
Memory vs knowledge
The distinction is fundamental:
- Memory is always injected — short, normative, behavior-shaping. Good for rules, preferences, decisions. Keep it small.
- Knowledge is retrieved on demand — reference material, documentation, long-form content. An agent searches it when the request calls for it.
Rule of thumb: if it should always apply, it belongs in memory. If it's only sometimes relevant, it belongs in knowledge.
FAQ
Do my hand-written notes also get injected? Yes. The free-form editor still works alongside typed entries.
Can I remove a rule without losing history? Yes — delete removes the rule outright, but you can also have a newer rule "supersede" an older one. The old one stays visible in the audit trail but is no longer injected.
What are those suggested rules at the bottom of the page? Patterns FixControl detects in your issues and agent runs. Click Accept to turn one into a memory entry, or Reject to discard it.