- Add E2B sandbox component with Python launcher script
- Support CLI parameters for E2B and Anthropic API keys (--e2b-api-key, --anthropic-api-key)
- Add comprehensive error handling for file downloads
- Make dotenv import optional in launcher script
- Add complete blog post with sandbox usage guide
- Update component generation system to support sandbox category
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Add new statusline/context-monitor component with real-time context usage monitoring
- Implement automatic Python script download for statusline components
- Update installIndividualSetting to support additional files installation
- Add context-monitor.py with visual progress bars, color-coded alerts, and session analytics
- Modify generate_components_json.py to exclude .py files from component listings
- Use relative paths (.claude/scripts/) instead of hardcoded paths
- Support executable file permissions for Python scripts
- Version bump to 1.20.2
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Introduced interactive documentation platform with live examples, tutorials, and user engagement features.
- Updated existing documentation commands to include structured metadata and enhanced descriptions.
- Added new commands for game development including analytics integration, asset pipeline setup, performance profiling, and testing frameworks.
- Enhanced Unity project setup command with platform-specific configurations and industry-standard practices.
- Updated husky command documentation for comprehensive CI checks and error handling.
- Introduced new workflow orchestrator command for managing complex automation workflows.
- Enhanced add-changelog command with current state checks and structured output.
- Improved commit command with repository state insights and structured usage.
- Updated performance audit command with current performance context and structured tasks.
- Enhanced create-feature command with project context checks and structured tasks.
- Improved security audit command with current environment checks and structured tasks.
- Updated setup-development-environment command with current environment checks.
- Enhanced svelte component creation command with project context checks and structured tasks.
- Improved sync-status command with current sync state checks and structured tasks.
- Updated sprint planning command with current sprint context checks and structured tasks.
- Enhanced generate-tests command with current testing setup checks and structured tasks.
- Improved code review command with current state checks and structured tasks.
- Add smart-contract-specialist for Solidity development with Hardhat/Foundry
- Add smart-contract-auditor for security audits and vulnerability detection
- Add web3-integration-specialist for frontend dApp development with React/wagmi
All agents follow established repository patterns with principle-based approaches rather than implementation-specific code examples.
- Updated descriptions for existing agents: terraform-specialist, api-documenter, docusaurus-expert, architect-reviewer, and unity-game-developer to clarify their roles and tools.
- Added new agents: changelog-generator, technical-writer, dependency-manager, documentation-expert, audio-mixer, audio-quality-controller, podcast-content-analyzer, podcast-metadata-specialist, podcast-transcriber, social-media-clip-creator, timestamp-precision-specialist, video-editor, 3D artist, game-designer, and unreal-engine-developer to expand capabilities in documentation, audio/video processing, game development, and dependency management.
- Included tools and models for new agents to ensure proper usage and integration.
- Introduced a new test engineer role with a detailed description and toolset.
- Developed a core testing framework including testing strategies, automation architecture, and technical implementation.
- Implemented a comprehensive test suite manager for unit, integration, and E2E testing.
- Created advanced test patterns and utilities for better test organization and data management.
- Added configuration templates for Playwright and Jest for E2E and unit/integration tests.
- Established a performance testing framework with load testing capabilities.
- Integrated test automation into CI/CD pipelines with GitHub Actions.
- Documented testing best practices for maintainable and reliable test implementations.
- Updated `database-optimization.md` to clarify focus areas and optimization strategies, removing redundant sections and enhancing clarity.
- Revised `database-optimizer.md` description for better specificity regarding SQL query optimization and schema design.
- Introduced new `nosql-specialist.md` file detailing NoSQL technologies, implementation strategies, and performance optimization techniques across various NoSQL databases including MongoDB, Redis, Cassandra, and DynamoDB.
- Updated hackathon-ai-strategist agent description and added tools for improved functionality.
- Revised llms-maintainer agent for proactive updates and enhanced tools.
- Introduced new model-evaluator agent for comprehensive AI model assessment and benchmarking.
- Enhanced prompt-engineer agent description for clarity on usage.
- Updated task-decomposition-expert agent to emphasize complex goal breakdown and tool selection.
- Expanded graphql-architect agent with detailed schema design and resolver optimization strategies.
- Created graphql-performance-optimizer agent for performance analysis and optimization of GraphQL APIs.
- Developed graphql-security-specialist agent focusing on security audits, authorization, and protection against vulnerabilities.
- Added security-auditor script to package.json for automated security audits.
- Add --verbose flag support for debugging agent execution
- Remove YAML front matter from system prompts to fix agent behavior
- Switch from --append-system-prompt to --system-prompt for better control
- Add detailed debug output showing command execution details
- Update help text to include verbose option
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
🚀 Released: Major new feature integrating Claude Code SDK
- Global agents accessible from anywhere with zero configuration
- Auto-detects project context and provides specialized AI assistance
- Complete CLI integration with create/list/update/remove commands
- Frontend integration with enhanced agent modals
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
🌍 Major new feature: Global AI Agents powered by Claude Code SDK
## New Features
- **Global Agent Creation**: `--create-agent <agent-name>`
- **Agent Management**: `--list-agents`, `--update-agent`, `--remove-agent`
- **Zero Configuration**: Agents install to /usr/local/bin (immediately available)
- **Auto Context Detection**: Smart project type detection and file context
- **Universal Access**: Works from any directory, in scripts, CI/CD, npm tasks
## Technical Implementation
- New global-agent-manager.js module with complete agent lifecycle
- Automatic PATH management across shell environments
- Executable script generation with Claude Code SDK integration
- Real-time loading indicators during AI processing
- Robust error handling and fallback mechanisms
## Frontend Integration
- Enhanced agent modals with Global Agent installation options
- New CSS styles for global agent sections
- Copy-to-clipboard functionality for all commands
- Usage examples and feature highlights
## User Experience
Before: Traditional project-based agent installation
After: `cct --create-agent security-auditor` → `security-auditor "prompt"` (anywhere)
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Remove obsolete tracking files (docs/track.html, docs/api/track.html)
- Simplify tracking-service.js by removing telemetry fallback system
- Update documentation to reflect Supabase-only architecture
- Remove references to GitHub Issues and unused workflow components
- Clean up legacy GitHub repo references in tracking service
- Update API examples to use correct endpoint and payload format
The system now uses only Supabase database for tracking, eliminating
the complex fallback system that was previously in place.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- 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>
- 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>
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>
- 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.
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>
Dani