- 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 4 obsolete tracking workflows:
- analytics-processor.yml (GitHub Issues-based tracking)
- tracking-dispatch.yml (repository dispatch events)
- process-tracking-logs.yml (GitHub Pages log processing)
- simple-tracking.yml (manual workflow dispatch)
- Remove obsolete JSON data file:
- docs/analytics/download-stats.json (workflow-generated data)
- Update WORKFLOWS_REFERENCE.md to reflect current architecture:
- Document only active workflows (deploy, publish-package)
- Replace workflow tracking docs with Supabase integration info
- Add migration history and troubleshooting for new system
The tracking system now uses direct Supabase database integration
from the CLI, eliminating all GitHub Actions dependencies for
analytics. This provides better performance, reliability, and
real-time tracking capabilities.
Remaining workflows handle only deployment and package publishing.
🤖 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>
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.