Commands Reference

Daily Vibe provides several commands to analyze your coding sessions, manage configuration, and explore data sources.

Global Options

These options are available for all commands:

Option	Description
`--help`	Show help information
`--version`	Show version number
`--config <path>`	Use custom configuration file
`--verbose`	Enable verbose logging

Configuration Commands

`daily-vibe config set`

Configure LLM providers and other settings.

daily-vibe config set [OPTIONS]

Options

Option	Type	Description	Example
`-p, --provider`	string	LLM provider (openai\|anthropic\|generic)	`--provider openai`
`-k, --api-key`	string	API key for the provider	`--api-key sk-proj-...`
`-u, --base-url`	string	Base URL for OpenAI-compatible APIs	`--base-url https://api.example.com/v1`
`-m, --model`	string	Model name to use	`--model gpt-4-turbo`
`-s, --show`	boolean	Show current configuration	`--show`

Examples

# Basic OpenAI setup
daily-vibe config set --provider openai --api-key sk-proj-abc123...

# With custom model
daily-vibe config set --provider openai --api-key sk-proj-abc123... --model gpt-4-turbo

# Claude setup
daily-vibe config set --provider anthropic --api-key sk-ant-api03-abc123...

# With specific model
daily-vibe config set --provider anthropic --api-key sk-ant-api03-abc123... --model claude-3-sonnet-20240229

# DashScope (Alibaba Cloud)
daily-vibe config set \
  --provider generic \
  --base-url https://dashscope.aliyuncs.com/compatible-mode/v1 \
  --api-key sk-abc123... \
  --model qwen-plus

# Local API server
daily-vibe config set \
  --provider generic \
  --base-url http://localhost:11434/v1 \
  --api-key local-key \
  --model llama2

# Display current configuration
daily-vibe config set --show

Analysis Commands

`daily-vibe analyze today`

Analyze today's coding sessions and generate reports.

daily-vibe analyze today [OPTIONS]

Options

Option	Type	Description	Default
`-o, --out`	string	Output directory for reports	`./reports`
`-j, --json`	boolean	Output results as JSON	`false`
`-p, --provider`	string	Override LLM provider	Config value
`-m, --model`	string	Override model name	Config value
`--no-redact`	boolean	Disable content redaction	`false`

Examples

# Basic analysis of today's sessions
daily-vibe analyze today

# Save reports to specific directory
daily-vibe analyze today --out ./daily-reports

# Get JSON output for scripting
daily-vibe analyze today --json

# Use different model for this analysis
daily-vibe analyze today --model gpt-4-turbo --out ./reports

# Disable redaction for debugging
daily-vibe analyze today --no-redact --out ./debug-reports

Output Structure

When using --out, Daily Vibe creates three files:

daily.md - Human-readable daily report
knowledge.md - Extracted knowledge and patterns
data.json - Complete analysis data

`daily-vibe analyze range`

Analyze coding sessions within a specific date range.

daily-vibe analyze range [OPTIONS]

Options

Option	Type	Description	Default
`-f, --from`	string	Start date (YYYY-MM-DD)	Required
`-t, --to`	string	End date (YYYY-MM-DD)	Required
`-o, --out`	string	Output directory for reports	`./reports`
`-j, --json`	boolean	Output results as JSON	`false`
`-p, --provider`	string	Override LLM provider	Config value
`-m, --model`	string	Override model name	Config value
`--no-redact`	boolean	Disable content redaction	`false`

Examples

# Analyze specific date range
daily-vibe analyze range --from 2025-01-01 --to 2025-01-07 --out ./weekly-reports

# Analyze yesterday to today
daily-vibe analyze range --from yesterday --to today

# Use custom model for analysis
daily-vibe analyze range --from 2025-01-15 --to 2025-01-16 --model claude-3-sonnet-20240229

# Analyze last week with JSON output
daily-vibe analyze range --from "7 days ago" --to today --json --out ./reports

Date Format Support

Daily Vibe supports flexible date formats:

ISO dates: 2025-01-15, 2025-01-15T10:30:00
Relative dates: today, yesterday, tomorrow
Natural language: "3 days ago", "last Monday", "next Friday"
Shortcuts: 1d (1 day ago), 1w (1 week ago), 1m (1 month ago)

Data Source Commands

`daily-vibe sources scan`

Scan and display available data sources on your system.

daily-vibe sources scan

This command shows:

Claude Code project files
Codex CLI session and history files
SpecStory history files
VS Code extension data
File counts and date ranges

Example Output

Data Sources Found:

