Build with your coding agent

Open your integration project in your coding agent and describe what your app needs. New projects include AGENTS.md, pointing to the installed authoring guide and SDK.

Existing projects

browserlayer guide

Ask the agent to run this command before authoring. It reads the guide bundled with your installed CLI, so the instructions match its APIs. The same guide is available at node_modules/@browserlayer/cli/skills/browserlayer-integration/SKILL.md.

Copy this task

Read browserlayer guide and the installed SDK README.md and TESTING.md first.

Website: <website URL>
Inspect this project's captures with browserlayer capture list --json.
If evidence is missing, open local Studio and guide me through a capture.
My app needs:
- A bookings sync: id, destination, date, status and amount.
- A cancel-booking endpoint taking a booking ID.

Build the integration using endpoints/, syncs/, connector/flows/
and connector/site/. Use authenticate and reauthenticate lifecycle files.
Keep website behavior in connector/ and app models/mapping in endpoints and syncs.
Handle MFA wherever it appears using resumable input.

Implement in small chunks. Run offline tests, then help me connect and
verify locally in Studio. Deploy to Development and verify there.
Finish by showing my backend how to create hosted Link, call the endpoint,
and consume signed webhooks and record changes.

Do not invent website behavior absent from the capture. Tell me which
operations require additional evidence or explicit mutation authorization.

Check the handoff

Stage	Evidence to ask for
Offline	Tests passing against faithful fixtures, including rejected input
Local	Connected account, endpoint result, sync records in SQLite
Development	Exact artifact version, cloud connection and completed runs
App	Hosted Link, verified completion, webhook receipt and persisted cursor

A successful compile is not a completed integration. An agent should report what it actually exercised and what remains unverified.