Memory
What Stevin remembers within a conversation, how to start fresh or shorten a long one, and how to make it keep your team's rules.
Within a conversation#
Within one conversation, Stevin remembers what was said earlier. You can say "do another one in the same format" or "change the second item".
In a long conversation, earlier content is condensed into a summary that keeps the main points. If it has lost an earlier detail, say it again.
Manage a conversation yourself#
In chat, a few commands act on the conversation itself:
| Command | Use it to |
|---|---|
/new |
Start a fresh conversation. The old one is archived, not deleted |
/compact |
Fold the earlier turns into a summary and carry on. Add a focus to keep, for example /compact keep the pricing |
/context |
See what this conversation's context currently holds |
/undo |
Bring back the conversation that the last /new archived. Send it again to swap back |
A command only affects the conversation it is sent in: your own direct-message conversation, or the group thread you sent it in. It never touches anyone else's conversation, and files are untouched.
Start a new conversation when you change topic. Stevin answers better, and faster, when the conversation holds only what matters for the task.
Across conversations#
A new conversation does not carry over what was said in another one. For anything Stevin should know every time, do not rely on it remembering a chat: write it down where it always looks.
Make it keep your team's rules#
The reliable way to make Stevin follow a rule every time is a skill:
- Your team's fixed formats and templates.
- Definitions of terms and internal names.
- The criteria for handling a kind of case.
Skills are plain text with a revision history, so anyone can see what Stevin is working from, and changes are easy to follow.
What it cannot recall#
- Content in systems that are not connected.
- Content the person asking is not allowed to see. Whose data Stevin may read on someone's behalf is set under Permissions.
For how data is handled, see Security and data.