Sugar
Autonomous AI development system for Claude Code with task queue management and workflow automation.
š° Sugar
Persistent memory for AI coding agents.
Sugar gives your AI agents memory that persists across sessions and projects. It remembers your decisions, patterns, and preferences so you stop re-explaining context every time you open a new session. The task queue builds on top of that memory layer to run work autonomously while you focus on other things.
What Sugar Does
Every AI coding session starts cold. You explain the same architectural decisions, re-describe the same error patterns, and re-establish the same preferences - over and over.
Sugar fixes that. It stores what matters and surfaces it when relevant:
- Project memory - Decisions, preferences, error patterns, and research stored per-project
- Global memory - Standards and guidelines shared across every project you work on
- Semantic search - Retrieve relevant context by meaning, not just keywords
- MCP integration - Your AI agent reads and writes memory directly during sessions
- Task queue - Hand off work to run autonomously, powered by the same memory layer
Quick Start
# Install once, use in any project
pipx install sugarai
# Initialize in your project
cd ~/dev/my-app
sugar init
# Store what you know
sugar remember "We use async/await everywhere, never callbacks" --type preference
sugar remember "JWT tokens use RS256, expire in 15 min - see auth/tokens.py" --type decision
sugar remember "When tests fail with import errors, check __init__.py exports first" --type error_pattern
# Retrieve it later
sugar recall "authentication"
sugar recall "how do we handle async"
Your AI agent can also read and write memory directly - no copy-pasting required.
MCP Integration
Connect Sugar's memory to your AI agent so it can access project context automatically.
Claude Code - Memory server (primary):
claude mcp add sugar -- sugar mcp memory
Claude Code - Task server (optional):
claude mcp add sugar-tasks -- sugar mcp tasks
Once connected, Claude can call store_learning to save context mid-session and search_memories to pull relevant knowledge before starting work. The memory server works from any directory - global memory is always available even outside a Sugar project.
Other MCP clients (Goose, Claude Desktop):
# Goose
goose configure
# Select "Add Extension" -> "Command-line Extension"
# Name: sugar
# Command: sugar mcp memory
# OpenCode - one command setup
sugar opencode setup
Global Memory (New in 3.8)
Some knowledge belongs to you, not just one project. Coding standards, preferred patterns, security practices - these should follow you everywhere.
# Store a guideline that applies to all your projects
sugar remember "Always validate and sanitize user input before any DB query" \
--type guideline --global
sugar remember "Use conventional commits: feat/fix/chore/docs/test" \
--type guideline --global
# View your global guidelines
sugar recall "security" --global
sugar memories --global
# Search works project-first, but guidelines always surface
sugar recall "database queries"
# Returns: project-specific memories + relevant global guidelines
Global memory lives at ~/.sugar/memory.db. Project memory lives at .sugar/sugar.db. When you search, project context wins - but guideline type memories from global always appear in results so your standards stay visible.
Via MCP, pass scope: "global" to store_learning to save cross-project knowledge directly from your AI session.
Memory types: decision, preference, file_context, error_pattern, research, outcome, guideline
Full docs: Memory System Guide
Task Queue
The task queue lets you hand off work and let it run autonomously. It reads from the same memory store, so Sugar already knows your preferences and patterns before it starts.
# Add tasks
sugar add "Fix authentication timeout" --type bug_fix --urgent
sugar add "Add user profile settings" --type feature
# Start the autonomous loop
sugar run
Sugar picks up tasks, executes them with your configured AI agent, runs tests, commits working code, and moves to the next task. It runs until the queue is empty or you stop it.
Delegate from Claude Code mid-session:
/sugar-task "Fix login timeout" --type bug_fix --urgent
Advanced task options:
# Orchestrated execution (research -> plan -> implement -> review)
sugar add "Add OAuth authentication" --type feature --orchestrate
# Iterative mode - loops until tests pass
sugar add "Implement rate limiting" --ralph --max-iterations 10
# Check queue status
sugar list
sugar status
Full docs: Task Orchestration
Supported AI Tools
Works with any CLI-based AI coding agent:
| Agent | Memory MCP | Task MCP | Notes |
|---|---|---|---|
| Claude Code | Yes | Yes | Full support |
| OpenCode | Yes | Yes | sugar opencode setup |
| Goose | Yes | Yes | Via MCP |
| Aider | Via CLI | Via CLI | Manual recall |
Installation
Recommended: pipx - installs once, available everywhere, no venv conflicts:
pipx install sugarai
Upgrade / Uninstall:
pipx upgrade sugarai
pipx uninstall sugarai
Other installation methods
pip (requires venv activation each session)
pip install sugarai
uv
uv pip install sugarai
With semantic search (recommended for memory):
pipx install 'sugarai[memory]'
With GitHub integration:
pipx install 'sugarai[github]'
All features:
pipx install 'sugarai[all]'
Sugar is project-local by default. Each project gets its own .sugar/ folder with its own database and config. Global memory lives at ~/.sugar/. Like git - one installation, per-project state.
Project Structure
~/.sugar/
āāā memory.db # Global memory (guidelines, cross-project knowledge)
~/dev/my-app/
āāā .sugar/
ā āāā sugar.db # Project memory + task queue
ā āāā config.yaml # Project settings
ā āāā prompts/ # Custom agent prompts
āāā src/
Recommended .gitignore:
.sugar/sugar.db
.sugar/sugar.log
.sugar/*.db-*
Commit .sugar/config.yaml and .sugar/prompts/ to share settings with your team.
Configuration
.sugar/config.yaml is created on sugar init:
sugar:
dry_run: false
loop_interval: 300
max_concurrent_work: 3
claude:
enable_agents: true
discovery:
github:
enabled: true
repo: "user/repository"
Documentation
- Quick Start
- Memory System
- CLI Reference
- Task Orchestration
- Goose Integration
- OpenCode Integration
- GitHub Integration
- Configuration Guide
- Troubleshooting
Requirements
- Python 3.11+
- A CLI-based AI agent: Claude Code, OpenCode, Aider, or similar
Contributing
Contributions welcome. See CONTRIBUTING.md.
git clone https://github.com/roboticforce/sugar.git
cd sugar
uv pip install -e ".[dev,test,github]"
pytest tests/ -v
License
Dual License: AGPL-3.0 + Commercial
- Open Source (AGPL-3.0): Free for open source and personal use
- Commercial License: For proprietary use - sugar.roboticforce.io/licensing
Sugar is provided "AS IS" without warranty. Review all AI-generated code before use.
Server Terkait
Scout Monitoring MCP
sponsorPut performance and error data directly in the hands of your AI assistant.
Alpha Vantage MCP Server
sponsorAccess financial market data: realtime & historical stock, ETF, options, forex, crypto, commodities, fundamentals, technical indicators, & more
MCP JS Debugger
Debug JavaScript and TypeScript applications through the Chrome DevTools Protocol with full source map support.
SpecLock
AI constraint engine ā persistent memory + active enforcement. Stops AI from breaking locked code. Semantic conflict detection, file-level guards, session continuity. 19 MCP tools.
Omega Memory
Persistent memory for AI coding agents with semantic search, contradiction detection, memory decay, and cross-session learning. 25 MCP tools, local-first, #1 on LongMemEval (95.4%).
Specifai
Integrate and automate Specifai projects with any MCP-compatible AI tool.
vHAL MCP Server
Search Android Vehicle Hardware Abstraction Layer (vHAL) documentation and source code from a local repository clone.
OpenZipline MCP
Provides secure, standards-compliant smart contract templates for tokens, access control, finance, and governance.
Authless Remote MCP Server
An example of a remote MCP server deployable on Cloudflare Workers without authentication.
DocGen MCP Server
Automated documentation generator from source files on Google Drive and GitHub.
.NET Types Explorer
Provides detailed type information from .NET projects including assembly exploration, type reflection, and NuGet integration for AI coding agents
Gurobi MCP
Solve optimization problems formulated by an LLM using the on-device Gurobi solver.