Your conversations. Your AI. Your model.

Build a reply agent from plain prompts, then run it on any chat platform with your own model: cloud key or local Ollama. Pandora is just a tool; it runs on your machine, with your keys, no data leaves.

01 · Your conversations

Every platform you already use - Slack, Gmail, LinkedIn, Discord, and more - without switching tabs or copy-pasting.

02 · Your AI

A reply agent you build from plain prompts and refine over time - not a preset, not someone else's script.

03 · Your model

Run fully local with Ollama, or plug in your own cloud key. Your choice, your cost, your data.

// FEATURES

Everything you need to build a reply agent. Nothing you don't.

// FEATURE 01

Your key or your machine

Use Ollama to run a model on your machine, or paste in an OpenAI or Anthropic key. Either way, the AI runs on your account - not ours.

ollama lm studio openai anthropic openrouter gemini mistral groq

// USE CASES

You write it once, then teach Pandora your style. After that, it drafts. You edit.

Slack · #eng-onboarding

Lucas 9:41 AM

hey just joined, sort of dropped in at the deep end 😅 where should i start?

You 9:43 AM

welcome! what team are you on?

Lucas 9:44 AM

infrastructure, reporting to Dan

You 9:45 AM

nice, good timing. what's your background, mostly backend?

Lucas 9:46 AM

yeah 4 years at a fintech, lots of k8s and terraform, some Go

You 9:47 AM

perfect, give me a sec

Lucas 9:52 AM

no rush — also do i need to request access to anything or does it auto-provision?

You 9:53 AM

some auto, some don't. github org access working?

Lucas 9:54 AM

can see the org, can't push to main repos

You pandora · generated reply

accept edit reject

Hey Lucas — since you've got the k8s/terraform background, skip the ramp framing and start with Platform Overview v3 (notion.so/plat-v3) and Terraform at $co (notion.so/tf-conv) — those two will make the first PRs click fast. The GitHub thing is the standard gate everyone hits — post in #access-requests tagging Dan, he clears it same day. Two other things: Thursday 2pm is our team sync (good place to meet everyone), and on-call shadowing doesn't kick in until week 2, so you've got time to ramp first.

Your prompt last 9 messages

When someone new on infra reaches out in this channel or DMs for orientation, draft my reply. What actually matters week one: - Platform Overview v3 — notion.so/plat-v3 — only arch doc that's current - Terraform at $co — notion.so/tf-conv — module layout + how we do reviews - Incident runbook — notion.so/inc-rb — referenced in week-2 standups Access gotchas everyone hits: - GitHub push to main repos needs the infra-team-member role — post in #access-requests tagging Dan, he approves same-day - VPN auto-provisions but takes ~2hrs after laptop setup - Prod AWS console is a separate ask to Sarah in IT Team rhythms worth flagging if relevant: - Thursday 2pm team sync (best place to meet everyone at once) - On-call shadowing starts week 2, not 1 Tailor to background: if they mention k8s/terraform experience, skip the beginner framing and point directly at infra docs. If early-career, give explicit reading order. Tone: direct, welcoming but not over-the-top. Short — busy week, no walls of text.

You wrote this prompt once. Pandora reuses it every time this thread needs a reply, reads the latest messages, and drafts in your voice.

Three steps: install, point at a model, write your first prompt.

Your model, your data, your voice.