Test mode Beta

Build and run CI against simulated devices

Beta. The Device SDK is live for design partners: Dopl issues your project's keys while the developer portal is being built, and @dopl/sdk is available on request. Agents that act for one signed in Dopl user can use the hosted MCP server instead.

Every project has a test environment. Requests made with an sk_test_ key only touch test data, and nothing made in test ever reaches a live device.

Simulated devices

With a test key, the Connect page offers a simulated device of every kind: glasses, phone, desktop, watch, home hub, home device, vehicle and robot. They exist only in test, and a live key never sees them. Each one publishes a realistic set of capabilities with limits modeled on a typical device of its kind; the simulated glasses match the Even Realities G2 lens. To pair one, choose it on the Connect page and press Continue under the code it shows.

A simulated device runs every call it supports and completes it at once with a result that includes simulated: true. Routing, grants, risk tiers and limits apply exactly as they do on real hardware, so a simulated watch truncates a long message the way a watch would.

Deterministic answers

CapabilitySimulated `result`
ask.choiceThe first option: { "simulated": true, "index": 0, "label": "Yes" }
ask.confirmConfirmed: { "simulated": true, "confirmed": true }
ask.text{ "simulated": true, "text": "simulated reply" }
Everything else{ "simulated": true }

Forcing failures

Use one of these IDs as the end user's external_user_id, exactly or followed by _ and any suffix such as sim_device_offline_ci42, and every simulated device of that user fails the same way. The same IDs work as a simulated device's ID, but Connect gives devices generated IDs, so the end user ID is the one you control.

IDEffect
sim_device_offlineThe user's devices read as offline: context lists none, and Deliver and device actions fail with device_offline (409, retryable)
sim_confirm_deniedEvery Deliver and device action fails with confirmation_denied (403, not retryable)
await dopl.connectSessions.create({
  external_user_id: "sim_device_offline_ci42",
  requested_scopes: ["present.*"],
  redirect_uri: "http://localhost:3000/connected",
});
// …pair a simulated device and exchange the token, then:
await dopl.notify("sim_device_offline_ci42", { text: "hi" }); // throws DoplError, code "device_offline"

Use a fresh suffix per CI run so each run starts with its own end user.