v1.4.451
cloudflare/agentsv1.4.451Apr 23, 2026by github-actions[bot]
AI Summary
Added three commerce intelligence patterns for analyzing video content and fixed logic for parsing vendor prefixes in model names.
Key Highlights
- Added `extract_affiliate_products` pattern to identify sponsored and organic opportunities.
- Added `extract_video_commerce_entities` to categorize commercial entities in video content.
- Added `analyze_monetization_opportunities` to map audience intent to revenue strategies.
- Fixed vendor prefix parsing to support `ollama/llama3` format without errors.
New Features
- extract_affiliate_products
- extract_video_commerce_entities
- analyze_monetization_opportunities
Full Release Notes
## Changes ### PR [#2079](https://github.com/danielmiessler/Fabric/pull/2079) by [teamsincetoday](https://github.com/teamsincetoday): Add 3 commerce intelligence patterns: affiliate extraction, video entities, monetization - Added `extract_affiliate_products` pattern to surface both sponsored and organic affiliate opportunities from any video transcript, going beyond the existing `extract_sponsors` pattern. - Added `extract_video_commerce_entities` pattern to identify all commercial entities in video content, categorized by type, timestamp position, and purchase likelihood. - Added `analyze_monetization_opportunities` pattern to map audience intent to revenue strategies, covering affiliate links, sponsorships, and digital products. - Registered all three new patterns in `pattern_descriptions.json` and `pattern_extracts.json` with appropriate metadata and tags. - Integrated all three patterns into `suggest_pattern` under the ANALYSIS, BUSINESS, and EXTRACT categories, and documented them in `pattern_explanations.md`. ### PR [#2086](https://github.com/danielmiessler/Fabric/pull/2086) by [majiayu000](https://github.com/majiayu000): fix: parse vendor prefix from model name for vendor/model convention - **Fix:** Added fallback logic to parse the vendor prefix from a model name when no vendor is explicitly specified. When a model string such as `ollama/llama3` is passed, the lookup no longer fails with a "could not find vendor" error; instead, the first path segment is split and checked against known vendors, correctly resolving the model to `llama3` under the `Ollama` vendor group.