It's like offering a service that provides storage by api for agents. Yeah, you can call the api, or call the s3 api directly or store to disk.
That said, I would try it before rolling my own.
yeah in fact coding / PR-based workflows is one of the few areas where I don't really go super deep. GitHub PRs may have their shortcomings, but IMO it is the undisputed best review/approval queue system in existence by a mile.
i would never encourage someone to make an agent that asks human permission before submitting a PR. the PR is the HitL step
And what we build still only serves a small subset of use cases (e.g. to support attachments there's a whole other layer of MIMEtype management and routing to put things in S3 and permission them properly)
What are you smoking my man?
Write a python script that begins with the 2 following lines "import openai import email "
Simple is better than complex
MX and SPF is as trivial as with providers. Dkim might be harder. But emails will still go through.
You can also rent an smtp server and have a similarly simple infra where you log in to the server to read and send emails.
If this is too complex, I'd recommend starting with a private protocol like discord, which is designed for kids, or telegram as an intermediate step.