Skip to content
engineer9 docs

Memory

engineer9 keeps a persistent memory of your team: the context it has learned from the channels it listens to. It draws on that memory every time it answers, so its responses reflect your systems, your people, and your history rather than generic knowledge.

What it remembers

Section titled “What it remembers”
  • Team roster: who someone is and what they own, learned from channel activity
  • Playbooks: how an incident or recurring issue was resolved (see Playbooks)
  • Team knowledge: systems, dependencies, and decisions as they come up

It saves these as it learns them, and surfaces the relevant pieces when you ask.

Asking what it knows

Section titled “Asking what it knows”
@engineer9 what do you know about our team?
@engineer9 do you know anything about the auth service timeouts?
@engineer9 show me the playbooks you have

Reviewing what it knows

Section titled “Reviewing what it knows”

Sign in to your dashboard to read what engineer9 has learned: its memory, the team roster, and saved playbooks. These are read-only views. To correct or add something, tell engineer9 in Slack; it updates its own memory as it learns. See Channels & access for how the roster is built.

Section titled “Related”