CI / lint-and-test (push) Has been cancelled

Details

Consolidate pipeline code from teleo-codex + VPS into single repo

Sources merged:
- teleo-codex/ops/pipeline-v2/ (11 newer lib files, 5 new lib modules)
- teleo-codex/ops/ (agent-state, diagnostics expansion, systemd units, ops scripts)
- VPS /opt/teleo-eval/telegram/ (10 new bot files, agent configs)
- VPS /opt/teleo-eval/pipeline/ops/ (vector-gc, backfill-descriptions)
- VPS /opt/teleo-eval/sync-mirror.sh (Bug 2 + Step 2.5 fixes)

Non-trivial merges:
- connect.py: kept codex threshold (0.65) + added infra domain parameter
- watchdog.py: kept infra version (stale_pr integration, superset of codex)
- deploy.sh: codex rsync version (interim, until VPS git clone migration)
- diagnostics/app.py: codex decomposed dashboard (14 new route modules)

81 files changed, +17105/-200 lines

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

2026-04-07 16:52:26 +01:00

1.5 KiB

Raw Blame History

Gmail Setup for Hermes Agent

Step 1: Create Google Cloud OAuth Credentials (~5 min)

Go to console.cloud.google.com
Create a new project (or use existing): "Hermes Assistant"
Enable these APIs:
- Gmail API
- Google Calendar API
- Google Drive API (optional)
Go to APIs & Services → Credentials → Create Credentials → OAuth 2.0 Client ID
Application type: Desktop app
Name: "Hermes Agent"
Download the JSON file → save as ~/.hermes/google-credentials.json

Step 2: Configure Hermes

Add to ~/.hermes/.env:

GOOGLE_CLIENT_ID=your-client-id.apps.googleusercontent.com
GOOGLE_CLIENT_SECRET=your-client-secret

Or place the downloaded JSON at ~/.hermes/google-credentials.json.

Step 3: Authorize

hermes setup google-workspace

This opens a browser auth flow (or gives you a URL to paste). Sign in with m3taversal@gmail.com and grant permissions. Token is saved locally.

Since this is a VPS (no browser), you'll get a URL — open it on your laptop, authorize, paste the code back into the terminal.

Step 4: Test

hermes "Show me my last 5 emails"
hermes "What's on my calendar today?"
hermes "Draft a reply to the last email from [name]"

Security Notes

OAuth tokens stored locally in ~/.hermes/ (chmod 600)
Hermes only accesses what you authorized — revoke anytime at myaccount.google.com/permissions
The VPS is SSH-only access, no public web ports exposed to Hermes

1.5 KiB Raw Blame History