Roo Activity Logger

What is Roo Activity Logger?

Roo Activity Logger is an MCP (Model Context Protocol) server that automatically records AI coding assistant development activities such as command executions, code generation, and file operations. It supports Claude Code, Cline, Roo-Code, and other MCP-compatible AI assistants, saving all logs as JSON files for search, analysis, and context restoration.

How to use Roo Activity Logger?

Add the server configuration to your MCP settings file (e.g., for Cline, Roo-Code, or Claude Code) using npx with the package github:annenpolka/roo-logger. Then add prompts to your rule files (or CLAUDE.md) to instruct the AI to use the log_activity, search_logs, and get_log_files tools. The logsDir parameter must be an absolute path.

Key features of Roo Activity Logger

• Records six activity types: command_execution, code_generation, file_operation, error_encountered, decision_made, conversation.
• Each log includes a unique ID, timestamp, type, level, summary, details, intention, context, and parent/related IDs.
• Logs are saved as date-based JSON files in a user-specified directory.
• Searchable by type, level, date range, text, parent ID, sequence, and related IDs.
• Supports multiple AI coding assistants and is customizable via the save directory.

Use cases of Roo Activity Logger

• Track every command execution and code generation during development sessions.
• Restore full context when resuming a task by searching previous logs.
• Audit activity history for debugging or progress analysis.
• Group related activities using parent and related IDs to understand complex workflows.

FAQ from Roo Activity Logger

What AI assistants does Roo Activity Logger support?

It supports Claude Code, Cline, Roo-Code, and any other MCP-compatible AI coding assistant.

What data is logged in each activity entry?

Each entry includes a unique ID, timestamp, activity type, log level, summary, details (any JSON), intention, context, optional parent ID, sequence number, and related IDs.

How do I configure the log directory?

The logsDir parameter is required in every tool call and must be an absolute path. The directory will be created automatically if it does not exist.

Can I filter logs by date?

Yes, the search_logs tool accepts startDate and endDate parameters in YYYY-MM-DD format.

Where are the logs stored?

All logs are saved as JSON files in the local directory specified by the logsDir parameter. No remote storage is used.