feat: expands the Huntly browser extension with AI-powered content processing, plus adds a new X (Twitter) settings area in the web app. #107
Conversation
- Add AI content processing with streaming support for web clipper - Add X (Twitter) settings page for configuring auto-save behavior - Add separate extension release workflow for independent versioning - Remove extension build from main release workflow - Add new parser utilities and UI components for content extraction - Update extension manifest and dependencies for new features Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
🤖 Augment PR SummarySummary: This PR significantly expands the Huntly browser extension with AI-powered content processing, plus adds a new X (Twitter) settings area in the web app. Changes:
Technical Notes: AI prompts support 🤖 Was this summary useful? React with 👍 or 👎 |
![augmentcode[bot]](https://avatars.githubusercontent.com/in/1027498?s=60&v=4){kind=small}
|
|
||
| on: | ||
| push: | ||
| tags: [ 'ext/v[0-9]+.[0-9]+.[0-9]+*' ] |
There was a problem hiding this comment.
GitHub Actions tag filters are glob patterns (not regex), so ext/v[0-9]+.[0-9]+... will treat +/. literally and may not trigger on normal ext/v1.2.3 tags.
🤖 Was this useful? React with 👍 or 👎
.github/workflows/release.yml
Outdated
| on: | ||
| push: | ||
| tags: [ v\d+\.\d+\.\d+ ] | ||
| tags: [ 'v[0-9]+.[0-9]+.[0-9]+*' ] |
There was a problem hiding this comment.
Same concern here: tags: [ 'v[0-9]+.[0-9]+.[0-9]+*' ] is not a regex, and the literal +/. may prevent the workflow from running on expected version tags.
🤖 Was this useful? React with 👍 or 👎
| const openSettings = (tab?: string) => { | ||
| const optionsUrl = chrome.runtime.getURL('options.html'); | ||
| const url = tab ? `${optionsUrl}#${tab}` : optionsUrl; | ||
| chrome.tabs.create({ url }); |
There was a problem hiding this comment.
chrome.tabs.create is not available in content scripts, and AIToolbar is also used inside the Shadow DOM preview (content-script context), so this can throw when users click “Configure …”.
🤖 Was this useful? React with 👍 or 👎
| setTestResult(null); | ||
|
|
||
| if (providerType === 'ollama') { | ||
| refreshOllamaModels(); |
There was a problem hiding this comment.
loadConfig() calls refreshOllamaModels() immediately after setBaseUrl(...), but refreshOllamaModels reads baseUrl from state, so it can fetch from the wrong URL on first open when a custom Ollama URL is saved.
🤖 Was this useful? React with 👍 or 👎
| }; | ||
|
|
||
| const allSelectedCount = enabledModels.length + customModels.length; | ||
| const canSave = |
There was a problem hiding this comment.
For Azure providers, baseUrl is required (per testProviderConnection), but canSave doesn’t enforce it, so users can save an enabled Azure config that can never work at runtime.
🤖 Was this useful? React with 👍 or 👎
Move the autoSaveTweetMinLikes retrieval from the browser extension to the server's TweetController to reduce API calls and centralize logic. Add caching in GlobalSettingService for performance optimization. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
lcomplete
changed the title
- Updated web_clipper.tsx to utilize parserType from messages for improved flexibility in parsing documents. - Refactored preview handling to ensure proper cleanup and restoration of scroll states. - Introduced system-prompts.ts to manage multilingual system prompts for summarization, translation, key points extraction, action items, and explanations. - Added languages.ts to define a comprehensive list of supported languages with their respective codes and names.
…t extraction from HTML content
… and mark standalone AI processing as complete
1 participant
Summary
Test plan
🤖 Generated with Claude Code