Comparison
eclaire vs llm-wiki-agent
Verdict
Pick eclaire if eclaire is a local-first, self-hosted AI assistant designed for private data management and task automation; pick llm-wiki-agent if llm-wiki-agent serves as a self-maintained personal knowledge base using AI agents like Claude, Codex, OpenCode, and Gemini CLI.
Markdown twin · eclaire alternatives · llm-wiki-agent alternatives
GraphCanon updated Sep 20, 2026
12views this month
vs
Trust & integrity
| Signal | eclaire | llm-wiki-agent |
|---|---|---|
| Maintenance | Slowing (128d since push) As of Sep 20, 2026 · github_public_v1 | Very active (0d since push) As of Sep 8, 2026 · github_public_v1 |
| Provenance | Not a fork · Organization account As of Sep 20, 2026 · github_public_v1 | Not a fork · Organization account As of Sep 8, 2026 · github_public_v1 |
| OSV dependency advisories | No lockfile (source not queried) As of Jul 15, 2026 · osv@v1 | No published findings from this source as of 2026-07-11 As of Jul 11, 2026 · osv@v1 |
| deps.dev advisories | Not queried deps.dev@v1 | Not queried deps.dev@v1 |
| OpenSSF Scorecard | Not queried openssf-scorecard@v1 | Not queried openssf-scorecard@v1 |
Tagline
- eclaire
- Local-first self-hosted AI assistant for data and task management
- llm-wiki-agent
- A personal knowledge base that builds and maintains itself using various AI agents.
Stars
- eclaire
- 923
- llm-wiki-agent
- 3.5k
Forks
- eclaire
- 95
- llm-wiki-agent
- 397
Open issues
- eclaire
- 2
- llm-wiki-agent
- 5
Language
- eclaire
- TypeScript
- llm-wiki-agent
- Python
Adopt for
- eclaire
- Eclaire is a local-first, self-hosted AI assistant designed for private data management and task automation.
- llm-wiki-agent
- llm-wiki-agent serves as a self-maintained personal knowledge base using AI agents like Claude, Codex, OpenCode, and Gemini CLI.
Persona
- eclaire
- -
- llm-wiki-agent
- -
Runtime
- eclaire
- -
- llm-wiki-agent
- -
License
- eclaire
- Eclaire is available under the MIT License, permitting free modification and distribution while providing disclaimers on warranties.
- llm-wiki-agent
- MIT
Last pushed
- eclaire
- May 14, 2026
- llm-wiki-agent
- Sep 7, 2026
Categories
- eclaire
- AI Agents, Data & Retrieval
- llm-wiki-agent
- AI Agents, Data & Retrieval
Trust and health
Maintenance
- eclaire
- Slowing (36%)
- llm-wiki-agent
- Very active (96%)
Days since push
- eclaire
- 128d
- llm-wiki-agent
- 0d
Open issues (now)
- eclaire
- 2
- llm-wiki-agent
- 5
Stars delta
- eclaire
- +28 (30d)
- llm-wiki-agent
- +163 (30d)
Open issues delta
- eclaire
- +1 (30d)
- llm-wiki-agent
- +2 (30d)
OSV dependency advisories
- eclaire
- No lockfile (source not queried)
- llm-wiki-agent
- No published findings from this source as of 2026-07-11
Full report
- eclaire
- Trust report
- llm-wiki-agent
- Trust report
Choose eclaire if…
- eclaire is primarily TypeScript; llm-wiki-agent is Python.
- Requirements: Self-hosting setup will vary depending on user's local server capabilities..
- Tags unique to eclaire: ai-assistant, document-processing, local-first, note-taking.
- When you require a privately managed environment for all your notes and documents since Eclaire stores everything locally without sending it to the cloud.
When NOT to use eclaire
- When you do not want to manage server infrastructure for running the Eclaire software since it requires self-hosting capabilities and ongoing maintenance.
- If your use case demands connectivity and synchronization across multiple devices over different networks, as Eclaire's local-first model might introduce limitations in accessibility.
Choose llm-wiki-agent if…
- llm-wiki-agent is primarily Python; eclaire is TypeScript.
- Tags unique to llm-wiki-agent: ai-agent, automation, knowledge-base, llm.
- When you need to create an interlinked wiki without setting up API keys or configuring Python environments.
When NOT to use llm-wiki-agent
- If the process requires strict privacy controls and no third-party AI agents can be used.
- When your project needs real-time interaction with APIs for dynamic content integration, as llm-wiki-agent does not support API-driven operations.
Explore
Sources
Every stat on this page traces to a dated GitHub sync, license file, enrichment field, or trust scan.
- GitHub stars (eclaire-labs/eclaire) · observed Sep 20, 2026
- GitHub forks (eclaire-labs/eclaire) · observed Sep 20, 2026
- Last push (eclaire-labs/eclaire) · observed May 14, 2026
- License file (MIT) · observed Sep 20, 2026
- Decision facts (enrichment) · observed Jul 17, 2026
- Trust scan (lockfile / OSV) · observed Jul 15, 2026
- GitHub stars (SamurAIGPT/llm-wiki-agent) · observed Sep 20, 2026
- GitHub forks (SamurAIGPT/llm-wiki-agent) · observed Sep 20, 2026
- Last push (SamurAIGPT/llm-wiki-agent) · observed Sep 7, 2026
- License file (MIT) · observed Sep 20, 2026
- Decision facts (enrichment) · observed Jul 14, 2026
- Trust scan (lockfile / OSV) · observed Jul 11, 2026
GitHub stars on cards: eclaire 923 · llm-wiki-agent 3.5k (synced Sep 20, 2026).
Common questions
- What is the difference between eclaire and llm-wiki-agent?
- eclaire: Local-first self-hosted AI assistant for data and task management. llm-wiki-agent: A personal knowledge base that builds and maintains itself using various AI agents.. See the comparison table for live GitHub stats and shared categories.
- When should I choose eclaire over llm-wiki-agent?
- Choose eclaire over llm-wiki-agent when eclaire is primarily TypeScript; llm-wiki-agent is Python; Requirements: Self-hosting setup will vary depending on user's local server capabilities.; Tags unique to eclaire: ai-assistant, document-processing, local-first, note-taking; When you require a privately managed environment for all your notes and documents since Eclaire stores everything locally without sending it to the cloud.
- When should I choose llm-wiki-agent over eclaire?
- Choose llm-wiki-agent over eclaire when llm-wiki-agent is primarily Python; eclaire is TypeScript; Tags unique to llm-wiki-agent: ai-agent, automation, knowledge-base, llm; When you need to create an interlinked wiki without setting up API keys or configuring Python environments.
- When should I avoid eclaire?
- When you do not want to manage server infrastructure for running the Eclaire software since it requires self-hosting capabilities and ongoing maintenance. If your use case demands connectivity and synchronization across multiple devices over different networks, as Eclaire's local-first model might introduce limitations in accessibility.
- When should I avoid llm-wiki-agent?
- If the process requires strict privacy controls and no third-party AI agents can be used. When your project needs real-time interaction with APIs for dynamic content integration, as llm-wiki-agent does not support API-driven operations.
- Is eclaire or llm-wiki-agent more popular on GitHub?
- llm-wiki-agent has more GitHub stars (3,497 vs 923). Stars measure visibility, not whether either tool fits your constraints.
- Are eclaire and llm-wiki-agent open source?
- Yes - both are open-source projects on GitHub (eclaire: MIT, llm-wiki-agent: MIT).
- Where can I find alternatives to eclaire or llm-wiki-agent?
- GraphCanon lists graph-backed alternatives at eclaire alternatives and llm-wiki-agent alternatives (eclaire markdown twin, llm-wiki-agent markdown twin), ranked by typed relationship edges rather than popularity votes.
- Is there a machine-readable version of this comparison?
- Yes. The markdown twin at this comparison mirrors this page for agents and LLM crawlers, with the same stats table and FAQ answers.
- Which is better maintained, eclaire or llm-wiki-agent?
- eclaire: Slowing. llm-wiki-agent: Very active. Compare maintenance labels, days since push, and release cadence in the trust section below - stars alone do not measure maintenance.
- Where are the full trust reports for eclaire and llm-wiki-agent?
- GraphCanon publishes per-repo trust reports with dated maintenance, provenance, and scan summaries: eclaire trust report; llm-wiki-agent trust report.