feat(slack): reply_broadcast so answer shows in main DM + quiet search log
phamdung2209+1: Claude Opus 4.7 (1M context)
cfeb8da
gateway.typing_indicator isn't a real Hermes option. The 'is thinking…'
status uses Slack assistant.threads.setStatus (thread-only by Slack
design) — it can't move to the channel root. Best achievable: set
platforms.slack.extra.reply_broadcast=true so the reply's first chunk
also posts to the main DM (Slack 'Also send to channel'), while typing +
tool progress stay in the thread. Also revert venus-search logs to info
now that the backend is confirmed active.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
chore(search): log register+tier at WARNING to confirm load in run logs
phamdung2209
8527f56
chore(search): log backend usage; revert to threaded progress
phamdung2209+1: Claude Opus 4.7 (1M context)
6511357
- venus-search now logs registration + which tier served each query, so
we can confirm in run logs that the backend (not native) handles search.
- reply_to_mode back to first + accumulate: off+separate still threaded
DMs (#9268) so progress can't leave the thread on Slack — keep the
proven threaded progress experience.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
fix(search): rename plugin dir to importable name + correct extract shape
phamdung2209+1: Claude Opus 4.7 (1M context)
40d857f
venus-search never registered: the hyphen dir name made
plugins.web.venus-search unimportable. Match the bundled provider layout
(verified against plugins/web/exa):
- dir venus-search → venus_search (valid module identifier)
- extract() returns list[dict] directly (not {success,data}) — bundled
exa/tavily providers return a bare list with per-URL error fields
- plugins.enabled uses manifest name web-venus-search (user backends
opt-in by manifest name; bundled ones auto-load)
- web.backend stays venus-search (the provider .name)
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
#1 Slack waiting effect: display.tool_progress=all + accumulate grouping
(live in-place tool bubble) + tool_progress_command.
#2 Context: default + secret bumped to 1,000,000 (was 131072); the
dropped-arg-under-pressure warnings were compaction churn.
#3 Static rework: /public/* serves /opt/data/public recursively
(sub-dirs preserved, traversal-safe) — old /static handler flattened
slashes so nested files 404'd. start.sh creates public/ + workspace
symlink; AGENTS.md tells the agent to publish into public/ and hand
out /public/... links instead of /static or /cache.
Plugin: manifest name + plugins.enabled now both 'venus-search' to match
the dir + provider name so it actually loads.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
feat(search): real tiered fallback plugin + 1M context
phamdung2209+1: Claude Opus 4.7 (1M context)
f38ab50
Add plugins/web/venus-search — a single Hermes web-search backend that
fans out internally with ordered fallback (the old exa-pool /
web-fallback-chain names were no-ops that never shipped):
search: Exa (multi-key pool) -> Tavily -> SearXNG -> DDGS
extract: Exa /contents (pool) -> Tavily /extract -> trafilatura
- Exa keys pool across EXA_API_KEY, EXA_API_KEY_2, ... rotating on
401/403/429 so multiple accounts share load.
- web.{backend,search_backend,extract_backend} = venus-search.
- start.sh seeds the plugin from repo into the volume (git = source of
truth); Dockerfile bakes ddgs + trafilatura so the keyless tiers
always work.
- Drop dead plugin names (exa-pool, web-fallback-chain, discord-proxy).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>