Skip to content

feat(forge): Gmail send/read capabilities for hey@hiago.sh - #34

Merged
uphiago merged 1 commit into
mainfrom
feat/gmail-capability
Aug 5, 2026
Merged

feat(forge): Gmail send/read capabilities for hey@hiago.sh#34
uphiago merged 1 commit into
mainfrom
feat/gmail-capability

Conversation

@uphiago

@uphiago uphiago commented Aug 5, 2026

Copy link
Copy Markdown
Owner

Adds Gmail email send and read capabilities to Barbarossa via the Forge runtime lane.

  • worker-rpc.py: new mail.send (smtplib, SMTP 587 STARTTLS) and mail.read (imaplib, IMAP 993 SSL) handlers
  • router: gmail_send and gmail_read MCP tools routing mail.* to Forge
  • models: JobRequest fields to/subject/body/mailbox/limit/query with validation; capabilities added to policy
  • secrets: gmail_user and gmail_app_password staged on the host (never in git), mounted to Forge
  • skill: barbarossa-gmail for Hermes
  • deploy script: ensures Gmail secrets exist
  • Tests updated (router 50 pass, worker/infra 34 pass)

Validated on OVH: real send + IMAP read with the App Password both succeed.

- New mail.send / mail.read capabilities in worker-rpc.py using smtplib (SMTP 587) and imaplib (IMAP 993)
- Router tools gmail_send and gmail_read routing mail.* to the Forge runtime lane
- JobRequest fields to, subject, body, mailbox, limit, query with validation
- Docker secrets gmail_user and gmail_app_password staged on the host (never in git)
- Hermes skill barbarossa-gmail documenting read/send usage
- deploy-runtime-files.sh ensures Gmail secrets exist on deploy
- Router + infra regression tests updated and passing
@uphiago
uphiago force-pushed the feat/gmail-capability branch from f54a28f to f1ca380 Compare August 5, 2026 02:12
@uphiago
uphiago merged commit d526db8 into main Aug 5, 2026
4 checks passed
@uphiago
uphiago deleted the feat/gmail-capability branch August 5, 2026 02:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant