Private work memory
Let your workspeak for you.
Peppermint is your private memory for work. It moves with you across Slack, Notion, Asana, Docs, Codex, Claude Code, and more, so you can ask questions, draft updates, and get useful answers in context right where the conversation is happening.
The problem
Your work gets scattered.Your context shouldn't.
Work happens across chats, docs, tickets, code, and meetings. Each time you switch tools, the thread behind what you were doing gets harder to recover.
Peppermint keeps that thread intact, so you do not have to dig through old messages, reopen tabs, or reconstruct the story just to move the work forward.
Control
Private first.Collaborative when useful.
Peppermint starts with your own memory for work. Then, when it helps, you can bring that context into handoffs, updates, and team conversations.
You decide where it shows up, when it responds, and what stays private.
SlackLaunch handoff
Summary can post to the launch channel after you approve it.
DocsLaunch prep note
Source context stays in your own memory unless you choose to share it.
LinearPEP-311 OAuth SSO bug
Pull the thread into a ticket reply without exposing the full working set.
Control
Private memory routing
Start inside your own memory layer.
Choose where Peppermint is allowed to show up.
Bring in context when the handoff needs it.
Only the summary leaves your private memory.