A comprehensive development logging system that provides persistent memory for AI assistants working on large-scale coding projects. Built as a monorepo with MCP (Model Context Protocol) server capabilities, devlog solves the critical problem of AI memory loss during extended development sessions by maintaining structured, searchable logs of tasks, decisions, and progress.
AI assistants face significant memory limitations when working on large codebases:
- Context window constraints limit how much code can be processed at once
- Session boundaries cause loss of project understanding between conversations
- Catastrophic forgetting leads to inconsistent code modifications
- State management issues result in duplicated or conflicting work
Devlog provides the solution: persistent, structured memory that maintains context across sessions, enabling AI assistants to work effectively on large projects over extended periods.
π Learn More: Read our comprehensive analysis of AI Memory Challenges in Development to understand why persistent logging is essential for AI-assisted coding.
This monorepo contains three core packages that work together to provide persistent memory for development:
Core devlog management functionality including:
- TypeScript types: All shared types and interfaces for type safety and consistency
- Storage backends: SQLite, PostgreSQL, MySQL support
- CRUD operations: Create, read, update, delete devlog entries
- Search & filtering: Find entries by keywords, status, type, or priority
- Memory persistence: Maintain state across AI sessions
- Integration services: Sync with enterprise platforms (Jira, GitHub, Azure DevOps)
MCP (Model Context Protocol) server that exposes core functionality to AI assistants:
- 15+ specialized tools for devlog management
- Standardized MCP interface for broad AI client compatibility
- Real-time memory access during AI conversations
- Session persistence across multiple interactions
Next.js web interface for visual devlog management:
- Dashboard view of all development activities
- Timeline visualization of project progress
- Search and filtering UI for finding relevant context
- Manual entry management for human developers
- Cross-session continuity: Maintain context between AI conversations
- Long-term project memory: Remember decisions, patterns, and insights
- Context reconstruction: Quickly restore project understanding
- Memory search: Find relevant past work and decisions
- Work type tracking: Features, bugfixes, tasks, refactoring, documentation
- Status workflows: new β in-progress β blocked/review β testing β done
- Priority management: Low, medium, high, critical priority levels
- Progress tracking: Detailed notes with timestamps and categories
- Semantic search: Find entries by keywords across title, description, notes
- Multi-dimensional filtering: Status, type, priority, date ranges
- Related work discovery: Prevent duplicate efforts and build on existing work
- Active context summaries: Get current project state for AI assistants
- Platform sync: Jira, Azure DevOps, GitHub Issues integration
- Bidirectional updates: Changes sync between devlog and external systems
- Unified workflow: Manage work across multiple platforms from one interface
- Audit trails: Track all changes and integrations
- Deterministic IDs: Hash-based IDs prevent duplicates across sessions
- Atomic operations: Consistent data state even during interruptions
- Multiple storage backends: SQLite, PostgreSQL, MySQL support
- Backup & recovery: Built-in data protection mechanisms
- Node.js 18+
- pnpm 10.15.0+
# Clone the repository
git clone https://github.com/codervisor/devlog.git
cd devlog
# Install dependencies
pnpm install
# Build all packages
pnpm build
pnpm start
# or with auto-rebuild during development
pnpm dev:mcp
pnpm dev:web
# Access at http://localhost:3000
Add to your MCP client configuration:
{
"mcpServers": {
"devlog": {
"command": "node",
"args": ["/path/to/devlog/packages/mcp/build/index.js"]
}
}
}
Devlog supports multiple storage backends (SQLite, PostgreSQL, MySQL) and enterprise integrations (Jira, GitHub, Azure DevOps).
# Copy example configuration
cp .env.example .env
# Edit .env with your settings
π Configuration Guide: See docs/guides/INTEGRATIONS.md for complete setup instructions including database configuration and enterprise platform integration.
Devlog provides seamless integration with AI assistants through the Model Context Protocol (MCP):
- 15+ specialized tools for memory management
- Real-time context access during AI conversations
- Session persistence across multiple interactions
- Automatic duplicate prevention with smart ID generation
AI assistants can create entries, track progress, search past work, and maintain context across development sessions.
π Technical Details: See docs/guides/EXAMPLES.md for complete MCP tool documentation and usage examples.
- AI Memory Challenge - Why devlog exists and the problems it solves
- Usage Examples - Common workflows and usage patterns
- Quick Setup Guide - Getting started documentation
- Enterprise Integrations - Jira, Azure DevOps, GitHub setup
- GitHub Setup - Detailed GitHub integration guide
- Testing Guide - How to test the devlog system
- Contributing Guide - How to contribute to the project
- Development Guide - Development workflow and best practices
See the docs/ directory for comprehensive documentation including technical specifications and design documents.
The @codervisor/devlog-core
package can be used directly in your applications:
import { WorkspaceDevlogManager } from '@codervisor/devlog-core';
const devlog = new WorkspaceDevlogManager({
fallbackToEnvConfig: true,
createWorkspaceConfigIfMissing: true,
});
await devlog.initialize();
// Create and manage development logs programmatically
const entry = await devlog.createDevlog({
title: 'Implement user authentication',
type: 'feature',
description: 'Add JWT-based authentication system'
});
π API Documentation: See docs/guides/EXAMPLES.md for complete API documentation and usage examples.
Apache 2.0 License - see LICENSE file for details.
We welcome contributions! Please see our Contributing Guide for details on how to get started.
- Documentation: docs/ directory
- Issues: GitHub Issues
- Discussions: GitHub Discussions