- Point tracking service to /api/track-download-supabase
- Ensure production tracking uses working endpoint
- All downloads will now be properly stored in Supabase database
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
Security improvements:
- Remove all debugging and test files (debug-db.js, test-db.js, init-db.js, etc.)
- Remove unused @vercel/postgres endpoint (track-download.js)
- Eliminate .env.production and .env.local files with exposed credentials
- Update documentation to reference correct API endpoint
- Ensure all sensitive data uses environment variables properly
Production ready:
- Only essential files remain for production deployment
- All endpoints use proper environment variable configuration
- Clean, secure codebase ready for main branch merge
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Add track-download-supabase.js using @supabase/supabase-js client
- Add init-db.js to check/initialize database tables
- Update dependencies to include Supabase client and latest @vercel/postgres
- Configure Supabase environment variables
- Provide SQL instructions for manual table creation if needed
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Remove accidentally created nested cli-tool/cli-tool directory
- Add simple tracking test script for local verification
- Confirmed tracking system works correctly with proper error handling
- Both database and telemetry endpoints are functional
- System gracefully handles local vs production differences
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Replace pool-based connection with @vercel/postgres sql template
- Use Vercel's auto-detection instead of explicit runtime config
- Convert all database queries to sql template literals
- Simplify table creation with proper error handling
- Maintain all functionality while ensuring Vercel compatibility
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Fix runtime configuration to use @vercel/node instead of nodejs18.x
- Convert API to ES modules for Vercel compatibility
- Add package.json for API function dependencies
- Ensure proper module handling for @vercel/postgres
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
Implements a comprehensive download tracking system inspired by npm analytics
to monitor component usage and improve popular components.
Key features:
• Anonymous download tracking for all component types (agents, commands, mcps, settings, hooks)
• Vercel + PostgreSQL backend with dual endpoint strategy
• Privacy-first design with complete opt-out support
• Fire-and-forget tracking that never blocks user experience
• Comprehensive test suite and documentation
Backend changes:
• Created API endpoint /api/track-download.js with PostgreSQL integration
• Implemented proper database schema with download_stats aggregation
• Added request validation, rate limiting, and security measures
• Configured Vercel deployment with database functions
CLI changes:
• Enhanced TrackingService to support database + telemetry endpoints
• Added automatic tracking for all installation types
• Implemented graceful fallback when database is unavailable
• Maintains existing privacy and opt-out mechanisms
Testing & Documentation:
• Added comprehensive test suite (test-download-tracking.js)
• Created detailed documentation (DOWNLOAD_TRACKING.md)
• Included deployment instructions and troubleshooting guide
• Added security and compliance information
The system respects user privacy by:
- Only collecting anonymous usage metrics
- Providing multiple opt-out mechanisms (CCT_NO_TRACKING, CCT_NO_ANALYTICS, CI=true)
- Never storing personally identifiable information
- Using fire-and-forget requests with timeout limits
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Added .vscode to .gitignore to prevent IDE settings from being tracked.
- Changed CodeGPT API key from "Ollama" to "OpenAI" in settings.json.
- Modified CSS styles for various components to enhance the terminal interface, including adjustments to padding, margins, and grid layouts.
- Introduced new terminal-style search functionality in index.html with improved search input handling and results display.
- Enhanced JavaScript event handling for category filters and search functionality, including debouncing and dynamic category display.
- Updated search results formatting to reflect terminal-style aesthetics.
- Upgraded jest-watch-typeahead from ^2.2.2 to ^3.0.1
- Resolves dependency compatibility issues causing npm install failures
- Version 3.0.1 provides improved Node.js compatibility and resolves known security vulnerabilities
- Updated package-lock.json to reflect the new dependency tree
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-authored-by: Claude <noreply@anthropic.com>
- Updated descriptions for RPG status bar and virtual code garden to include display details.
- Modified component documentation to reflect new features and descriptions for various statuslines.
- Removed max-height restrictions in CSS for better component visibility.
- Adjusted modal helper to show full component descriptions instead of truncated versions.
- Introduced settings for Amazon Bedrock, Google Vertex AI, and corporate proxy configurations.
- Added custom headers support for API requests.
- Implemented API key helper for dynamic authentication token generation.
- Restricted login methods to Claude.ai and Anthropic Console accounts.
- Configured bash command execution timeouts and performance optimizations.
- Enhanced privacy settings by disabling telemetry and non-essential traffic.
- Established AWS credential management for Bedrock integration.
- Allowed additional directory access and common git operations.
- Created comprehensive permissions for development and read-only modes.
- Developed various status line configurations for improved user experience.
- Move search button to first position in filter-buttons row
- Remove display:none from search button to make it visible
- Add category-filter-btn class to all category filter buttons
- Update toggleSearch() function to hide/show category filters:
- When search is active: hide all category-filter-btn and category-filter-label elements
- When search is inactive: restore normal display of category filters
- Improved UX: clean interface switching between search mode and filter mode
User experience:
1. Click 🔍 Search button (first in row)
2. Category filters disappear, search bar appears
3. Click 🔍 Search button again to return to normal filter view
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
New Features:
- 🎯 Single prompt for batch installations - ask locations once for all components
- ✅ Accurate success counting - shows actual vs attempted installations
- 📝 General terminology - 'configuration components' instead of 'settings and hooks'
Improvements:
- ⚠️ Clear error messages when installations fail due to permissions
- 🔄 Consistent location selection across all components in batch mode
- 📋 Better feedback showing selected locations before installation
- 🎨 Cleaner user experience with no repeated prompts
Bug Fixes:
- Fixed misleading success messages when some locations fail
- Fixed repetitive prompts during batch installations
- Fixed inconsistent default locations between silent and interactive modes
Available on npm: npm install -g claude-code-templates@latest
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Change 'settings and hooks' to 'configuration components'
- More flexible terminology that doesn't expose internal categorization
- Cleaner user experience with generic language
Before:
📍 Choose installation locations for settings and hooks:
? Where would you like to install settings and hooks?
📋 Will install settings and hooks in: user, local
After:
📍 Choose installation locations for configuration components:
? Where would you like to install the configuration components?
📋 Will install configuration components in: user, local
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Ask installation locations ONCE at the beginning for all settings and hooks
- Eliminate repeated prompts during batch installation
- Add sharedInstallLocations parameter to individual functions
- Use shared locations when provided, fall back to individual prompts otherwise
- Show clear message about selected locations before installation begins
Flow:
1. User runs: --setting=model/use-sonnet,telemetry/enable-telemetry
2. CLI asks ONCE: 'Where would you like to install settings and hooks?'
3. User selects locations (e.g., user, project, local)
4. CLI shows: 'Will install settings and hooks in: user, project, local'
5. All settings install to those same locations automatically
6. No additional prompts, CLI exits after completion
Prevents the frustrating loop where each component shows its own
installation menu, creating a better user experience for batch operations.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Add successfulInstallations counter to track actual successful installations
- Show accurate count in summary messages instead of total attempted
- Differentiate between complete success and partial success:
- 🎉 Green message when all locations successful
- ⚠️ Yellow message when some locations failed
- ❌ Red details showing number of failed installations
- Prevents misleading 'successfully installed in 4 location(s)!' when only 3 succeeded
Example outputs:
✅ All successful: '🎉 Setting installed in 3 location(s)!'
⚠️ Partial success: '⚠️ Setting installed in 3 of 4 location(s).'
'❌ 1 installation(s) failed due to permission or other errors.'
Fixes the case where enterprise settings fail due to permission denied
but user still sees success message for all locations.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Settings and hooks now support checkbox selection for multiple installation locations
- Users can install the same component in multiple environments simultaneously:
- 🏠 User Settings (~/.claude/settings.json) - Global
- 📁 Project Settings (.claude/settings.json) - Team shared
- ⚙️ Local Settings (.claude/settings.local.json) - Personal
- 🏢 Enterprise Settings - System-wide (requires admin)
- Interactive prompts show checkbox interface with validation
- Each location is processed independently with conflict detection
- Progress messages show installation status for each location
- Tracking includes installation_location for analytics
- Graceful error handling - failed locations don't stop others
- Summary message shows total installations completed
Example: Install allow-npm-commands in both user and project settings
for global availability plus team sharing.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Settings and hooks now show interactive prompts for installation location
- Fixed inconsistency between silent mode default and interactive mode default
- Both now default to 'local' settings (.claude/settings.local.json)
- Respects --yes flag to skip prompts when needed
- Users will now see the 4 installation options:
- 🏠 User Settings (~/.claude/settings.json) - Global
- 📁 Project Settings (.claude/settings.json) - Team shared
- ⚙️ Local Settings (.claude/settings.local.json) - Personal
- 🏢 Enterprise Settings - System-wide (requires admin)
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
## Search System ✨
- ✅ Real-time search across all components (agents, commands, settings, hooks, MCPs)
- ✅ Intelligent scoring algorithm with multi-field matching
- ✅ Search result cards with full flip functionality and compact design
- ✅ Proper integration with global event handlers
- ✅ Hover effects and copy button functionality matching normal cards
- ✅ Keyboard shortcuts (Escape, Enter) and responsive design
## Cart Manager Fixes 🛒
- ✅ Added support for settings and hooks categories (5 total categories)
- ✅ Updated cart initialization, UI, and command generation
- ✅ Fixed JavaScript errors when adding settings/hooks to cart
- ✅ Added proper cart sections and icons for all component types
## Technical Improvements 🔧
- ✅ Fixed showComponentDetails function calls with correct parameters
- ✅ Matching HTML structure with normal cards (command-display, command-code-container)
- ✅ Proper CSS styling with debug helpers for troubleshooting
- ✅ Compact card design optimized for available space
- ✅ Search button temporarily hidden per user request
## Additional Features 📋
- ✅ Added comprehensive ASCII roadmap for future development phases
- ✅ Enhanced component path handling and category conversions
- ✅ Improved error handling and component loading
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Added search button to filter buttons section with toggle functionality
- Implemented real-time search across all component categories (except templates)
- Search triggers after 3+ characters with 300ms debouncing for performance
- Searches through component names, descriptions, categories, tags, and keywords
- Added comprehensive search UI with input field, clear button, and results info
- Display search results grouped by category with match scoring
- Shows "No results" with helpful search suggestions when no matches found
- Integrated with existing cart functionality and component installation commands
- Added keyboard shortcuts (Escape to close, Enter to focus first result)
- Responsive design with mobile-optimized search interface
- Search data loaded from main components.json with fallback mechanisms
Features:
✅ Search across agents, commands, settings, hooks, and MCPs
✅ Real-time results with intelligent scoring algorithm
✅ Category-based result grouping and filtering
✅ Keyboard navigation support
✅ Mobile-responsive search interface
✅ Integration with existing cart and installation workflows
✅ Performance optimized with debouncing and caching
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Updated title and meta descriptions to emphasize Anthropic Claude Code connection
- Added structured data (JSON-LD) for better search engine understanding
- Enhanced keywords to include "Claude Opus 4.1", "terminal velocity", "deep coding"
- Added "Official Claude Code" button linking to anthropic.com/claude-code
- Repositioned messaging to align with Anthropic's official Claude Code value propositions
- Improved OG and Twitter card descriptions for better social sharing
- Added product/platform meta tags for better categorization
SEO targeting: "Claude Code", "Anthropic Claude", "AI development", "Claude Opus 4.1"
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
Dani