OpenCode Monitor is a CLI tool for monitoring and analyzing OpenCode AI coding sessions.
Transform your OpenCode usage data into beautiful, actionable insights with comprehensive analytics, real-time monitoring, and professional reporting capabilities.
- π Comprehensive Reports - Daily, weekly, and monthly usage breakdowns
- π° Cost Tracking - Accurate cost calculations for multiple AI models
- π Model Analytics - Detailed breakdown of usage per AI model with
--breakdownflag - π Project Analytics - Track costs and token usage by coding project
- β±οΈ Performance Metrics - Session duration and processing time tracking
- π Flexible Week Boundaries - Customize weekly reports with 7 start day options (Monday-Sunday)
- π Output Speed Tracking - Average output tokens per second for each model in reports
- π Workflow Grouping - Automatically groups main sessions with their sub-agent sessions (explore, etc.)
- SQLite Database - Native support for OpenCode v1.2.0+ SQLite format (
~/.local/share/opencode/opencode.db) - Legacy File Support - Backwards compatible with pre-v1.2.0 JSON file storage
- Auto Detection - Automatically detects and uses the appropriate storage backend
- Hierarchical Sessions - Parent/sub-agent relationships from SQLite displayed as tree view
- π Rich Terminal UI - Professional design with clean styling and optimal space utilization
- π Progress Bars - Visual indicators for cost quotas, context usage, and session time
- π₯ Color Coding - Green/yellow/red status indicators based on usage thresholds
- π± Live Dashboard - Real-time monitoring with project names and session titles
- β° Session Time Tracking - 5-hour session progress bar with color-coded time alerts
- π§ Tool Usage Panel - Track tool success rates (bash, read, edit, etc.) in live dashboard
- π CSV Export - Spreadsheet-compatible exports with metadata
- π JSON Export - Machine-readable exports for custom integrations
- π Multiple Report Types - Sessions, daily, weekly, monthly, model, and project reports
Option 1: uv Installation (Fastest - One-liner)
uv is a fast Python package manager. It installs the tool in an isolated environment without cloning the repository.
# Install directly from GitHub
uv tool install git+https://github.com/Shlomob/ocmonitor-share.git
# With optional extras
uv tool install "git+https://github.com/Shlomob/ocmonitor-share.git#egg=ocmonitor[charts,export]"Why uv?
- No need to clone the repository
- Lightning-fast dependency resolution
- Creates isolated environments automatically
- Easy to upgrade:
uv tool upgrade ocmonitor
Option 2: pipx Installation (Cross Platform)
pipx is the recommended way to install Python CLI applications. It creates isolated environments and works on all platforms (including Arch Linux, Ubuntu, macOS, etc.).
git clone https://github.com/Shlomob/ocmonitor-share.git
cd ocmonitor-share
pipx install .Why pipx?
- Creates isolated environments (no dependency conflicts)
- Works on Arch Linux without breaking system packages
- No sudo required
- Easy to upgrade or uninstall
Optional extras:
# With visualization charts
pipx install ".[charts]"
# With export functionality
pipx install ".[export]"
# With all extras
pipx install ".[charts,export]"Option 3: Automated Installation (Linux/macOS)
git clone https://github.com/Shlomob/ocmonitor-share.git
cd ocmonitor-share
./install.shOption 4: Manual Installation
git clone https://github.com/Shlomob/ocmonitor-share.git
cd ocmonitor-share
python3 -m pip install -r requirements.txt
python3 -m pip install -e .# Quick configuration check
ocmonitor config show
# Analyze your sessions (auto-detects SQLite or files)
ocmonitor --theme light sessions
# Analyze by project
ocmonitor projects
# Real-time monitoring (dark theme)
ocmonitor --theme dark live
# Export your data
ocmonitor export sessions --format csv
# Force specific data source
ocmonitor sessions --source sqlite
ocmonitor sessions --source files- Quick Start Guide - Get up and running in 5 minutes
- Manual Test Guide - Comprehensive testing instructions
- Contributing Guidelines - How to contribute to the project
- Cost Management - Track your AI usage costs across different models and projects
- Usage Optimization - Identify patterns in your coding sessions with session time tracking
- Performance Monitoring - Monitor session efficiency and token usage with real-time dashboards
- Project Analytics - Understand which projects consume the most AI resources
- Team Analytics - Aggregate usage statistics across team members and projects
- Budget Planning - Forecast AI costs based on usage trends and project breakdowns
- Model Comparison - Compare performance and costs across different AI models
- Session Management - Track coding session durations and productivity patterns
- Resource Planning - Plan AI resource allocation and budgets by project
- Usage Reporting - Generate professional reports for stakeholders with export capabilities
- Cost Attribution - Track AI costs by project, team, and time period
- Quality Monitoring - Monitor session lengths and usage patterns for optimization
πΈ Screenshots: The following examples include both text output and clickable screenshots. To add your own screenshots, place PNG files in the
screenshots/directory with the corresponding filenames.
Click image to view full-size screenshot of sessions summary output
By default, sessions are grouped into workflows - a main session combined with its sub-agent sessions (like explore). This gives you a complete picture of your coding session including all agent activity.
# Sessions with workflow grouping (default)
ocmonitor sessions ~/.local/share/opencode/storage/message
# Sessions without grouping (flat list)
ocmonitor sessions ~/.local/share/opencode/storage/message --no-group
# List detected agents and their types
ocmonitor agentsWorkflow Features:
- Main sessions and sub-agent sessions are visually grouped with tree-style formatting
- Aggregated tokens and costs are shown for the entire workflow
- Sub-agent count displayed in the Agent column (e.g.,
+2means 2 sub-agents) - Use
--no-groupto see individual sessions without grouping
Time-based usage breakdown with optional per-model cost analysis.
# Daily breakdown
ocmonitor daily ~/.local/share/opencode/storage/message
# Weekly breakdown with per-model breakdown
ocmonitor weekly ~/.local/share/opencode/storage/message --breakdown
# Monthly breakdown
ocmonitor monthly ~/.local/share/opencode/storage/message
# Weekly with custom start day
ocmonitor weekly ~/.local/share/opencode/storage/message --start-day friday --breakdown--breakdown Flag: Shows token consumption and cost per model within each time period (daily/weekly/monthly), making it easy to see which models are consuming resources.
Supported days: monday, tuesday, wednesday, thursday, friday, saturday, sunday
Real-time monitoring dashboard that updates automatically.
# Start live monitoring (updates every 5 seconds)
ocmonitor live ~/.local/share/opencode/storage/message
# Custom refresh interval (in seconds)
ocmonitor live ~/.local/share/opencode/storage/message --refresh 10Features:
- π Auto-refreshing display with professional UI design
- π Real-time cost tracking with progress indicators
- β±οΈ Live session duration with 5-hour progress bar
- π Token usage updates and context window monitoring
- π Output Rate - Rolling 5-minute window showing output tokens per second
- π¦ Color-coded status indicators and time alerts
- π Project name display for better context
- π Human-readable session titles instead of cryptic IDs
- π Workflow Tracking - Automatically tracks entire workflow including sub-agents (explore, etc.)
- π§ Tool Usage Stats - Shows success rates for tools (bash, read, edit, etc.) with color-coded progress bars
Click image to view full-size screenshot of the live monitoring dashboard
Click image to view full-size screenshot of model usage analytics
Model Analytics Features:
- Per-model token usage and cost breakdown
- Cost percentage distribution across models
- Speed Column - Average output tokens per second for each model
- Session and interaction counts per model
Create your configuration file at: ~/.config/ocmonitor/config.toml
# Create the configuration directory
mkdir -p ~/.config/ocmonitor
# Create your configuration file
touch ~/.config/ocmonitor/config.tomlThe tool is highly configurable through the config.toml file:
[paths]
# OpenCode v1.2.0+ SQLite database (preferred)
database_file = "~/.local/share/opencode/opencode.db"
# Legacy file storage (fallback)
messages_dir = "~/.local/share/opencode/storage/message"
export_dir = "./exports"
[ui]
table_style = "rich"
progress_bars = true
colors = true
[export]
default_format = "csv"
include_metadata = true
[models]
# Path to local models pricing configuration
config_file = "models.json"
# Remote pricing fallback from models.dev (disabled by default)
remote_fallback = false
remote_url = "https://models.dev/api.json"
remote_timeout_seconds = 8
remote_cache_ttl_hours = 24Configuration File Search Order:
~/.config/ocmonitor/config.toml(recommended user location)config.toml(current directory)- Project directory fallback
OpenCode Monitor supports automatic pricing updates from models.dev, a community-maintained pricing database.
Features:
- Automatically fetches pricing for new models not in your local
models.json - Fill-only mode - never overwrites your local or user-defined prices
- Shared cache across all your projects (
~/.cache/ocmonitor/models_dev_api.json) - 24-hour TTL with stale cache fallback on errors
- Works offline using cached data
Enable Remote Fallback:
[models]
remote_fallback = trueUse --no-remote to disable for a single run:
# Force local-only pricing for this command
ocmonitor --no-remote sessionsPricing Precedence (highest to lowest):
- OpenCode's pre-computed cost (from session data, when available)
- User override file (
~/.config/ocmonitor/models.json) - Project/local
models.json - models.dev remote fallback (fill-only)
- Python 3.8+
- pip package manager
The project uses pyproject.toml for modern Python packaging. You can install in development mode using either pip or pipx:
git clone https://github.com/Shlomob/ocmonitor-share.git
cd ocmonitor-share
# Using pip (editable install)
python3 -m pip install -e ".[dev]"
# Or using pipx (editable install)
pipx install -e ".[dev]"Install all extras for development:
python3 -m pip install -e ".[dev,charts,export]"# Run all tests
pytest
# Run only unit tests
pytest -m unit
# Run only integration tests
pytest -m integration
# Legacy test scripts
python3 test_basic.py
python3 test_simple.pyocmonitor/
βββ ocmonitor/ # Core package
β βββ cli.py # Command-line interface
β βββ config.py # Configuration management
β βββ models/ # Pydantic data models
β β βββ session.py # Session and interaction models
β β βββ workflow.py # Workflow grouping models
β βββ services/ # Business logic services
β β βββ agent_registry.py # Agent type detection
β β βββ session_grouper.py # Workflow grouping logic
β β βββ live_monitor.py # Real-time monitoring
β β βββ report_generator.py # Report generation
β βββ ui/ # Rich UI components
β β βββ dashboard.py # Live dashboard UI
β βββ utils/ # Utility functions
β βββ data_loader.py # Unified data loading (SQLite/files)
β βββ file_utils.py # File processing
β βββ sqlite_utils.py # SQLite database access
βββ config.toml # User configuration
βββ models.json # AI model pricing data
βββ test_sessions/ # Sample test data
We welcome contributions! Please see our Contributing Guidelines for details on:
- π Reporting bugs
- π‘ Suggesting features
- π§ Setting up development environment
- π Code style and standards
- π Submitting pull requests
This project is licensed under the MIT License - see the LICENSE file for details.
- OpenCode - For creating an excellent AI coding agent that makes development more efficient
- ccusage - A similar monitoring tool for Claude Code that inspired features in this project
- Click - Excellent CLI framework
- Rich - Beautiful terminal formatting
- Pydantic - Data validation and settings
π§ͺ Beta Testing - This application is currently in beta testing phase. Please report any issues you encounter.
Built with β€οΈ for the OpenCode community


