Driving your AI assistant

The general pattern is the same everywhere: give the assistant the pages for your integration path, then describe what you want it to build. The details differ a little per tool.

Claude Code / claude.ai

Claude can fetch URLs directly — just include the URL in your message:

Read https://docs.sudomimus.com/en-us/connect/flow.md and
https://docs.sudomimus.com/en-us/application-rules/return-rules.md. Use the
Connect and Session API references for exact request and response shapes.
Implement Connect CALLBACK for my Next.js app. The application anchor is
your-application. Support passkeys and email OTP. Add routes for
/api/auth/establish, /api/auth/callback, and /api/auth/refresh.

Cursor / Continue / similar editor tools

Use your editor’s URL-attach feature (e.g. Cursor’s @web, Continue’s @docs) to attach the matching flow page, such as https://docs.sudomimus.com/en-us/connect/flow.md, then ask the same question. Attach the return-rule page and API reference when the task needs their exact contracts.

ChatGPT with web browsing

Fetch https://docs.sudomimus.com/en-us/connect/flow.md and
https://docs.sudomimus.com/en-us/application-rules/return-rules.md. Write a
Python Flask backend that uses Connect CALLBACK. Use application anchor your-app and
store pending sessions in PostgreSQL.

Let the assistant use the CLI

When the task involves your Sudomimus account or developer resources, the assistant should use the CLI instead of trying to drive the With portal through a browser. Give it a narrow instruction like:

Use the Sudomimus CLI for Sudomimus account operations. Prefer JSON output,
for example `sudomimus whoami --json`. If the CLI is not logged in, stop and
ask me to run `sudomimus login --no-open`; do not read or print the local
credentials file.

See Sudomimus CLI for AI agents for supported commands, endpoint overrides, and security boundaries.

Tips for better output

• Be specific about your stack. “Node.js + Express” produces different code than “Bun + Hono”. The docs cover the protocol; you tell the assistant the surrounding context.
• Name the authentication methods you need. Sudomimus supports passkeys, email OTP, Steam, AccessKey, and OIDC; the appropriate choice depends on the product requirements.
• Give it your application anchor, callback URL, and any env vars you have. These values are project configuration and are not part of the general documentation.
• Give it the matching machine-readable contract. For Connect, Session, Native, and Device, use the OpenAPI reference. For OIDC, provide the issuer so its library can read discovery, plus the OIDC integration guide for the supported profile.
• Fetch more pages when needed. Follow links from the flow guide for setup, token verification, and other details. Re-fetch the contract when it may have changed.