Settings
Cloudflare D1
Active database for this Worker session (UUID from Dashboard → D1). Compare with Cloudflare to confirm you are on production (jaybot) or dev (jbot-dev). In local development, the nav Live DB / Dev DB toggle switches between these IDs when both bindings exist.
Loading…
Notifications
Subscribe to browser push alerts when your flows run (see Strategy management → flow designer). Works on desktop Chrome, Firefox, and Edge; Safari support varies by platform.
Local dev: If Subscribe shows "push service not available", permission and the service worker already succeeded — Chrome could not reach FCM (not JayBot). Try http://127.0.0.1:4321 instead of localhost (restart astro dev after pull — dev server listens on all interfaces), another network (no VPN), Firefox, OS notification settings for Chrome, or subscribe on your production https URL.
Could not load push status (sign in?).
OANDA (forex)
Demo mode uses your practice API token and account ID (fxpractice.oanda.com). Live mode uses your live token and account (api-fxtrade.oanda.com). Values in the footer come from OANDA's account summary after you save credentials here (or via worker env vars for dev). When a side shows as configured, Test connection works with empty fields (tests saved credentials or worker environment variables).
API debug log
Test/Save responses and errors (tokens are never logged). Also printed to the browser console as [jaybot settings] / [jaybot api].
No entries yet — use Test or Save.
Practice (demo / shadow)
Loading…
Live
Loading…
Production: set Worker secret BROKER_CREDENTIALS_KEY so tokens are stored encrypted (jb1:). Without it, tokens are stored as JSON in D1 (dev only). Static web deploys need PUBLIC_API_URL pointing at this Worker so browser calls reach /api/*.