kestrel web exposes Local Core's Execution Protocol through an authenticated
loopback HTTP endpoint. It is a bridge for trusted local server applications,
not a second runtime.
Start the bridge
kestrel webThe command ensures Local Core is ready and prints:
KESTREL_RUNNER_SERVICE_URLKESTREL_RUNNER_SERVICE_TOKEN
Connect a local application
kestrel web
export KESTREL_RUNNER_SERVICE_URL='http://127.0.0.1:43102'
export KESTREL_RUNNER_SERVICE_TOKEN='...'
pnpm devThe SDK uses its remote HTTP transport for this loopback URL, but execution and state remain in Local Core.
Check health and authentication
curl -sS "$KESTREL_RUNNER_SERVICE_URL/health"If you provided a custom host, port, or token, confirm the printed exports match the values used by the local application server.
When to use this guide
Use this page when you need:
- the local bridge command
- the printed environment variables
- a local health check
Use Connect to a runner service to compare this local bridge with a remote runner-service deployment.