create-external-bot-integration

Topics in the source

• Create an External Bot Integration
• 1. Establish the release contract before narrowing the implementation
• 2. Prove the uncertain provider boundary first
• 3. Reuse Runner while keeping placement and capability separate
• 4. Build onboarding as a watched, resumable workflow
• 5. Qualify both correctness and the ordinary user experience
• 6. Deliver one identifiable candidate and verify the deployed path
• References

Make an existing external agent a useful Paperclip participant: Paperclip can assign work to it, and it can initiate governed work from its own conversation. It uses its relevant native capabilities, returns inspectable results to Paperclip, and participates in normal admission, authority, and finalization. This workflow incorporates the September 30–October 9, 2026 Dot integration. Provider facts and code paths in the references are dated evidence, not a claim that every future bot supports the same APIs. Verify the current implementation and official provider documentation before choosing a transport or changing code. Read release-contract.md. Infer already-stated requirements and authorization from the conversation. Ask only about consequential unknowns; do not ask the user to repeat “two way,” Cloud, or use of Runner. Record the target environment, acting identity, capabilities, allowed human setup steps, delivery/stop expectations, and checkable finish line. Keep one compact matrix in the existing plan or task. Follow repository conventions if creating a plan file. “Works” must name its level: prototype, real provider, real Runner, managed sandbox, deployed tenant, or unattend

This is an excerpt. Refer to the complete source and its current requirements.