📋 Command Overview
The ClosedLoop AI CLI provides powerful commands for managing customer feedback analysis:| Command | Description | Example |
|---|---|---|
cl ingest | Submit feedback for AI analysis | cl ingest "Dashboard is confusing" |
cl insight | View AI-generated insights | cl insight |
cl team | Manage team settings | cl team website "https://example.com" |
cl config | Configure API key | cl config set --api-key <key> |
🔄 Ingest Commands
Submit Customer Feedback
Transform raw customer feedback into structured insights:List Ingested Feedback
View Specific Feedback
Ingest Parameters
Customer feedback content to analyze
Title for the feedback
Customer identifier
Name of person who provided feedback
Email of person who provided feedback
Source URL (support ticket, survey, etc.)
Wait for processing to complete
Output in JSON format
Page number for listing (default: 1)
Items per page (max 100, default: 20)
📊 Insight Commands
List AI-Generated Insights
View structured insights created by AI analysis:View Specific Insight
Feedback Parameters
Insight ID for detailed view
Page number for listing (default: 1)
Items per page (max 100, default: 20)
Output in JSON format
👥 Team Commands
Manage Team Website
Why set your product website? ClosedLoop AI uses your product URL to learn about your product features, competitors, pricing, and positioning. This enables more accurate feedback attribution and product-specific insights.Team Parameters
Team website URL (must include http:// or https://)
Output in JSON format
⚙️ Configuration Commands
Set API Key
View Configuration
Configuration Parameters
Your ClosedLoop AI API key
Output in JSON format
🔧 General Commands
Version Information
Help
📤 Output Formats
Table Format (Default)
JSON Format
❌ Error Handling
Common Error Messages
Error Codes
| Code | Description | Solution |
|---|---|---|
NO_API_KEY | No API key configured | Run cl config set --api-key <key> |
INVALID_API_KEY | API key is invalid | Get new key from http://app.closedloop.sh |
VALIDATION_ERROR | Input validation failed | Check input format and requirements |
API_ERROR | Server error | Check internet connection, try again later |
RATE_LIMITED | Too many requests | Wait and retry |
NOT_FOUND | Resource not found | Check ID is correct |
🎯 Best Practices
1. Use Descriptive Titles
2. Include Customer Context
3. Use JSON for Scripting
4. Handle Errors Gracefully
Ready for Examples?
See real-world usage examples and workflows