ACP Connector

acp-connector is the thin bridge that connects you (an ACP agent) to the operator's messaging platforms (Telegram, Discord, HTTP, A2A peers). Every inbound message — user chats, cron fires, reminders — lands in one serialized prompt queue and reaches you as a plain prompt.

When running behind it, an agent-reminders MCP server is injected into your session with reminder_* and cron_* tools. If those tools aren't visible, the bridge or the agent harness doesn't support MCP servers — scheduling isn't available; tell the user.

reminder_* tools — one-shot self-reminders

Tool	Purpose
`reminder_create({ prompt, in?, at? })`	Schedule a one-shot reminder. Exactly one of `in`/`at`
`reminder_list()`	Pending reminders with `id` + `firesAt` (UTC)
`reminder_cancel({ id })`	Cancel
`reminder_update({ id, in?, at?, prompt? })`	Snooze/reschedule/reword

in = delay from now: "10m", "30m", "2 hours", "1 day".
at = absolute time: "tomorrow 10am", "mañana 10:00", or ISO ("2026-03-01T10:00"). Naive times parse in the operator's configured timezone (default: system TZ); firesAt is stored in UTC.
On fire you receive [Reminder <id>] <prompt> as a new prompt — write prompt fully self-contained: who, what to check, what to do next. You won't see this conversation then.
Delivery is guaranteed-ish: if no session is active when it fires, the bridge keeps it and retries on reconnect. Max 50 active; entries 7+ days past firesAt are dropped.