Using Debuglet

Submit a local measurement

After Getting Started, choose a saved dispatcher and submit the bundled hello debuglet:

dbl connect http://127.0.0.1:9000 --name local
dbl run --sample hello --wait
dbl logs ID

When more than one executor is ready, select one with --executor ID. dbl status ID reads its state and dbl logs --follow ID follows stored output.

Connect to a managed dispatcher

Managed deployments authenticate clients. Register once, keep the account key and recovery code in their owner-only locations, and then submit:

dbl connect https://dispatcher.example --name research
dbl --dispatcher research login --register researcher
dbl --dispatcher research nodes
dbl --dispatcher research run --sample hello --wait --allow-remote-test

--allow-remote-test makes a deliberate acknowledgement that the TEST payment workflow is being used remotely.

The CLI guide covers saved connections, credentials, submission, cancellation, results, and JSON output: CLI reference. The HTTP API guide and OpenAPI document are the contracts for non-Go clients. Go applications should use the supported Go client library.

Write a debuglet

Debuglets are WASI command modules. Build a Go example with:

make wasm SAMPLE_DIR=examples/debuglets/go/hello-local
dbl run --wasm examples/debuglets/go/hello-local/debuglet.wasm --wait

Start from the debuglet examples and use the debuglet guide for the ABI and host functions.

For port, executor connection, OAuth, readiness or state-version failures, start with the troubleshooting guide for the package you installed.