Memories
How Cleric remembers facts about your environment
Memories are facts that Cleric learns from your conversations and uses to improve future investigations. They cover everything from system architecture and alert behavior to how you want Cleric to respond.
How Memories Work
When you interact with Cleric during an investigation, it identifies useful facts from your interactions and offers to remember them. These memories are then used in future investigations to provide more accurate and contextual analysis.
Categories
Cleric classifies each memory into one of these categories:
Alerts & Runbooks: triage rules, known false positives, escalation policy, and incident remediation playbooks
Architecture & Data: service dependencies, ownership, deployment topology, data stores, and data flows
Observability: where and how to query data, including dashboards, log and metric sources, queries, and metric names
Infrastructure: the platform layer beneath services: cloud accounts, Kubernetes, networking, and capacity
Auth & Security: authentication, authorization, secrets management, and security posture
Integrations: third-party vendors, external APIs, and the failure modes they introduce
Deploy & Release: CI/CD pipelines, rollout patterns, and release mechanics
Developer Workflow: source repositories, code and config locations, team ownership, and development conventions
Domain & Product: terminology, acronyms, business rules, and customer or company specifics
Agent Behavior: how Cleric should respond, including language, format, scope, and output conventions
Cleric organizes the broader knowledge it gathers into these same categories. See How Cleric Learns.
Memory Proposals
After you send a follow-up message during an investigation, Cleric may propose a memory based on what you shared.
Example: Accepting a Memory
During an investigation, you might share context:
Cleric will propose a memory:
Click Remember to save the fact. Cleric confirms:
Example: Rejecting a Memory
Sometimes Cleric might propose a memory that's not quite accurate:
If this isn't accurate (maybe high memory usage is normal during certain operations), click Reject:
You can then provide the correct context:
Cleric will propose a corrected memory based on your clarification.
Saving and Deleting Memories Directly
In addition to memory proposals, you can directly tell Cleric what to remember or forget during any conversation.
Saving a Memory
Cleric saves the fact immediately and confirms. This is useful when you want to teach Cleric something without waiting for it to propose a memory.
Deleting a Memory
Cleric finds the matching memory and removes it. Use this to correct outdated information or remove facts that no longer apply.
Managing Memories from the Web App
Open Knowledge > Memories in the sidebar to browse, search, and filter every memory Cleric has stored. Click Add memory to save a fact directly, or hover a row and click the trash icon to delete one. These are the same operations as @Cleric Remember… and @Cleric Forget… in Slack.
How Memories Are Used
During investigations, Cleric automatically searches its memory for relevant facts based on the services, environments, and topics involved.
For example, if Cleric is investigating an issue with the checkout service, it will search for any memories related to:
The checkout service specifically
Services that checkout depends on
The environment where the issue occurred
Similar alert patterns
This helps Cleric:
Identify dependencies that aren't visible in monitoring data
Apply your preferred investigation approaches
Avoid paths you've indicated aren't useful
Recognize known patterns and false positives
Querying Memories
You can ask Cleric what it remembers about specific services, environments, or topics.
Example: Service-Specific Memories
Cleric's response:
Example: Environment-Specific Memories
Cleric's response:
Memory Cleanup
Cleric reviews its memories after investigations to keep them accurate and relevant. Memories are removed when they:
Haven't been relevant to recent investigations
Are contradicted by newer information you've provided
No longer apply due to infrastructure changes
Last updated