{"repo":"NousResearch/hermes-agent","public_id":"19197","display_label":"Web tools provider architecture and search/extract documentation","summary":"Two members propose a capability-based provider architecture for web tools, splitting search and extract (one version also includes browse). A third asks for documentation or clarification on using Tavily for search alongside self-hosted Firecrawl for extract, which loosely relates to the same split.","subsystem":"docs","counts":{"members":3,"open_issues":0,"open_issues_distinct":0,"open_prs":0,"closed_issues":3,"merged_prs":0,"attempt_prs":0},"landed_fix":null,"resolution":{"state":"unresolved","by":null},"freshness":{"state":"never_verified","last_verified_at":null,"is_stale":false},"grouping":{"backbone":"LLM_ONLY","link_density":0.24},"fix_edges":[],"members":[{"kind":"issue","number":19197,"title":"refactor: capability-based provider architecture for web tools (search/extract split)","url":null,"state":"closed"},{"kind":"issue","number":19198,"title":"refactor: capability-based provider architecture for web tools (search/extract/browse split)","url":null,"state":"closed"},{"kind":"issue","number":21003,"title":"[Feature]: Clarification / documentation request for Tavily search + self-hosted Firecrawl extract","url":null,"state":"closed"}],"trust":{"default_tier":"verified","includes_suggested":false}}