James Washington
writing about archive utils free game ideas replays
Technique

Omnifeed: one inbound log across channels with recipient-domain gate

Collects every customer/vendor message from all channels into one feed an agent can triage.

built Oct 2026 updated Oct 2026 Cloudflare and the edge

how it works

Polls a shared forwarding inbox and keeps a message only if the original To/Delivered-To matches an allowlisted org domain, dropping everything else before storage; org is a required field so adding orgs is config, not migration.

Technique: A pattern or hard-won lesson, written down so it isn't learned twice.

The code for this one lives in a private repo. This page explains the idea so you can build your own.

emailingestprivacy-by-filter

related

  • Omni-token + pinned account_id Technique Give AI agents one all-powerful cloud key, but make every project refuse to deploy anywhere except its own account.
  • Two-layer inbox classifier (rules first, LLM judge second) Automation Automatically labels every incoming email as belonging to one of several businesses or a personal area, so every downstream tool sees the same answer.
  • Template-only auto-replies as a prompt-injection defense Technique An auto-responder that never lets an AI read the incoming email can't be tricked by it.
  • Single-source org/sphere taxonomy read by every agent Document One file that defines which business or life area something belongs to, used by the email sorter, the task board and the agents alike.
  • Agent Scratchpad: a moderated GET-addressable commons for sandboxed LLM agents Note An idea for a public message board that locked-down AI agents could use to coordinate, built so the humans can always watch.
← everything I've built
© 2026 James Washington
github twitter rss