PeppermintGet started

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.

Get startedSee it in action

Not locked to one tool. Not trapped in one thread. Your context moves with you.

Google DocsGoogle SheetsSlackGmailGoogle CalendarNotionFigmaGoogle ChromeYouTubeAsana

The problem

Your work gets scattered.Your context shouldn't.

Work happens across chats, docs, tickets, code, and meetings. Peppermint can help you answer work questions without pulling you out of flow state.

FinderFileEditViewGoWindowHelp
Lunch · 37m leftMon 9:41 AM
Search Everis
# peppy-all-team13 members

Thread open

Today
L
Liam Martin9:09 AM

@Abdullah @Sabrina Can you tell me what still blocks Tuesday's launch? Pull Linear tickets and Figma context.

Slack Twin

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.

Slack
Reply surface

Launch handoff

Summary can post to the launch channel after you approve it.

Selected destination
Docs
Private note

Launch prep note

Source context stays in your own memory unless you choose to share it.

Available, not active
Linear
Issue context

PEP-311 OAuth SSO bug

Pull the thread into a ticket reply without exposing the full working set.

Available, not active

Control

Private memory routing

Live
Private by default

Start inside your own memory layer.

Reply surface

Choose where Peppermint is allowed to show up.

SlackDocsLinear
Share with selected collaborators

Bring in context when the handoff needs it.

Launch teamProductOps
Keep source context private

Only the summary leaves your private memory.

Ask before posting