leon-ai/leon

🧠 Leon is your open-source personal assistant.

View on GitHub ↗Jump to charts ↓Open shareable report →

Summary Information

Updated 10 minutes ago
Added to GitGenius on August 31st, 2026
Created on February 10th, 2019
Open Issues & Pull Requests: 111 (+0)
Number of forks: 1,470
Total Stargazers: 17,475 (-3)
Total Subscribers: 276 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 28.2 hours
Mean response time: 55.9 days
90th percentile: 320.1 days
Tracked items: 29

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 95% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Only 11% of issues opened in the past year have been closed. Three people close 53% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 21
New in 7 days: 1
Closed in 7 days: 0
Avg open age: 635 days
Stale 30+ days: 20
Stale 90+ days: 16

Recent activity

Opened in 7 days: 1
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (21)
  • feature request (3)
  • question (3)
  • improvement (2)
  • skill (1)

Detailed Description

Leon is an open-source personal AI assistant built around tools, context, memory, and agentic execution.

Leon addresses the need for a privacy-aware assistant that operates locally without relying on cloud services or free-form guessing. The tool combines intent understanding with agentic capabilities, allowing it to choose how to handle tasks, use dedicated tools, remember information, and recover from errors. It can complete workflows deterministically or through agent-style execution, grounding its responses in your real environment rather than generating generic answers.

The project suits developers who want a customizable assistant they can run locally with full control over data and behavior. It differs from traditional intent-classification assistants by incorporating memory systems, tool integration, and agentic decision-making. Those evaluating adoption should note that the project is undergoing significant architectural changes, with a 2.0 Developer Preview on the develop branch representing the new direction, while the master branch contains the earlier, more stable version. The new documentation is still in development, so understanding the current state requires consulting the architecture and context files rather than traditional guides.

Development activity shows active work on core architectural changes, with the project maintaining separate branches to support both legacy users and those exploring the new agentic capabilities. The maintainer shares progress regularly through external channels and maintains a public roadmap for planned features.