Developer documentation
Build with Clone.
Choose your integration. Both paths use the same prediction API, context and company billing.
Clone SDK
Add suggestions to an existing composer with React or the headless controller.
Start with the SDK →HTTP API
Send your product’s context from any backend. Build your own interface and execution flow.
Make your first prediction →Install with your agent.
Give your coding agent the integration brief. It can inspect your code and ask about the experience you want.
Read the installation prompt
Integrate Clone into this product using https://clone.is/docs/sdk-quickstart and https://clone.is/docs/quickstart. Read the current documentation and pin the SDK release version. Discover our framework, composer, auth and backend before making changes. Ask me only about choices I have not already specified: suggestion triggers, instant or typewriter display, product context or optional Connect Clone, whether to offer Clone mode and its turn/time limits, and rollout controls. Keep app keys on the backend and derive user identity from the authenticated session. Preserve typing, IME and sending during prediction errors, delays and limits. Let me personally accept billing terms and enter the card. Do not enable automatic sending or production billing without my explicit choice. Verify deterministic UI/outage cases before any authorized billable prediction. Report what was tested and what still needs customer-app verification.
Take it to production.
Context and control
Choose what your product sends and what users explicitly share.
Reliability
Handle cancellation, old responses, outages and limits.
Pricing and billing
Understand billable suggestions, sandbox allowance and monthly invoices.
Optional Clone mode
Let users choose bounded automatic sends with explicit controls.