Beta is live, 0 / 200 seats claimed

Catch what slips through
ClickUp, Slack & Teams.

It's 9am Monday. Coffee in hand. Slack still loading. Pickle has already read your week. The 40-hour task with no description. The "shipping today" from 3 days ago. The decision in a group DM that never reached the card. Nine patterns a good ops manager would catch in ClickUp by day three, Pickle catches them in 5 seconds. Free during Beta. More patterns and smarter automation keep landing.

An ops manager costs $80k a year. Pickle costs an email. Free plan stays free, forever.

Hire Pickle For Free See how it works
No card. Just an email. Token never stored Open source · MIT Founder-built · founder-supported
ClickUp · audited live Slack · audited live Microsoft Teams · audited live
Aditya Sharma A Built by Aditya Sharma · used by my own team and 6 founder friends in private beta
// what pickle catches

Three workspaces. One audit.

A good ops manager catches this stuff by day three. Pickle does it before standup. Pick a platform tab and see three real catches Pickle would flag for you this morning.

ClickUp Pattern 01 · Empty hours
Pickle catch · ready in your morning brief
XYZ-184 has 47h logged this week. Comments: 0. Descriptions: "API improvements" × 4. Ask David in standup what shipped.
Slack Pattern 09 · DM-only completion
Pickle catch · ready in your morning brief
DM says "shipped the auth refactor" 6 days ago. Card XYZ-72 still In Progress, no comment since assignment. Either close it or call it WIP.
Microsoft Teams Pattern 12 · Decisions in DM
Pickle catch · ready in your morning brief
Decision made in #founders chat 6 days ago: "go with Stripe Checkout, not custom." Planner task XYZ-203 description still says TBD. Update before the team rebuilds context.
// how it works

60 seconds. Your AI installs Pickle for you.

No npm, no terminal hacks, no JSON to hand-edit. You email-sign-up, paste a prompt into your AI assistant, and it installs Pickle into its own MCP config — alongside everything you already have. Then you say "Pickle Start" and the guided setup begins in chat.

1

Drop your email — get the install prompt

Sign up below. I email you a one-time install prompt that includes your unique Pickle key. Takes 10 seconds, no card.

→ check your inbox
2

Paste the prompt into your assistant

Open Claude Code / Cursor / Cline / Codex (anything with file-edit tools). Paste the prompt as your first message. The AI adds Pickle to your existing MCP config without touching anything else.

→ AI installs · safe harbour
3

Restart, then say "Pickle Start"

When the AI confirms "MCP Installed", restart your assistant. Open a new chat, type "Pickle Start". Guided setup begins — pick a platform, paste your token, you're connected.

→ chat-guided per platform
4

Ask what needs you today

"Pickle, audit my ClickUp from last 24 hours." Pickle scans, ranks the catches, hands back a plain-English brief in under 5 seconds.

→ ranked brief in <5s
// 9 free + 4 pro patterns

The work that quietly falls through.

Thirteen failure modes a good ops manager would catch. Nine are free in Beta (all pure ClickUp). The other four — cross-tool catches that need Slack / Teams chat data or multi-person reports — land later as Pickle grows. I'll email when each one ships.

01 · empty hours
most common
Time logged, nothing shipped

Hours pile up on a task. Descriptions are blank or "8h development". The dashboard says someone's working; nothing in the artefact says what they built.

Real catch · Tuesday
XYZ-184 has 47h logged this week. Comments: 0. Description: 'API improvements'. What are we paying for?
02 · stale in-progress
silent killer
"In progress" for six weeks

Not blocked. Not done. Just sitting. The kind of task you find in your monthly review and realize it's been moving sideways since March.

Real catch
XYZ-87: In Progress · 43 days. Last comment: 19 days ago. Pickle flagged it Wednesday before standup.
03 · zombie tasks
hides in plain sight
Assigned. Never touched.

30+ days since assignment, never opened, never mentioned in any chat. Lives in the list like a forgotten password. Counts in every report as "pending."

Real catch
Sarah has 4 tasks from March. Two shipped. Two haven't been opened since assignment. Ask her about XYZ-45 and XYZ-67.
04 · standup copy-paste
fake updates
Same standup three days running

When the standup message is >85% identical to yesterday's, it's not an update. It's a placeholder. Pickle catches the similarity and flags those days as zero-evidence.

Real catch
Mon/Tue/Wed standups from David: identical text. Two pixels different. The week shows no actual progress.
05 · expired promises
trust erosion
"Shipping by Friday", said Monday

Soft commitments in chat die in scrollback. Pickle reads ClickUp comments + chat, anchors the temporal commit, and flags it by Friday EOD with the exact quote.

