] [--all]` (alias `agnt5 ls`); `agnt5 logs [options]` **Status**: work-in-progress; both commands return a placeholder error today (`list functionality not yet implemented`) — use the Control Plane UI/API directly until the integration ships **Inspection alternatives**: query the Control Plane HTTP API or browse Studio **Work in Progress** Both commands are currently under development. They return placeholder errors today but will provide full deployment visibility once the Control Plane endpoints are stabilized. ### `agnt5 list`

Displays a list of deployments for the current project. The command accepts filters that will be wired to the Control Plane once the backing API stabilizes. ### Syntax ```bash agnt5 list [options] agnt5 ls [options] ``` ### Options | Flag | Description | | --- | --- | | `--environment` | Environment to inspect (default: `development`) | | `--limit` | Maximum number of deployments to show (default: `10`) | | `--status` | Filter by deployment status | | `--all` | Include deployments from every environment | **Current Status:** Returns a placeholder error today (`list functionality not yet implemented`). Use the Control Plane UI or APIs directly for detailed history until the CLI integration ships.

Basic listing Filtered results Environment-specific ```bash # List recent deployments agnt5 list ``` ``` Error: list functionality not yet implemented Use the Control Plane UI for deployment history. ``` ```bash # Short alias agnt5 ls ``` ```bash # Filter by status agnt5 list --status running --limit 20 ``` ``` Error: list functionality not yet implemented Expected output: ID | Status | Environment | Created | Image ------------|---------|-------------|------------|------- dep-abc123 | running | production | 2 min ago | v1.2.0 dep-def456 | running | staging | 1 hr ago | v1.1.8 ``` ```bash # List all deployments across environments agnt5 list --all ``` ```bash # Show production deployments agnt5 list --environment production ``` ``` Error: list functionality not yet implemented Expected output for production: ID | Status | Created | Image | Replicas ------------|---------|------------|--------|---------- dep-prod-01 | running | 2 min ago | v1.2.0 | 3/3 dep-prod-02 | stopped | 1 hr ago | v1.1.9 | 0/3 ```

### `agnt5 logs`

Streams logs for a specific deployment. When an ID is omitted the command will eventually default to the latest deployment for the current project. ### Syntax ```bash agnt5 logs [deployment-id] [options] ``` ### Options | Flag | Description | | --- | --- | | `--follow`, `-f` | Follow log output | | `--tail` | Number of lines to show from the end of the logs (default: `100`) | | `--since` | Timestamp or duration filter (e.g., `2h`, `30m`) | **Current Status:** Returns a placeholder error until log streaming is implemented. The CLI currently surfaces a message reminding you that a deployment ID is required.

Basic logs Live streaming Time filtering ```bash # Show logs for latest deployment agnt5 logs ``` ``` Error: deployment ID required Log streaming not yet implemented. Use the Control Plane UI for deployment logs. ``` ```bash # Show last 50 lines from recent logs agnt5 logs --tail 50 ``` ```bash # Stream logs for specific deployment agnt5 logs deploy-abc123 --follow ``` ``` Error: deployment ID required Expected behavior: 2024-01-15T10:30:45Z [INFO] Starting service... 2024-01-15T10:30:46Z [INFO] Handler registered: greet_user 2024-01-15T10:30:47Z [INFO] Service ready on port 8080 2024-01-15T10:30:48Z [INFO] Received request: greet_user ... (streaming continues) ``` ```bash # Follow logs with short flag agnt5 logs deploy-abc123 -f ``` ```bash # Show logs from last 2 hours agnt5 logs --since 2h ``` ``` Error: deployment ID required Expected filtered output: 2024-01-15T08:30:45Z [INFO] Service healthy 2024-01-15T08:35:12Z [INFO] Request processed 2024-01-15T09:15:33Z [WARN] High memory usage 2024-01-15T09:45:21Z [INFO] Memory usage normal ``` ```bash # Follow logs with time filter agnt5 logs deploy-abc123 -f --since 30m ```

## Planned Integration Once these commands are complete they will work hand-in-hand with `agnt5 deploy` to provide an end-to-end workflow: ### Example Future Workflow ```bash # 1. Deploy your project agnt5 deploy --prod # 2. List deployments to see the new one agnt5 list --environment production # 3. Monitor logs for the deployment agnt5 logs deploy-abc123 --follow # 4. Check deployment status agnt5 list --status running ``` ### Integration with Deployment Pipeline The visibility commands will integrate seamlessly with the deployment workflow: - **Post-deployment monitoring**: After `agnt5 deploy` completes, use `agnt5 logs` to monitor the new deployment - **Historical analysis**: Use `agnt5 list` to compare deployment performance over time - **Debugging**: Filter logs by time ranges to troubleshoot specific deployment issues - **Multi-environment visibility**: Compare deployments across development, staging, and production ### Expected Features When implementation is complete, expect: - **Rich filtering**: Filter deployments by status, environment, time range, and more - **Real-time updates**: Live log streaming with automatic reconnection - **Deployment details**: Full metadata about each deployment including build info, resource usage, and health status - **Integration hooks**: Commands will automatically detect the current project context and default to relevant deployments Until these commands are implemented, you can monitor deployments through the Control Plane UI or use the direct APIs for programmatic access.