Mission#

Send Maxime a short, original joke on WhatsApp. One-shot. Don't be cringe.

Acceptance criteria#

• A new joke (not previously sent) lands on Maxime's WhatsApp.
• Delivery goes through one of the two supported paths in team/RELAY-PROTOCOL.md.
• Run log captures the full session trajectory (see "Logging requirements").

Target#

• Maxime's WhatsApp number: +6580860085
• Canonical session key for direct delivery: agent:main:whatsapp:direct:+6580860085

How to deliver — pick ONE path#

You are Debbie running in agent:debbie. You do NOT have a direct WhatsApp tool of your own. Use one of the protocol paths:

Path A — Relay through Robbie's WhatsApp session (preferred for ad-hoc)#

Use when: you want the message routed and reformatted by Robbie immediately.

sessions_send(
  sessionKey: "agent:main:whatsapp:direct:+6580860085",
  message: "[notify|debbie] Joke for you: \"<the joke>\"",
  timeoutSeconds: 60
)

The [notify|debbie] tag is mandatory — untagged inter-session messages are dropped per protocol.

Robbie reformats and emits to WhatsApp as part of his turn response. The reply field in the sessions_send result IS the WhatsApp-delivered text.

Path B — Direct push via cron isolated session (most reliable)#

Use when: you want true push delivery that doesn't depend on Robbie's session being free.

cron({
  action: "add",
  job: {
    name: "debbie-joke-<runId>",
    schedule: { kind: "at", at: "<now+5s ISO>" },
    payload: {
      kind: "agentTurn",
      message: "Send exactly this and nothing else: \"🦑 Debbie: <the joke>\""
    },
    sessionTarget: "isolated",
    delivery: {
      mode: "announce",
      channel: "whatsapp",
      to: "+6580860085",
      bestEffort: true
    },
    deleteAfterRun: true
  }
})

This bypasses the relay entirely and uses the channel plugin directly. No tag needed (no relay involved).

Verification (mandatory before status=done)#

For Path A:

• Confirm the sessions_send response contains a non-empty reply field starting with 🦑 Debbie: (Robbie's reformatted output).
• That reply IS what Maxime sees on WhatsApp.

For Path B:

• Confirm cron.add returned a job id.
• After firing time, call cron({action:"runs", jobId}) and confirm the latest run finished and the announce delivery succeeded.

Do NOT mark done on optimistic claims. If neither verification holds, mark failed.

Common failure modes#

• Untagged Path A message → Robbie drops it (NO_REPLY). Always include [notify|debbie].
• Path B with sessionTarget: main → cron rejects: channel delivery only works with sessionTarget: "isolated".
• Re-trigger on already-done task → mark new run skipped, reason "already done", do not send a duplicate joke.
• Embedded fallback (gateway unreachable) → mark failed immediately. Don't fake delivery.

Logging requirements#

Every run produces .runs/<runId>.log with:

1. Header (runId, taskId, agent, startedAt, command)
2. Full agent transcript (every message, tool call, tool result)
3. For Path A: full sessions_send request + response payloads
4. For Path B: full cron.add request + response, plus cron.runs confirmation
5. Final status line (status=, exitCode=, endedAt=, optional error=)

Run history (preserved for context)#

See runs: frontmatter above. Pre-2026-05-07 runs were embedded-fallback no-ops. Run 5 (r-t-004-1778117455634) was the first real delivery, via Path A under the new relay protocol.