Skip to content
AI Primer
workflow

Zeeg prototypes a Pi email assistant that filters inboxes through APIs

Zeeg is prototyping a Pi-based email assistant that filters an existing inbox through APIs and learns from curation. Hosting remains tentative while encryption requirements are unresolved.

2 min read
Zeeg prototypes a Pi email assistant that filters inboxes through APIs
Zeeg prototypes a Pi email assistant that filters inboxes through APIs

TL;DR

Pi's SDK embeds the agent in Node.js or Bun with a host-selected toolset. Its provider documentation includes ChatGPT Plus/Pro authentication and automatic OAuth-token refresh.

Inbox filtering

Zeeg described an earlier email-automation setup as struggling to follow instructions while processing and archiving unwanted mail. His brief is refreshingly narrow: clean up the email app he already uses, as he explained in a reply.

He summarized the event loop as onEmail() => learnAndDecide() in another reply.

Pi and subscription access

His initial request paired two requirements: his own hardware and a Codex subscription. Coding platforms looked too heavyweight for the job.

He rejected Flue's structured-workflow approach in favor of something more freeform, then settled on Pi.

One commenter recommended pi-durable, while zeeg said it added little for this use case, although Pi itself simplified parts of the implementation.

Decision tiers

Five outcome buckets appear in the initial Sift dashboard:

  • Rules
  • Sender memory
  • Decision model
  • Agent
  • Undecided

The pictured run exercised only the agent tier, leaving the model-free paths untested in this sample. Zeeg described the setup as “luna with chatgpt sub.”

Tailnet access and hosting

The prototype's access and distribution plans remain small-scale:

  • Interface: a management UI with mobile-web support and a tailnet requirement.
  • Repository: zeeg calls it open source and plans to share it once it reaches the point where he is using it himself.
  • Hosting: he wants encryption settled before hosting for others. In the same thread, he described designing around Cloudflare Durable Objects and criticized their complexity.

Gmail security assessment

Gmail's restricted-scope security review has already reached the project's TODO.md.

Google's restricted-scope rules require a third-party security assessment for covered apps accessing restricted data through servers, with exceptions including personal use and development. Its CASA guidance requires annual revalidation for covered applications.

Further reading

Discussion across the web

Where this story is being discussed, in original context.

On X· 5 threads
TL;DR2 posts
Inbox filtering3 posts
Pi and subscription access5 posts
Decision tiers2 posts
Tailnet access and hosting2 posts
Share on X