PEP-311 OAuth SSO affects sign-in copy.
PeppermintConnect to ClinePeppermint for Cline
Connect Peppermint to Cline
Cline remembers your repo. Peppermint remembers the work around it: Slack decisions, Linear tickets, docs, meetings, browser context, and what changed on your computer before Cline starts editing.
Slack decisionsLinear ticketsGoogle DocsMeetingsBrowser contextLocal files
user
Before I change onboarding, what context should I know?
Cline
Calling Peppermint before plan mode...
peppermint.memory.search
query: onboarding, OAuth, download trackingAbdullah flagged callback edge cases.
Sabrina updated first-run onboarding direction.
suggested Memory Bank updateactiveContext.md
+ preserve download attribution before changing CTA routes
+ keep OAuth SSO language consistent with PEP-311
+ review callback copy before editing onboarding flow
The gap
Memory Bank keeps the repo straight. Peppermint brings in the work around it.
Cline should not have to infer the whole story from code alone. It can ask Peppermint for the Slack, Linear, docs, and meeting context that explains what changed.
Great at remembering the repo.
Markdown files like projectbrief.md, activeContext.md, and progress.md help Cline carry project state across tasks.
Built for the work around the repo.
Peppermint captures fresh context from the rest of your workday so Cline can understand the decision before it changes the code.
What Cline can ask
Better questions before Plan and Act.
Peppermint gives Cline a memory source for the information that usually lives outside the editor.
What changed since my last Cline session?
Recent decisions, tickets, docs, and conversations that changed the implementation path.
What belongs in activeContext.md?
A clean, current-state summary Cline can write into Memory Bank with your approval.
Which artifact explains this feature?
The Linear issue, doc, Slack thread, or file that gives Cline evidence before it edits.
What assumption would be expensive?
Anything the repo cannot know: launch timing, design direction, customer language, or PM decisions.
Setup
Three steps to give Cline live work memory.
- 1
Download Peppermint
Let Peppermint build a private work memory from the apps and surfaces where your context already lives.
- 2
Connect Cline through MCP
Add Peppermint as a remote server from Cline's MCP Servers panel, then choose Streamable HTTP.
- 3
Ask before Plan and Act
Tell Cline to query Peppermint before editing, then approve any Memory Bank file updates.
Remote server previewTransport: Streamable HTTP
https://api.peppermint.com/mcp/your-workspaceFAQ
For Cline power users who already have a system.
No. Memory Bank is still the project memory inside your repo. Peppermint brings in the work context that lives outside the repo, then helps Cline turn it into better Memory Bank updates.
Cline is built around human approval. The right flow is for Peppermint to provide the current context, Cline to propose the Memory Bank update, and you to approve the file change.
Current work focus, recent decisions, next steps, and anything Cline needs before editing. Peppermint is useful because it can bring in the latest state from Slack, Linear, Docs, meetings, and your desktop instead of relying only on what is already in the repo.
Manual updates are fine until the context lives in five other tools. Peppermint gives Cline the raw material for a cleaner update, then you approve what actually gets written.
Ask for recent decisions, relevant artifacts, blockers, collaborator notes, and what changed since the last coding session. The goal is less guessing before code changes.
No. Peppermint is a memory layer. Cline still follows its approval model for tool use and file changes, which is exactly what you want when memory is being turned into code edits.
Launch timing, product decisions, customer language, Slack threads, Figma or doc direction, Linear priorities, meeting outcomes, and the reason a change matters now.
Peppermint exposes work memory through an MCP server. Cline connects to that server, asks for relevant context, then uses the returned memories and artifacts inside Plan and Act workflows.
This page is for Cline users, but the same Peppermint memory layer can support Claude Code, Codex, and other MCP-capable agents.
Both, but the strongest fit is a founder or operator using Cline across product, code, docs, and customer conversations. Peppermint helps Cline understand the whole work loop, not just the repository.
Paid traffic path
Stop making Cline rediscover your week.
Add Peppermint, connect your work context, and let Cline ask for the missing memory before it edits.