Using Notification Send

TL;DR

Notify the user who owns this Wayfinder Shells instance. Email renders Markdown into themed HTML; SMS/text sends concise plain text.

MCP tool (preferred from agents):

notification_send(
  title="Rebalance complete",
  message="Moved **50 USDC** from Aave → Morpho.\n\n- tx: 0x…\n- new APY: 7.4%",
)

Python client (from scripts):

from wayfinder_paths.core.clients.NotifyClient import NOTIFY_CLIENT

await NOTIFY_CLIENT.notify(
    title="Rebalance complete",
    message="Moved **50 USDC** from Aave → Morpho.\n\n- tx: 0x…\n- new APY: 7.4%",
    delivery="email",  # or "sms" / "text"
)

Both POST to {api_base}/opencode/notify/ with the configured WAYFINDER_API_KEY.

Limits & gotchas

• Title: ≤ 200 chars (required, non-empty after strip).
• Message: ≤ 20 000 chars (required). Rendered as Markdown — headings, lists, tables, fenced code, links all work.
• Delivery gate: Email requires email_verified: true; SMS/text requires a verified phone number.
• Throttle: Backend caps at 12 notifications / user / day across email/SMS. Budget sends; don't spam progress updates.
• Shells-only: No-op (or HTTP error) outside a Wayfinder Shells instance. The MCP tool gates on is_opencode_instance() indirectly via the API; the client just hits the URL. Detection: OPENCODE_INSTANCE_ID env var is set, or the health probe at http://localhost:3096/global/health returns healthy: true.
• Client returns the parsed JSON dict directly (no (ok, data) tuple — it's a WayfinderClient, not an adapter).
• Scheduled jobs: Routine successful runs already sync to backend job history. Only opt into all success chat job_result messages with always_notify_session_on_job_completion=True when the user explicitly wants live run output. For conditional chat callbacks, print one line from the script: WAYFINDER_JOB_RESULT {"summary":"Funding crossover detected","instructions":"Research whether to unroll the position.","severity":"warning"}.

When to use

• Report completed fund-moving work to the owner ("rebalance done", "withdraw confirmed").
• Surface decisions that need them ("APY dropped below threshold — pause strategy?").
• Flag failures you can't auto-resolve.
• Escalate job_result events from scheduled jobs only when they need owner attention.

Don't use for chatty progress updates. Alert scripts should be edge-triggered: persist the previous state, notify once when a threshold first crosses or an action is taken, then suppress repeats until a reset condition or cooldown. If the right response is more research or a proposed script rather than an external notification, emit WAYFINDER_JOB_RESULT instead of calling Notify.

Markdown formatting tips

• Use **bold** for amounts and statuses.
• Code-fence tx hashes / addresses so they don't wrap mid-string.
• Tables work for multi-step rebalance summaries.
• Links: [Block explorer](https://...) → clickable in the rendered email.

Error shape

MCP tool returns {"ok": false, "error": {"code": ..., "message": ...}} for:

• invalid_request — title/message empty or exceeds limit.
• notify_http_error — backend rejected (check details for body).
• notify_error — transport failure.