{{ message }}
Repository navigation
docs: add web search and fetch backend to Hermes Agent integration - #3045
Open
JanHranicky wants to merge 2 commits into
Open
JanHranicky wants to merge 2 commits into
JanHranicky wants to merge 2 commits into
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
JanHranicky
marked this pull request as ready for review
October 6, 2026 08:19
apify-service-account
added
the
t-integrations
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
marcel-rbro
reviewed
Oct 21, 2026
marcel-rbro
left a comment
marcel-rbro
left a comment
Contributor
There was a problem hiding this comment.
Quick question before this merges: apify-hermes-agent-plugin#20 switches the web search backend from RAG Web Browser to the Web Search Actor, which caps results at 10 and adds APIFY_WEB_SEARCH_COUNTRY / APIFY_WEB_SEARCH_LANGUAGE. This PR documents v0.1.5, so the search details (line 81, the web.search_backend row, and the Resources link) will be out of date once that ships.
Which would you prefer?
- Merge this as is for v0.1.5, and follow up with a separate PR when the next release is out.
- Hold this PR until the next release and update it to cover Web Search, the 10-result cap, and the two new env vars. This assumes it's fine to name the Web Search Actor publicly by then.
Comment on lines
+121
to
+122
| | `web.search_backend` | Set to `apify` in `~/.hermes/config.yaml` to use the RAG Web Browser Actor for web search. | | ||
| | `web.extract_backend` | Set to `apify` in `~/.hermes/config.yaml` to use the Web Fetch Actor for web content extraction. | |
Contributor
There was a problem hiding this comment.
web.search_backend and web.extract_backend are documented twice: in the YAML block under "Use Apify for web search and fetch" and in this table. Could you keep them in one place? Either works:
- Keep the YAML in the web search section and drop these two rows.
- Keep these rows and replace the YAML with a short pointer to Configuration.
Contributor
Author
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documents the Apify web search and web fetch backend added in apify-hermes-agent-plugin v0.1.5, along with the related configuration settings and troubleshooting steps.