Real catch
Mon 10:42am: "Will land the migration by Friday." Friday 6pm: still open, no comment in 48h.
06 · blocker age
auto-escalate
Blocker raised, nobody cleared it

Blocked status is fine for a day. Two weeks is a process failure. Pickle stamps days-unresolved on every blocker; auto-🔴 at 14 days, asks who owns the unblock.

Real catch
XYZ-91 has been "Blocked: waiting on legal" for 17 days. Pickle: who is your contact at legal? Loop them.
07 · effort-output mismatch
budget leak
40h logged. Zero comments. Still open.

High effort + low signal + still-open status = a task that's quietly burning your runway. Pickle cites hours, comment count, and the window so you can ask the right question.

Real catch
"Pricing page" task: 38h across two contractors. 0 comments. Status hasn't changed in 11 days. What's the holdup?
08 · ghost mode
Pro
Silent across every surface

Comments: 0. Chat messages: 0. Task updates: 0. For 40%+ of the window. Pickle flags the gap and checks if they were DM-active (so you know if it's burnout or just async). Needs Slack + ClickUp cross-read — ships later.

Real catch
Chris: silent in #engineering for 11 of last 14 days. DM activity: yes. Not absent, just disengaged from team channels.
09 · DM-only completion
Pro
"Done" in DM. Card never updated.

Completion claimed in chat but the card still says "in progress." Two weeks later, the dashboard says you're behind. Pickle gives partial credit + a hygiene flag. Needs Slack/Teams chat data — ships later.

Real catch
David DMed: "shipped the auth refactor." Card XYZ-72 still in In Progress, no comment. Either close it or call it WIP.
10 · description quality
signal not effort
"8h development" is not a description

Time billed isn't the same as time accounted for. Pickle scores description quality. Does it actually describe what shipped, or does it just list how long it took?

Real catch
Last week: 6 time entries totalling 31h. 4 of them say "development" or "fixes". The other 2 say what changed and why.
11 · manager bottleneck
Pro
Tasks awaiting you

The hardest pattern to see in yourself. Pickle inverts the audit and shows you every task or comment your team is waiting on. Days of yours-blocking-theirs. Part of Manager Mode — ships later.

Real catch
3 tasks waiting on your review · 7 comments tagged @you with no reply · 1 "approval please" from 9 days ago.
12 · decisions in DM
Pro
Decision made in chat, never on the card

Group DMs are where decisions actually happen. Cards are where they're supposed to land. Pickle scans group DMs, matches mentions of task IDs, and links the decision back. Needs Slack/Teams DM access — ships later.

Real catch
"Let's go with Stripe Checkout, not custom" decided in #founders DM 6 days ago. Card XYZ-203 description still says "TBD."
13 · recurring zombie
graveyard
The same task stale, week after week

If Pickle flagged a task as stale this Monday, last Monday, and the Monday before, that's not a task. That's a graveyard entry. Time to kill or recommit.

Real catch
XYZ-12 has been a "recurring zombie" for 5 weeks running. First flagged Apr 14. It's not getting done. Close it or pull it forward.
// what already lives in your stack

Three native tools. None of them audit.

ClickUp Brain, Slack AI, and Microsoft Copilot each summarise what's already in their own app. None compare what your team said in chat against what the tasks actually show. That cross-tool audit is the entire point of Pickle. Click whichever applies to you:

Inside ClickUp

Pickle vs ClickUp Brain

CapabilityBrainPickle
Summarise a task✓✓
Generate task descriptions✓✗
Ranked inbox across all your tasks✗✓
Empty-description time entries✗✓
Zombie task detection✗✓
Standup-vs-evidence audit✗✓
Expired-promise tracking✗✓
Blocker age + escalation✗✓
Runs inside Claude / Cursor / Codex / Cline✗✓
Brain writes for you. Pickle audits what's there.
Inside Slack

Pickle vs Slack AI

CapabilitySlack AIPickle
Summarise a thread / channel✓✓
Daily channel recap✓✓
Unanswered DMs as actionable inbox✗✓
@mentions you never replied to✗✓
What YOU delegated, never heard back✗✓
Drafts follow-ups · waits for approval✗✓
Refuses 3rd nudge to the same person✗✓
Scores messages by your role✗✓
Runs in your assistant (not stuck in Slack)✗✓
Slack AI summarises. Pickle follows up.
Inside Teams

Pickle vs Microsoft Copilot

CapabilityCopilotPickle
Summarise a meeting✓✓
Draft replies in Teams✓✗
Reads Planner tasks assigned to you✓✓
Unanswered 1:1 + group chats as inbox✗✓
Approvals + adaptive cards as items✓✓
Delegated Planner tasks tracker✗✓
Action items from meeting chats✓✓
Cross-platform: chat ↔ task evidence✗✓
Runs in any MCP host (not just Teams)✗✓
Copilot writes inside a meeting. Pickle audits the day after.

The TL;DR. Native AIs are great inside their tool. Pickle is what reads across all three and tells you what no single one of them can see.

// pricing

Free, forever, for what's here today. More features keep landing.

The 9 ClickUp audit patterns you see on this page are free in Beta and stay free forever. As Pickle grows, I'll ship more patterns and smarter automation. If any of that ever becomes a paid layer, I'll design the price with the people using Pickle, not at them. No surprises, no bait-and-switch. For now: zero card, zero billing, just sign up and use it.

Live now · Beta cohort

100% free · 0 / 200 seats claimed

Cap at 200
Hire Pickle For Free (Beta seat)
Roadmap · what's coming next

More features ahead

The Free plan (9 ClickUp patterns) is permanent. Here's what I'm building on top of it. These features are not yet shipped — sign up and I'll email you the day each one lands.

If any of these ever become a paid layer, the price will be set with the people using Pickle — not at them. Beta users hear first when something ships, and get to shape what's worth paying for. Free will always exist.

// install in 60 seconds

Paste one block. Restart your assistant. Done.

Already have your Pickle key? Drop the config below into your assistant. Don't have a key yet? Grab it free — takes 10 seconds. Once installed, ask Pickle in chat to walk you through ClickUp / Slack / Teams setup.

📧
Email signup → install prompt → "Pickle Start".

The actual install command is in the welcome email (it includes your unique Pickle key, so it can't live on this public page). Sign up below, then check your inbox: you'll get a one-time prompt to paste into Claude Code / Cursor / Cline / Codex. Your AI installs Pickle into its own MCP config — alongside whatever you already have — without touching anything else. Restart, type "Pickle Start" in any chat, and the guided platform setup begins.

Get my install prompt — free
No card. No password. Email only, so I can send the install prompt + your unique Pickle key.
What the email sends you

A copy-paste prompt that any file-edit-capable AI (Claude Code, Cursor, Cline, Codex) understands. It looks roughly like this — with your real Pickle key filled in:

// paste this as your first message to Claude / Cursor / Cline / Codex
Install the Pickle MCP server in my AI assistant. Do NOT modify or remove any
existing MCP servers — Pickle goes alongside them.

1. Detect my config (Claude Desktop, Claude Code, Cursor, Cline, or Codex)
2. Read existing config, preserve all entries
3. Add Pickle to mcpServers:
   { "pickle": { "type": "http",
     "url": "https://pickle.adityaarsharma.com/mcp",
     "headers": { "x-pickle-key": "<YOUR_KEY>" } } }
4. Write back. Print "✓ MCP Installed. Please restart, then type 'Pickle Start'."
Safe-harbour mode: never touch other MCP servers.

After your AI confirms install + you restart, the first chat you open: type Pickle Start. Pickle walks you through ClickUp / Slack / Microsoft Teams setup — one platform at a time, 30 seconds each.

On Claude Desktop (no file-edit tools)? Manual install JSON

Claude Desktop's chat doesn't have file-edit tools, so the AI can't install for you. Paste this block manually into your config file instead (the email tells you the exact path):

{
  "mcpServers": {
    "pickle": {
      "type": "http",
      "url": "https://pickle.adityaarsharma.com/mcp",
      "headers": {
        "x-pickle-key": "<your-key-from-email>"
      }
    }
  }
}

Config file: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) · %APPDATA%/Claude/claude_desktop_config.json (Windows). Restart Claude, then type Pickle Start in a fresh chat.

// privacy & security · read this carefully

Your work data never sits on our server.

Pickle is the rare AI tool that is genuinely stateless. We don't have your task data because we never wrote it down. The audit happens inside one request and ends when the response is sent. Here's exactly what that means.

Pickle is a relay, not a vault

Your ClickUp / Slack / Teams tokens live in your own MCP config on your machine. When you run an audit, the token passes through Pickle's server in memory only — used once to relay the call to the platform's official API, then gone. We don't store it, don't log it, don't sell it, and don't retain access to it after your request returns.

Zero task & chat data stored

No chat history. No task bodies. No comments. No DM transcripts. Each request is independent. When the response leaves the server, all of it disappears from memory.

Open source · auditable

Every line of the server is open under MIT. Read it. Diff it. Self-host it if your security team requires.

"My team doesn't allow sharing work data with third parties."

Read that sentence again. Pickle doesn't share your work data with anyone. It uses your token to read your own data from ClickUp, Slack, and Microsoft's own servers. The audit happens inside one request. The result goes back to your assistant (Claude, Cursor, Codex, Cline), which is running locally on your laptop. None of your task or chat content ever lands on a Pickle disk.

If your security team allows Zapier, Make, n8n, or your own CI runner, Pickle is the same risk class. Same API-token model. Less data persistence.

Still not comfortable? Run it yourself. The full server is on GitHub under MIT. Drop it on a Mac mini, a VPC, a Raspberry Pi. Your tokens never leave your network. You maintain it. I won't touch it.

What we DO store
  • Your email (so we can send product updates)
  • Your free key (so the next request authenticates)
  • The number of times your key has been used (for the admin dashboard counter)
  • Your IP + user-agent on signup (for spam protection)
What we don't store, log, or retain access to
  • Any ClickUp task, comment, time entry, or description — not stored, not even briefly retained after your request
  • Any Slack message, DM, channel, or thread — ditto
  • Any Microsoft Teams chat, Planner task, or meeting content — ditto
  • Your ClickUp / Slack / Teams API tokens — never written to disk, never logged, never retained in any cache. They pass through the request like the postman handing you mail, gone the moment your request ends.
  • Any audit result or "catch" — computed in memory, returned to your assistant, then discarded.
// why this exists

I built this because I needed it.

Aditya Sharma A
Aditya Sharma
Founder · shipping Pickle from adityaarsharma.com

I've been running small teams for years. Every Monday I'd open ClickUp and find a task with 47 hours logged and "API improvements" as the description, repeated four times. Every Friday someone's "shipping today" from three days ago was still open. Every review I'd find a task that had been "in progress" since April.

Hiring another ops person was the obvious answer. $80k a year for someone to do the unglamorous part of management. That seemed dumb. So I built the tool I wished I had. Runs every morning. Reads all three workspaces. Tells me what's slipping.

Pickle is not a vibe-coded AI demo. I'm shipping it with the same care I put into every product on adityaarsharma.com. I dogfood it on my own team every morning. I keep my products alive. They don't disappear after a launch tweet.

Native AIs (ClickUp Brain, Slack AI, Copilot) are great inside their own tool. None of them read across the other two. Pickle is the only thing built specifically to audit work across all three workspaces and catch what falls between them. That's the category. That's the gap.

My honest deal with you: Use Pickle for 7 days. If it doesn't catch one thing you'd actually want to fix, delete the config block, hit reply on the welcome email, and tell me what was missing. Free during Beta, free if it doesn't work for you, free if you just want to read the source. There's no catch.

"

The first morning I ran it, Pickle caught a task with 47 hours logged and 'API improvements' as the description, repeated four times. We'd been paying for that for a month.

Me, the first time I dogfooded it
"

Used it for two weeks. Found two zombie tasks I'd completely forgotten about and a decision in a group DM that never reached the card. Now I check it before standup.

A founder friend in the private beta
// frequently asked

Real questions. Straight answers.

If you're going to add an MCP server to your workspace, you deserve to know exactly what it does and doesn't do.

Does Pickle actually work across ClickUp, Slack, AND Microsoft Teams?

Yes — with an honest split between what's shipped today and what's on the roadmap. Free in Beta (live today): 9 ClickUp patterns (empty hours, stale in-progress, zombie tasks, standup copy-paste, expired promises, blocker age, effort-output mismatch, description quality, recurring zombie), plus chat-guided setup for Slack and Microsoft Teams. Shipping later: the 4 cross-tool patterns that need Slack/Teams chat data (ghost mode, DM-only completion, decisions-in-DM, manager bottleneck). You connect each platform separately (one token each), and Pickle delivers a single morning brief through Claude / Cursor / Codex / Cline. Beta users hear first when each new pattern ships.

What's the Beta? What happens when it ends?

The first 200 sign-ups are the Beta cohort. Beta gets you: the 9 ClickUp audit patterns, the chat-guided setup for Slack & Microsoft Teams, unlimited audits, founder support direct from me. The Free plan stays free, forever, for everyone — Beta or not. As Pickle grows, I'll ship more patterns and smarter automation on top of Free, never instead of it. If any of that ever becomes a paid layer, Beta users hear about it first and get a say in what's worth paying for. For now: no pricing decided, no cards taken.

Won't my team resent being audited like this?

Pickle is a private brief, not a public scoreboard. The output goes to you, the manager or founder, inside your own assistant. It's not posted in a channel. It's not stack-ranked. It's not surfaced to anyone you didn't already pay to know this stuff. Think of it as the thing a good ops manager would tell you over coffee Monday morning, except automated. Most of what Pickle catches is just "hey, this card is rotting, somebody should poke it" — that's a healthier signal than nothing. The patterns are about work, not people: stale tasks, broken promises, empty descriptions. Not "Sarah is slow." Use it the way you'd use it if you were managing the team yourself, because you are.

Is my ClickUp / Slack / Teams token safe?

Yes. Each token travels inside the HTTPS request header. Pickle uses it to call the corresponding API on your behalf, then discards it. The server stores no tokens, no task data, no chat content, no message bodies, no logs. Every request is independent. When the response is sent, all of it is gone. The only persistent thing is your email + free key (if you submit one) for product updates.

Do I have to install anything? Run Node? Use the terminal?

No. The install itself happens via prompt: sign up by email, get a one-time install prompt with your Pickle key, paste it into Claude Code / Cursor / Cline / Codex as your first message. Your AI reads its own config, adds Pickle alongside any existing MCP servers (safe-harbour — never removes anything else), and confirms with "MCP Installed". You restart, type "Pickle Start" in a new chat, and the guided platform setup begins. No Node.js, no npm, no shell, no env files. Claude Desktop users (which lacks file-edit tools) get a small JSON block to paste manually instead — same destination, one extra step. The code is on GitHub if you want to audit it.

How do I add my ClickUp / Slack / Teams tokens?

Not in advance. After Pickle is installed (via the install prompt from the welcome email — your AI does it), the trigger word is "Pickle Start". Just type it in any chat. Pickle asks which platform you want first — ClickUp, Slack, or Microsoft Teams — and walks you through getting that platform's token in ~30 seconds, including exactly which header line to add to your MCP config. Edit the config, restart, you're connected. Repeat per platform. Nothing leaves your laptop except the request when an audit runs.

Which assistants does Pickle plug into?

Any assistant that speaks MCP. Claude Code, Claude Desktop, Cursor, Codex (OpenAI Agent SDK), Cline, Continue, Zed, Goose. Install configs for the four most-used are above the FAQ.

How is this different from ClickUp Brain, Slack AI, or Microsoft Copilot?

Native AIs are great inside their own tool. Brain summarises ClickUp; Slack AI summarises Slack; Copilot drafts replies in Teams. None of them audit, and none read across the other two. Pickle is built to find the 40-hour task with no description, the "shipping today" promise still open Thursday, the decision in #founders DM that never reached the Planner card. That cross-tool synthesis is what we do. (Full comparison tables are in the section above.)

Can I self-host instead of using the Cloud?

Yes. The full server is MIT open source. You'll maintain Node.js, TLS, uptime, and process management yourself. Every teammate who wants to use it has to install and configure their own MCP config. You'll also miss the patterns I ship weekly, since you'd be running a frozen copy. Not blocked, just a different job. Most folks pick the Cloud because it's the same code with none of the ops tax.

What does Pro cost when it launches?

Honest answer: I don't know yet, and I'm not going to make one up. The Free plan (9 ClickUp patterns) is permanent. As I ship more (Manager Mode, always-watching, cross-tool catches), I'll figure out which features are worth a paid layer by talking to the Beta cohort first. The two things I commit to now: (1) Free stays free, forever, for everyone. (2) Beta users hear first when something new ships, and get to shape what becomes paid. If the paid stuff never makes sense for your use case, stay on Free — that's a real option, not a downgrade.

What patterns does Pickle catch today?

9 free in Beta (all ClickUp): empty hours, stale in-progress, zombie tasks, standup copy-paste, expired promises, blocker age, effort-output mismatch, description quality, recurring zombie. 4 in Pro (need Slack/Teams chat or multi-person data): ghost mode, DM-only completion, manager bottleneck, decisions in DM. Each pattern is a concrete rule (not vibes-based). Full descriptions in the patterns section above. New patterns ship to all users on the Cloud automatically.

What happens if you (the founder) shut Pickle down?

Two things stay yours regardless. Your work data: Pickle never had it. It was always in your ClickUp / Slack / Teams. Your email + key: exportable from the admin endpoint, ping me and I'll send a CSV in 10 minutes. The remote server is MIT-open, so even if I disappear someone could spin it back up. That's part of why the source is public.

Who built this and why should I trust them?

One person: Aditya Sharma. I keep my products alive. They don't disappear after a launch tweet. Founder-built, founder-supported. If anything breaks, email me at [email protected]. I respond direct.