hermes - 💡(How to fix) Fix Add generic Gmail semantic search workflow [1 comments, 1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
NousResearch/hermes-agent#16836Fetched 2026-04-29 06:38:39
View on GitHub
Comments
1
Participants
1
Timeline
2
Reactions
0
Author
Participants
Timeline (top)
closed ×1commented ×1
RAW_BUFFERClick to expand / collapse

Issue: Add generic Gmail semantic search workflow

Feature Description

Add a read-only gmail.semantic_search action to the Google Workspace tool. The action should provide a reusable workflow for broad personal email requests, with domain selection, ledger-first reads, bounded Gmail scans, and normalized semantic ledger output.

Motivation

Personal currently needs special handling for broad inbox requests such as trip extraction. That does not scale to real estate closing, financial documents, tax documents, subscriptions, purchases, or other personal domains. We need a shared retrieval and ledger foundation before adding more domain-specific extractors.

Proposed Solution

  • Add a domain registry to tools/google_workspace_tool.py.
  • Add gmail.semantic_search as a read-only Gmail action.
  • Support domain, query, refresh, full_scan, max_scan_pages, max_scan_messages, max_details, and max_age_hours.
  • Return fresh ledgers before calling Gmail.
  • Scan Gmail with existing gmail.scan and fetch details with gmail.get.
  • Persist sanitized ledgers under HERMES_HOME/memories/.
  • Add tests for ledger-first behavior, bounded scan behavior, and domain scoring.

Acceptance Criteria

  • gmail.semantic_search appears in the tool schema.
  • Fresh semantic ledgers bypass Gmail calls.
  • Refresh or missing ledger triggers a bounded Gmail scan/search.
  • The output includes records, scan stats, privacy metadata, and ledger path.
  • Tests pass without live Gmail credentials.

extent analysis

TL;DR

Implement the proposed solution by adding a gmail.semantic_search action to the Google Workspace tool, incorporating domain selection, ledger-first reads, and bounded Gmail scans.

Guidance

  • Review the tools/google_workspace_tool.py file to ensure it can accommodate the proposed domain registry and gmail.semantic_search action.
  • Implement tests for ledger-first behavior, bounded scan behavior, and domain scoring to validate the new functionality.
  • Verify that the gmail.semantic_search action correctly handles parameters such as domain, query, refresh, and max_scan_pages to ensure proper functionality.
  • Consider implementing error handling for cases where the ledger is missing or the Gmail scan/search fails.

Example

No code snippet is provided as the issue does not contain sufficient technical details to generate a specific example.

Notes

The proposed solution appears to be a significant addition to the Google Workspace tool, and its implementation may require careful consideration of performance, security, and data privacy implications.

Recommendation

Apply the proposed solution by implementing the gmail.semantic_search action and its supporting components, as it seems to address the motivation and feature description provided in the issue.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING