Add Tavily web search integration and Telegram typing indicator#3
Merged
initializ-mk merged 10 commits intodevelopfrom Feb 23, 2026
Merged
Add Tavily web search integration and Telegram typing indicator#3initializ-mk merged 10 commits intodevelopfrom
initializ-mk merged 10 commits intodevelopfrom
Conversation
- Add web_search provider abstraction with Tavily (default) and Perplexity backends - Auto-detect provider from env vars (TAVILY_API_KEY > PERPLEXITY_API_KEY), with explicit override via WEB_SEARCH_PROVIDER - Add tavily-search as external skill with embedded script and registry entry - Add `forge skills add` command for vendoring registry skills into projects - Update init wizard with provider selection phase when web_search is chosen - Send Telegram "typing" chat action while LLM processes requests
- Add CLAUDE.md with pre-commit gofmt and golangci-lint instructions - Wire validateTavilyKey into the init wizard tools step - Fix gofmt formatting in skills.go and tools_step.go - Rename ValidatePerplexityFunc to ValidateWebSearchKeyFunc for both providers
…alidation - Egress step now only shows the selected web_search provider domain (Tavily or Perplexity) instead of both - Skills step prompts for required_env, one_of_env, and optional_env when skills are selected, blocking if required/one_of is not provided - Web search tool step validates Tavily/Perplexity API keys with async validation (same pattern as provider step) - DeriveEgressFunc now receives envVars to filter provider-specific domains - Updated tests to match new provider-specific behavior
Tools line now displays "web_search [tavily]" or "web_search [perplexity]" to indicate which provider was selected.
The review step reads from WizardContext directly, not the tools step Summary(). Updated Prepare() to annotate web_search with the provider from ctx.EnvVars.
Init() was not resetting phase, currentPrompt, envPrompts, or envValues. When the user navigated back from a later step, the stale skillsEnvPhase with an exhausted currentPrompt caused an index out of range panic.
Skills step now checks env vars collected by earlier wizard steps (via Prepare/knownEnvVars) so it won't re-prompt for keys like OPENAI_API_KEY already provided as the model provider. buildEnvVars() uses a written map to skip duplicate keys when writing the .env file.
Provider step Apply() now stores the API key in ctx.EnvVars (e.g. OPENAI_API_KEY) so the skills step's Prepare() can detect it via knownEnvVars and skip the one_of group entirely.
MultiSelect and SingleSelect Init() methods were no-ops that didn't reset the done flag. After navigating back, done remained true causing Update() to short-circuit and treat all keys (including space) as no-ops while the step immediately re-completed.
Three issues fixed: - Wizard now handles esc globally as quit (matching kbd hints) - Removed redundant esc→back mapping from review step that caused the review↔egress loop - EgressDisplay.Init() now resets done flag so back-navigation doesn't immediately re-advance
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
1 participant
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.
Summary
web_searchtool into a provider pattern with pluggable backends (Tavily and Perplexity). Auto-detects from env vars (TAVILY_API_KEY>PERPLEXITY_API_KEY), with explicit override viaWEB_SEARCH_PROVIDER.tavily-searchto the skill registry with an embedded shell script (scripts/tavily-search.sh), skill markdown, andforge skills addCLI command for vendoring skills into projects.web_searchis selected, the wizard now presents a provider choice (Tavily recommended / Perplexity) before prompting for the API key.sendChatAction("typing")immediately when a message is received and repeats every 4s while the LLM processes, for both polling and webhook modes.New files
forge-core/tools/builtins/web_search_provider.gowebSearchOptsforge-core/tools/builtins/web_search_tavily.goforge-core/tools/builtins/web_search_perplexity.goweb_search.go)forge-core/registry/skills/tavily-search.mdforge-core/registry/scripts/tavily-search.shTest plan
go test ./forge-core/tools/builtins/— 16/16 pass (incl. Tavily provider, Perplexity provider, override, auto-detect, no-key)go test ./forge-core/registry/— 7/7 pass (incl. tavily-search index, script loading)go test ./forge-core/security/— 22/22 passgo test ./forge-plugins/channels/telegram/— 13/13 pass (incl. sendChatAction, typing indicator)go build ./forge-core/...andgo build ./forge-cli/...compile cleanly