Connectors

Five surfaces.
Under watch.

Each surface is wired for oversight — every agent action monitored for accuracy, tone, and policy, exceptions escalated with full context. No glue code, no middleware you maintain.

Five channels converging into the chrome diamond core
Five channels · one loop
Productivity suite

Google Workspace

The connector that gives your agent a day job. It reads Gmail, Calendar, and Drive through granular OAuth scopes you control — the loop perceives your actual workday and acts inside it.

◂ inbound: new mail, invites, doc changesoutbound: drafts, scheduling, summaries ▸
  • Gmail triage — urgency scoring, draft replies, thread summarization
  • Calendar guard — conflict detection, focus-time defense, prep briefs
  • Drive awareness — changed docs surface in briefings automatically
  • Per-scope auth — grant mail, calendar, drive independently; revoke anytime
aoc connect google-workspace # guided OAuth flow
Universal inbox

Email

Not on Google? Any IMAP/SMTP mailbox comes under full watch. Every read, draft, and send is monitored and logged — governed by the oversight policies you set.

◂ inbound: polled mail, thread updatesoutbound: send, draft, forward ▸
  • Any provider — IMAP/SMTP with app-password or credential auth
  • Draft-first mode — agent drafts, you approve, loop sends
  • Thread memory — replies carry full conversation context
  • Flag-gated sending — autopilot.reply decides autonomy level
aoc connect email --imap mail.example.com --smtp mail.example.com
Carrier messaging

Telenyx SMS

Two-way texting over the Telenyx network. Inbound SMS is a first-class loop event — it wakes the agent instantly, day or night. Outbound texts carry escalations, confirmations, and alerts under your rules.

◂ inbound: SMS wakes the loop immediatelyoutbound: alerts, escalations, confirmations ▸
  • Instant wake — inbound texts skip the interval, loop fires now
  • Escalation rules — quiet hours, severity routing, on-call chains
  • Two-way threads — replies stay in conversational context
  • Delivery journal — every send logged with carrier status
aoc connect telenyx --api-key $TELENYX_KEY --from +15551234567
Command channel

Telegram

Think of it as a conversational command line for your agent. Ask for briefings, approve plans, flip feature flags, and inspect the loop journal — all from any Telegram chat, anywhere.

◂ inbound: commands, questions, approvalsoutbound: answers, briefings, confirmations ▸
  • Fastest setup — bot token in, talking to your agent in a minute
  • Plan approvals — agent proposes, you tap approve from chat
  • Flag control — toggle behavior without opening a dashboard
  • Loop inspection — journal, memory, and tick status on demand
aoc connect telegram # paste bot token when prompted
Team messaging

WhatsApp

Meet your team where they already talk. The WhatsApp connector keeps long-running threads in context for the oversight plane — a follow-up three days later still carries the full story for any human who picks up the escalation.

◂ inbound: messages, group mentionsoutbound: replies, digests, follow-ups ▸
  • Thread persistence — context survives across days and ticks
  • Group awareness — agent responds when mentioned, stays quiet otherwise
  • Digest mode — compress noisy groups into scheduled summaries
  • Business API — connects through your WhatsApp Business number
aoc connect whatsapp # guided Business API pairing
Early access

Wire your world into the loop.

All five connectors ship at launch. Join the waitlist and pick your first channel when your slot opens.

Join the waitlist →

Prefer docs first? Read the connector setup guides →