Claude Code Projects:
  ~/claude/projects/project1/*.jsonl (45 files, 2025-01-10 to 2025-01-16)
  ~/claude/projects/project2/*.jsonl (23 files, 2025-01-12 to 2025-01-16)

Codex CLI Sessions:
  ~/.codex/sessions/*.jsonl (12 files, 2025-01-15 to 2025-01-16)
  
Codex CLI History:
  ~/.codex/history/*.jsonl (156 files, 2024-12-01 to 2025-01-16)

SpecStory:
  ./project/.specstory/history/* (8 files, 2025-01-14 to 2025-01-16)

VS Code Extensions:
  Codex extension data found (last updated: 2025-01-16)

Total: 244 files across 5 data sources

Data Redaction Commands

`daily-vibe redact test`

Test redaction rules on text or files to see what would be redacted.

daily-vibe redact test [TEXT]
daily-vibe redact test --file <path>

Options

Option	Type	Description
`-f, --file`	string	Test redaction on a file

Examples

# Test with text
daily-vibe redact test "My API key is sk-proj-abc123xyz"

# Test with file
daily-vibe redact test --file ./sensitive-file.txt

# Test multiple lines
daily-vibe redact test "
API Key: sk-proj-abc123
Email: user@company.com
Server: 192.168.1.100
"

Example Output

Original:
My API key is sk-proj-abc123xyz and email is john@example.com

Redacted:
My API key is [REDACTED] and email is [REDACTED]

Patterns matched:
- sk-[a-zA-Z0-9]{20,} (API Key)
- \b[A-Za-z0-9._%+-]+@[A-Za-z0-9.-]+\.[A-Z|a-z]{2,}\b (Email)

Command Chaining and Automation

Combining Commands

You can combine commands for automated workflows:

# Scan sources and analyze today if data exists
daily-vibe sources scan && daily-vibe analyze today --out ./reports

# Configure and immediately test
daily-vibe config set --provider openai --api-key $OPENAI_KEY && \
daily-vibe analyze today --json

Scripting Examples

#!/bin/bash
# weekly-report.sh

WEEK_START=$(date -d "last Monday" +%Y-%m-%d)
WEEK_END=$(date -d "last Sunday" +%Y-%m-%d)
OUTPUT_DIR="./reports/week-$(date +%U)"

echo "Generating weekly report for $WEEK_START to $WEEK_END"

daily-vibe analyze range \
  --from "$WEEK_START" \
  --to "$WEEK_END" \
  --out "$OUTPUT_DIR"

echo "Report saved to $OUTPUT_DIR"

# weekly-report.ps1

$WeekStart = (Get-Date).AddDays(-7).ToString("yyyy-MM-dd")
$WeekEnd = (Get-Date).ToString("yyyy-MM-dd") 
$OutputDir = "./reports/week-$(Get-Date -Format 'yyyy-ww')"

Write-Host "Generating weekly report for $WeekStart to $WeekEnd"

daily-vibe analyze range `
  --from $WeekStart `
  --to $WeekEnd `
  --out $OutputDir

Write-Host "Report saved to $OutputDir"

// weekly-report.js
const { execSync } = require('child_process');
const path = require('path');

const now = new Date();
const weekStart = new Date(now.setDate(now.getDate() - 7)).toISOString().split('T')[0];
const weekEnd = new Date().toISOString().split('T')[0];
const outputDir = `./reports/week-${new Date().getWeek()}`;

console.log(`Generating weekly report for ${weekStart} to ${weekEnd}`);

try {
  execSync(`daily-vibe analyze range --from ${weekStart} --to ${weekEnd} --out ${outputDir}`, {
    stdio: 'inherit'
  });
  console.log(`Report saved to ${outputDir}`);
} catch (error) {
  console.error('Analysis failed:', error.message);
}

Exit Codes

Daily Vibe uses standard exit codes:

Code	Meaning
`0`	Success
`1`	General error
`2`	Configuration error
`3`	Data source error
`4`	Analysis error
`5`	Network/API error

Performance Tips

Large Datasets: For analyzing large date ranges, consider using --json output and processing results programmatically to avoid memory issues.

Use Date Filters: Narrow down date ranges to reduce processing time
JSON Output: Use --json for faster processing when human-readable output isn't needed
Parallel Processing: Daily Vibe automatically uses parallel processing for large datasets
Redaction: Disable redaction with --no-redact if not needed (faster processing)

Common Patterns

Daily Automation

# Add to cron for daily reports
0 8 * * * /usr/local/bin/daily-vibe analyze today --out ~/reports/$(date +%Y-%m-%d)

CI/CD Integration

# In your CI pipeline
daily-vibe analyze range --from $CI_START_DATE --to $CI_END_DATE --json > analysis.json

Development Workflow

# Morning routine
daily-vibe analyze today --out ./daily && code ./daily/daily.md

# Weekly review  
daily-vibe analyze range --from "7 days ago" --to today --out ./weekly-review

Troubleshooting Commands

If you encounter issues, try these debugging commands:

# Check configuration
daily-vibe config set --show

# Verify data sources
daily-vibe sources scan

# Test with verbose output
daily-vibe --verbose analyze today

# Test redaction
daily-vibe redact test "sample API key sk-test123"

Next Steps

Now that you know the commands, explore:

Examples - Real-world usage scenarios
Troubleshooting - Common issues and solutions
Development - Contributing to Daily Vibe

Commands Reference

On this page