Paperclip · Connectors · Setup v5
One decision per step. Everything else automatic.
Provider setup is now a persistent step-rail wizard. It shows the immutable agent, sends provider-owned approvals to the provider, hides credentials when an authenticated handoff can return them, and documents the exact effect behind every action.
Setup is not infrastructure configurationPaperclip chooses delivery and maximal safe capabilities. Users see only actions the provider requires them to perform.
45 product surfaces16 setup phasesEvery action explainedDesktop + mobile
Review convention: red dashed marks are annotations, not proposed UI. The step-rail layout is informed by the supplied reference image; none of its text or functionality is copied.
Navigation and product flow
Minimal default paths with honest advanced branches
Agent selection happens once. Provider setup contains one focused phase at a time; transport mechanics are selected by the deployment.
flow.svg1280×1040

${sections}Review
What changed in v5
- Generic purpose copy: “Use this connection as an agent tool” applies to every dual-purpose connector.
- Immutable agent: no setup screen offers Change agent; another agent means another connection.
- Stepped setup: Slack has two default phases plus a three-phase custom-app branch; GitHub has three default phases plus an existing-App branch; Teams has four phases; Telegram has three.
- Automatic delivery: webhook, relay, Socket Mode, and polling are not endpoint-wizard choices.
- Credential minimization: secrets appear only where a provider cannot return or provision them for Paperclip.
- Complete review: all prior provider endpoint tabs and conversation walkthroughs remain in the same grouped viewer.
- Paperclip base:
${baseSha}, matching origin/master when generated.