Intent-Engine
δΈζ | English
Intent-Engine is a minimalist, project-specific strategic intent tracking system designed for human-AI collaboration.
It's not just another todo listβit's a bridge connecting human strategic thinking with AI execution capabilities, helping answer two critical questions: "Where are we going?" and "Why are we going there?"
π― What is it?
Intent-Engine is a CLI tool + database system for recording, tracking, and reviewing strategic intents. It provides a shared, traceable "intent layer" for human-AI collaboration.
Core Features:
- π Strategic Task Management: Focus on What and Why, not just How
- π§ AI's External Long-term Memory: Persist decision history and context across sessions
- π³ Hierarchical Problem Decomposition: Support unlimited levels of parent-child task relationships
- π Structured Decision Tracking: Every key decision is recorded as an event stream
- π JSON-native Interface: Perfect for AI tool integration
π₯ Who is it for?
Primary Users
- Human Developers: Set strategic goals and record project intentions
- AI Agents: Understand objectives, execute tasks, and document decision processes
- Human-AI Collaboration Teams: Maintain context synchronization in long-term projects
Use Cases
- β Complex projects requiring AI to work continuously across multiple sessions
- β Technical projects needing to trace "why this decision was made"
- β System engineering requiring decomposition of large tasks into subtask trees
- β Automated processes where AI autonomously manages work priorities
π‘ What problems does it solve?
Value for Humans
Problems with Traditional Task Management Tools (Jira/Linear):
- β Focus on tactical execution (Sprints, Story Points), lacking strategic layer
- β Require extensive manual maintenance (status updates, comments)
- β Not suitable for AI integration (primarily Web UI)
Intent-Engine's Solution:
- β Strategic intent layer: Each task includes complete specifications (spec) and decision history (events)
- β Automation-friendly: AI can autonomously create, update, and switch tasks
- β CLI + JSON: Perfect AI toolchain integration
Value for AI
Limitations of Claude Code TodoWrite:
- β Session-level: Only exists in current conversation, disappears when session ends
- β No History: Cannot trace previous decisions and thought processes
- β Flat Structure: Lacks hierarchical relationships, difficult to manage complex tasks
Intent-Engine's Advantages:
- β Project-level: Persisted to SQLite database, permanently saved across sessions
- β Traceable: Complete event stream records context of every decision
- β Hierarchical: Task tree structure, enforces completing all subtasks before parent task
- β
Atomic Operations: Commands like
start,pick-next,spawn-subtask,switchsave 50-70% tokens
π Essential Differences from Other Tools
| Dimension | Intent-Engine | Claude Code TodoWrite | Jira/Linear |
|---|---|---|---|
| Core Philosophy | Strategic intent layer: What + Why | Tactical execution layer: What (temporary) | Task tracking layer: What + When |
| Primary Users | Humans β AI (bidirectional) | AI internal use (unidirectional) | Human teams (collaborative) |
| Lifecycle | Project-level (cross-session, persistent) | Session-level (temporary, volatile) | Project-level (persistent) |
| Data Structure | Task tree + Event stream + Specifications | Flat list (no hierarchy) | Workflows + Fields + Comments |
| History Tracing | β Complete decision history (events) | β No history | β οΈ Has comments but no structured decisions |
| Interaction Mode | CLI + JSON (AI-friendly) | Tool Call (AI-specific) | Web UI (human-friendly) |
| Granularity | Coarse-grained (strategic milestones) | Fine-grained (current steps) | Medium-grained (Sprint tasks) |
| Core Value | AI's external long-term memory | AI's working memory (short-term) | Team work coordination |
Typical Use Case Comparison
Intent-Engine: "Implement user authentication system" (includes complete technical specs, decision history, subtask tree)
- Lifecycle: Days to weeks
- AI can resume context anytime via
task start --with-eventsand continue working
TodoWrite: "Modify auth.rs file" (temporary step in current session)
- Lifecycle: Current session
- Disappears after session ends, cannot be recovered
Jira: "PROJ-123: Add OAuth2 support" (specific task assigned to team)
- Lifecycle: One Sprint (1-2 weeks)
- Requires manual status and progress updates
π Quick Start
1. Installation
# Method 1: Cargo Install (Recommended)
# Method 2: Download Pre-compiled Binary
# Visit https://github.com/wayfind/intent-engine/releases
# Verify Installation
π Detailed Installation Guide: See INSTALLATION.md for all installation methods, troubleshooting, and integration options.
2. Experience Core Features in 5 Minutes
# 1. Add a strategic task
| \
# 2. Start task and view context
# 3. Discover sub-problem during work? Create subtask and auto-switch
# 4. Record key decision (subtask is now current task)
| \
# 5. Complete subtask
# 6. Switch back to parent task and complete
# 7. Generate work report
π‘ More Detailed Tutorial: See QUICKSTART.md
π MCP Service: Deep Integration with Claude Code/Desktop
Intent-Engine provides a Rust-native MCP (Model Context Protocol) server, enabling Claude Code and Claude Desktop to directly use all Intent-Engine features without manually running commands.
Why Use MCP Service?
Traditional CLI Approach vs MCP Service:
| Aspect | CLI Commands | MCP Service |
|---|---|---|
| Usage | Humans manually execute commands | AI automatically invokes tools |
| Integration Difficulty | Need to copy-paste commands | Completely transparent, works out-of-box |
| Context Awareness | Need to manually pass task IDs | AI automatically manages current task |
| Token Efficiency | Need to output full commands | Atomic operations, save 50-70% |
| User Experience | Need to switch between terminal | Seamlessly complete within conversation |
Quick Installation
Method 1: Automatic (Recommended)
# Install from cargo
# Auto-configure MCP server for Claude Code
# Or for Claude Desktop
Method 2: From Source
# Clone the project
# Build and install (unified binary with CLI and MCP server)
# Auto-configure for Claude Code/Desktop
# Or use the shell script:
# ./scripts/install/install-mcp-server.sh
Note: The
setup-mcpcommand automatically detects your OS and configures the correct file path. It targets Claude Code v2.0.37+ by default.
Manual Configuration
Edit Claude's MCP configuration file:
Claude Code (v2.0.37+):
- Linux/macOS/WSL:
~/.claude.json - Windows:
%APPDATA%\Claude\.claude.json
Note: Earlier versions may use
~/.claude/mcp_servers.jsonor~/.config/claude-code/mcp_servers.json
Claude Desktop:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
Add configuration:
Restart Claude Code/Desktop, and you'll see 17 Intent-Engine tools available.
MCP Tools List
After installation, Claude can automatically use the following tools:
Task Management (12 tools):
task_add- Create strategic tasktask_add_dependency- Define task dependenciestask_start- Start task (atomic: set doing + set as current)task_pick_next- Intelligently recommend next tasktask_spawn_subtask- Create subtask and switch (atomic)task_switch- Switch tasks (atomic: pause current + start new)task_done- Complete task (validates all subtasks done)task_list- Find tasks by status/parent (renamed fromtask_find)task_get- Get detailed task informationtask_context- Get task ancestry and subtask treetask_update- Update task propertiestask_delete- Delete a task
Search & Discovery (1 tool):
search- Unified full-text search across tasks and events
Event Tracking (2 tools):
event_add- Record decisions/blockers/milestones (AI's external long-term memory)event_list- List event history with filtering
Workflow (2 tools):
current_task_get- Get currently focused taskreport_generate- Generate work reports
Usage Example
After installation, the experience in Claude Code:
You: "Help me implement a user authentication system"
Claude: I'll use Intent-Engine to track this work.
[Automatically calls task_add to create task #1]
[Automatically calls task_start to begin and get context]
"I've created and started task #1: Implement user authentication system.
Based on project analysis, I suggest breaking it down into these subtasks:
1. JWT Token generation and validation
2. User password hashing storage
3. Refresh Token mechanism
Let me create subtasks for each area..."
[Automatically calls task_spawn_subtask to create subtask #2]
[Begins implementing first subtask]
Key Advantages:
- β Zero Manual Operations: AI automatically manages tasks, no need to copy-paste commands
- β Context Preservation: Automatically resume task status and decision history across sessions
- β Transparent Tracking: All decisions automatically recorded to event stream
- β
Multi-project Isolation: Different projects automatically use their own
.intent-enginedatabases
Technical Advantages
Intent-Engine's MCP server uses Rust native implementation, compared to traditional Python wrappers:
| Metric | Rust Native | Python Wrapper |
|---|---|---|
| Startup Time | < 10ms | 300-500ms |
| Memory Usage | ~5MB | ~30-50MB |
| Dependencies | Zero | Requires Python 3.7+ |
| Performance | Native | IPC overhead |
Verify Installation
# Manually test MCP server (from project directory)
| \
# Or using environment variable
| \
INTENT_ENGINE_PROJECT_DIR=/path/to/your/project
# Should return JSON response with 13 tools
Detailed Documentation
- π Complete MCP Server Configuration Guide - Installation, configuration, troubleshooting
- π§ MCP Tools Sync System - Maintainer's guide
- π CLAUDE.md - Complete AI assistant integration guide
π Web Dashboard: Visual Task Management
New in v0.5: Intent-Engine now includes a built-in web dashboard for visual task management and monitoring.
Key Features
- β Modern Web UI: Beautiful interface powered by TailwindCSS and HTMX
- β Markdown Rendering: Rich text display with code syntax highlighting
- β Real-Time Search: Instant full-text search across tasks and events
- β Task Workflows: Visual buttons for start, complete, switch, and spawn operations
- β Event Tracking: Timeline view of decisions, blockers, milestones, and notes
- β Multi-Project Support: Run dashboards for multiple projects simultaneously
Quick Start
# Start dashboard (uses fixed port 11391)
# Open in browser automatically
# Or manually access the URL shown in the output
# http://127.0.0.1:11391
# Check running dashboards
# Stop dashboard
Why Use the Dashboard?
Perfect for:
- π Visualizing Progress: See task hierarchy and status at a glance
- π Browsing History: Review event timelines with rich Markdown rendering
- π¨ Presenting to Teams: Share project status via browser
- π Exploring Tasks: Search and filter large task sets interactively
Integration:
- All changes sync instantly with CLI and MCP tools (shares same database)
- RESTful API available for custom integrations
Documentation
- π Dashboard User Guide - Complete user manual
- π§ API Reference - REST API documentation
- ποΈ Architecture Spec - Technical design
β¨ Core Features
New in v0.4 (2025-11)
- π Unified Search Engine:
searchprovides full-text search across both tasks and events, retrieving complete context in a single query
New in v0.2 (2025-11)
- π Task Dependency System: Define task dependencies, automatically prevent blocked tasks from starting
- π Smart Event Querying: Filter events by type and time range, dramatically reduce token usage
- π― Priority Enum: Human-friendly priority interface (
critical/high/medium/low) - π Command Rename:
task findβtask listfor better clarity
Core Capabilities
- Project Awareness: Automatically searches upward for
.intent-enginedirectory, senses project root - Lazy Initialization: Write commands auto-initialize project, no manual init needed
- Task Tree Management: Support unlimited levels of parent-child task relationships
- Decision History: Complete event stream recording (decision, blocker, milestone, etc.)
- Smart Recommendation:
pick-nextrecommends next task based on context - Atomic Operations: Commands like
start,switch,spawn-subtasksave 50-70% tokens - π FTS5 Search Engine: Millisecond response under GB-scale tasks, unique snippet function highlights matches with
**, extremely Agent-context-friendly - JSON Output: All commands output structured JSON, perfect for AI tool integration
π Documentation Navigation
π― Core Documents
- INTERFACE_SPEC.md - Interface Specification (Authoritative)
- QUICKSTART.md - 5-minute quick start
π Getting Started
- The Intent-Engine Way - Design philosophy and collaboration patterns (highly recommended)
- Installation Guide - Detailed installation guide and troubleshooting
π€ AI Integration
- AI Quick Guide - AI client quick reference
- MCP Server - Integrate with Claude Code/Desktop
- Claude Skill - Lightweight Claude Code integration
π Deep Dive
- Command Reference - Complete command reference
- Task Workflow Analysis - Token optimization strategy explained
- Performance Report - Performance benchmarks
- Security Testing - Security test reports
- MCP Tools Sync - MCP tools synchronization system
π₯ Contributors
- Contributing Guide - How to contribute code
- Release Process - Release workflow
π Unique Value of Intent-Engine
1. Memory Sharing Layer for Human-AI Collaboration
- Humans set strategic intents (What + Why)
- AI executes tactical tasks (How)
- Intent-Engine records the entire process
2. Cross-session Context Recovery
- AI can resume complete context anytime via
task start --with-events - No need for humans to repeatedly explain background
3. Decision Traceability
- Every key decision is recorded (
event add --type decision) - Future review of "why we chose solution A over solution B"
4. Hierarchical Problem Decomposition
- Support unlimited levels of parent-child tasks
- Enforces completing all subtasks before parent task completion
π οΈ Technology Stack
- Language: Rust 2021
- CLI: clap 4.5
- Database: SQLite with sqlx 0.7
- Async Runtime: tokio 1.35
- Full-text Search: SQLite FTS5
π§ Development Setup
First-time Setup for Contributors (Required)
To avoid CI formatting check failures, please run immediately after cloning:
This installs git pre-commit hooks that automatically run cargo fmt before each commit, ensuring code formatting compliance.
Development Tool Commands
The project provides a Makefile to simplify common operations:
π Detailed Documentation: See scripts/README.md for complete development workflow and automation tools.
π§ͺ Testing
Intent-Engine includes a complete testing suite:
# Run all tests
# Run performance tests
# View test coverage
Test Statistics: 505+ tests all passing β
- Unit tests, integration tests, CLI tests
- MCP integration tests
- Special character security tests
- Performance and benchmarking tests
- Windows encoding compatibility tests
π License
This project is dual-licensed under MIT or Apache-2.0.
- MIT License - See LICENSE-MIT
- Apache License 2.0 - See LICENSE-APACHE
π€ Contributing
Issues and Pull Requests are welcome!
- Contributing Guide
- Code of Conduct (coming soon)
π Related Links
Next Steps: Read The Intent-Engine Way for deep understanding of design philosophy, or check out QUICKSTART.md to start using it right away.