Skip to main content

​
remember

Creates or updates entities in your knowledge vault.

​
Parameters

ParameterTypeRequiredDescription
namestringYesName of the entity
entity_typestringYesType: person, project, concept, technology, decision, etc.
contentstringYesKnowledge to store
related_tostring[]NoNames of related entities to link

​
When your AI calls this

Your AI will call remember when:
  • You share a decision: “We’re going with PostgreSQL for the new service”
  • You mention someone new: “I just started working with Maria on the frontend”
  • You correct something: “Actually, the deadline moved to March 15”
  • You explicitly ask: “Remember that the API rate limit is 1000 req/min”

​
Examples

Storing a decision: 
remember(
  name: "Database choice for payments service",
  entity_type: "decision",
  content: "Decided to use PostgreSQL instead of MongoDB for the new payments service. Reasons: ACID compliance, team familiarity, existing infrastructure.",
  related_to: ["payments service", "PostgreSQL"]
)
Recording a person: 
remember(
  name: "Maria Santos",
  entity_type: "person",
  content: "Frontend engineer working on the dashboard redesign. Reports to David. Joined the team in January 2026.",
  related_to: ["dashboard redesign", "David"]
)

​
Updates vs. creates

If an entity with the same name already exists, remember updates it with the new information. Previous versions are preserved. BaseLayer maintains a version history so no knowledge is lost.
You don’t need to worry about duplicates. BaseLayer intelligently merges new information with existing entities.