Memo Code

A lightweight coding agent for terminal and web workflows.

Website · Documentation · 中文文档

Memo started with a simple question: What does the simplest Agent look like?

In the second half of 2024, while writing my tech blog post Agent = LLM + TOOL, I began thinking about the essence of Agents — nothing more than LLM + Tool loops. But when I actually started implementing it, I discovered that behind every seemingly simple feature lies a mountain of engineering details:

• Best practices for system prompts
• Tool design and security boundaries
• Multi-model switching and compatibility
• Context management (especially long-session compaction strategies)
• Tricky TUI interactions
• Multi-workspace support for Web version
• npm package distribution and hot-reloading
• ...

This project grew from a small demo into an indispensable "productivity assistant" in my daily development — it helps me update documentation, manage GitHub Issues, debug projects... While I still use Claude Code and Codex CLI as my primary development tools, Memo quietly handles the tedious tasks in the background.

This is a personal project built from scratch. All architectural designs and technical decisions are independent explorations and trade-offs. If you're interested in the engineering implementation of Agents, I hope Memo can give you some reference.

npm install -g @memo-code/memo
# or pnpm / yarn / bun

export OPENAI_API_KEY=your_key
# or configure other compatible APIs

memo

First run will guide you through Provider/Model setup and save config to ~/.memo/config.toml.

memo-code/
├── packages/
│   ├── core/          # Core logic: Session state machine, Config handling
│   ├── tools/         # Tool routing, MCP Client management, built-in tools (exec_command, read_text_file, apply_patch...)
│   ├── tui/           # Terminal runtime: CLI entry, interactive TUI
│   ├── web-ui/        # Web frontend: React components
│   └── web-server/    # Web backend: session management, API adapter
└── docs/              # Technical documentation

Technical Highlights:

• Architecture: Clean Core / Tools / TUI separation, state-machine driven session management
• Testing: Core + Tools coverage > 70%, complete unit + integration tests
• Protocol: Native MCP (Model Context Protocol) support, can integrate any MCP tool server
• Token Estimation: Real-time context monitoring based on tiktoken, configurable auto-compaction strategy
• Distribution: npm package with pre-built Web assets, hot-reloading without perception

• exec_command / write_stdin - Execute Shell commands
• apply_patch - Structured patch editing (*** Begin Patch/*** End Patch)
• read_text_file / read_media_file / read_files / write_file / edit_file / list_directory / search_files - Filesystem read/write/search
• webfetch - Paged web fetching with markdown extraction and policy guards
• MCP resource access - list_mcp_resources, read_mcp_resource
• update_plan - Structured task progress management
• get_memory - Persistent memory reading

current_provider = "openai_compatible"
auto_compact_threshold_percent = 80

[[providers.openai_compatible]]
name = "openai_compatible"
env_api_key = "OPENAI_API_KEY"
model = "gpt-4.1-mini"
base_url = "https://api.openai.com/v1"

# MCP Server
[mcp_servers.github]
command = "npx"
args = ["-y", "@modelcontextprotocol/server-github"]

# Skills
active_skills = ["./skills/doc-writing/SKILL.md"]

# Install dependencies
pnpm install

# Run locally
pnpm start

# Build for distribution
pnpm run build

# Test
pnpm test              # all tests
pnpm run test:coverage # coverage report (threshold ≥70%)

# Format
pnpm run format        # write
pnpm run format:check  # CI check

MIT License