​

Memory Types Reference

​

Why Memory Types?

1. Organization - Group related memories instead of throwing everything into a generic “notes” bucket.
2. Filtering - Query specific types (e.g., retrieving only “commitments” or “preferences”).

​

Quick Reference

​

Detailed Definitions

​

fact

• Static information
• Not opinions or preferences
• Verifiable claims
• Core knowledge

• “Paris is the capital of France”
• “Database uses PostgreSQL”
• “Team has 5 engineers”

memanto remember "Paris is the capital of France" --type fact

​

preference

• Opinions about preferences
• User/system choices
• Style choices
• Communication preferences

• “Prefers dark mode”
• “Email over phone”
• “Concise responses”

memanto remember "Prefers email contact" --type preference

​

decision

• Technology choices
• Process decisions
• Strategic choices
• Why decisions

• “Chose TypeScript for codebase”
• “Decided to use AWS”
• “Selected Agile methodology”

memanto remember "Chose PostgreSQL for database" --type decision

​

commitment

• Deliverables
• Promises to keep
• Obligations
• Accountability

• “Will deliver report by Friday”
• “Committed to 10% growth”
• “Promised 24/7 support”

memanto remember "Will deliver API docs by Friday" --type commitment

​

goal

• Future targets
• KPIs
• Milestones
• Aspirations

• “Reach 1M users”
• “Improve performance by 50%”
• “Launch MVP by Q2”

memanto remember "Launch MVP by March 31" --type goal

​

event

• Historical events
• Meetings
• Incidents
• Milestones

• “Had meeting with CEO”
• “System outage on March 20”
• “Project launched successfully”

memanto remember "Team meeting at 2pm" --type event

​

instruction

• Policies
• Best practices
• Procedures
• Constraints

• “Always validate input”
• “Follow REST conventions”
• “Require code review”

memanto remember "Always validate user input" --type instruction

​

relationship

• People relationships
• System dependencies
• Business relationships
• Hierarchies

• “Alice manages Bob”
• “Project X depends on API Y”
• “Customer referred by John”

memanto remember "Alice manages Bob" --type relationship

​

context

• Seasonal context
• Business phases
• System states
• Environmental factors

• “In Q1 planning phase”
• “Budget season is active”
• “System in maintenance”

memanto remember "We're in Q1 planning" --type context

​

learning

• Insights
• Lessons
• Patterns recognized
• Knowledge gained

• “Users need better onboarding”
• “Mobile-first is essential”
• “Documentation must be clear”

memanto remember "Users need simpler onboarding" --type learning

​

observation

• Patterns observed
• Trends noticed
• Data observations
• Field observations

• “Traffic peaks on Fridays”
• “Users skip step 2”
• “Support tickets spike after releases”

memanto remember "Traffic peaks on Fridays" --type observation

​

error

• Warnings
• Lessons from failures
• Anti-patterns
• Known issues

• “Avoid deprecated API”
• “Skip validation=bug”
• “Don’t hardcode secrets”

memanto remember "Never skip input validation" --type error

​

artifact

• Documents
• Code files
• Resources
• References

• “Q3 budget spreadsheet”
• “API documentation file”
• “Customer contract”

memanto remember "Q3 budget spreadsheet" --type artifact

​

Selection Guide

Does it describe something that happened?
  → event

Is it a choice or decision?
  → decision

Is it a promise or obligation?
  → commitment

Is it a rule or guideline?
  → instruction

Is it someone's preference?
  → preference

Is it an objective fact?
  → fact

Is it a future goal?
  → goal

Is it a lesson learned?
  → learning

Is it a pattern observed?
  → observation

Is it a warning or mistake?
  → error

Is it a connection between things?
  → relationship

Is it situational info?
  → context

Otherwise, ask: "Is it a document/file?"
  → artifact

​

Best Practices

​

DO

• Use specific types for better organization
• Choose the most specific type available
• Be consistent in your selections
• Filter queries by type when appropriate

​

DON’T

• Overuse generic “fact” type
• Store everything as one type
• Mix unrelated information in one memory
• Ignore type distinctions
• Use wrong type for convenience
• Skip commitment type for promises
• Forget about error type for lessons

​

Filtering by Type

​

CLI

# Get only commitments
memanto recall "what must we do" --type commitment

# Get only preferences
memanto recall "what does user like" --type preference

# Get only decisions
memanto recall "why did we choose this" --type decision

​

API

response = httpx.get(
    f"{base}/agents/{agent}/recall",
    params={
        "query": "What must we do?",
        "memory_type": "commitment"
    },
    headers=headers
)