OAuth into your Salesforce org. Click Install All. Open Lightning App Builder and drag the components onto a record page. That's it. No connected app to configure. No metadata wrangling. No "this works on my machine."
Uses OAuth 2.0 with PKCE. We never see your password. The session cookie holds your token for 8 hours; nothing is persisted server-side.
4 production-grade Lightning Web Components, ready to drop on Account / Opportunity / Contact / Lead / Case record pages. Every inference call routes through the Bugs SF Proxy, which sits on top of the Salesforce Models API (Trust Layer ON — PII masking, audit trail, toxicity scoring).
Three-bullet AI summary of the current record. Reads every field via @wire(getRecord), sends to Claude Opus 4.7, renders in an SLDS card.
Generates a record-grounded outreach email. Editable subject + body in-place. One-click copy to clipboard.
Top 3 AI-ranked next steps with reasoning, grounded in the record's current state.
Suggests fills for empty fields based on the rest of the record. Confidence-scored. Never saves — suggestions only.
┌──────────────────────┐ ┌────────────────────────────┐ ┌─────────────────────────┐
│ YOUR Salesforce org │ ───► │ Bugs Demo Installer (Heroku)│ ───► │ Bugs SF Proxy (Heroku) │
│ (OAuth web flow) │ │ - OAuth2 PKCE │ │ - OpenAI-compat API │
│ any AE, any org │ │ - Builds MDAPI zip │ │ - Salesforce Models API │
│ │ ◄─── │ - POST /deployRequest │ │ - Trust Layer ON │
│ 4 LWCs + RSS + CSP │ └────────────────────────────┘ └─────────────────────────┘
└──────────────────────┘ ▲
│
┌─────────────┴────────────┐
│ Installed LWCs call this │
│ at runtime from your org │
└──────────────────────────┘
One connected app in Amin's org issues the OAuth code. Tokens belong to your user; metadata writes go to your org via the standard REST Metadata API. The connected-app pain Andy called out? Solved exactly once, here, for everyone.
git push heroku main. You just shipped a one-click installer for whatever you want to demo next.