thread-keeper logo
thread-keeper
★ 13
vs
metaharness logo
metaharness
★ 713

thread-keeper vs metaharness

thread-keeper: thread-keeper is a multi-agent shared brain that unifies memory, skills, and coordination across various LLM clients like Claude, Codex, and Copilot. It enables agents to share collective memory, signal each other, and autonomously improve their skill library over time, transforming isolated chats into a cohesive multi-agent system.; metaharness: MetaHarness is a CLI and browser Studio that mints custom AI agent harnesses from any GitHub repository, creating a repo-aware CLI, coding agent, and local MCP server tailored to the project. It acts as a factory for agent frameworks, allowing users to ship their own branded, npm-publishable AI agents with custom memory, governance, and model routing.

01

TL;DR

thread-keeper logo
thread-keeperMulti-Agent · ★ 13

Maintaining context across different LLM sessions and tools.

metaharness logo
metaharnessMulti-Agent · ★ 713

Creating a Repo-Specific Coding Agent: Generate a custom AI agent to assist with coding, maintenance, and automation tasks for a specific GitHub repository.

02

Side-by-Side Comparison

Field
thread-keeper logothread-keeper
metaharness logometaharness
Category
Multi-Agent
Multi-Agent
Stars
★ 13
★ 713
License
MIT
MIT
Install Command
pipx install 'threadkeeper[semantic]' && thread-keeper-setup
npx metaharness my-bot --template vertical:coding --host claude-code
Updated
1d ago
1d ago
Open Source
Yes
Yes
Tags
Multi-Agent System, Shared Memory, LLM Orchestration
AI Agent Generation, Multi-Agent System, LLM Infra
03

Features

thread-keeper logothread-keeper
01Collective and Cross-Session Memory
02Multi-Agent Coordination and Communication
03Autonomous Skill Improvement
04Unified Memory and Learning Across Multiple CLIs
metaharness logometaharness
01Custom AI Agent Harness Generation: Mints custom AI agent harnesses from any repo, complete with a repo-aware CLI and local MCP server.
02Repo Scoring & Cost Estimation: Scores any repository to assess harness fit, build likelihood, tool safety, and estimated cost per run before scaffolding.
03Model Routing & Optimization: Automatically routes requests to the cheapest model that meets quality standards, and supports training on custom data for better cost efficiency.
04Self-Evolving Harness (Darwin Mode): Enables the harness to mutate its own configuration, test changes in a sandbox, and keep only measurable improvements for continuous evolution.
05Multiple Host Compatibility: Supports deployment and execution on nine different agent hosts, including Claude Code, OpenAI Codex, pi.dev, Hermes, and GitHub Actions.
04

Use Cases

thread-keeper logothread-keeper
↳Maintaining context across different LLM sessions and tools.
↳Enabling knowledge transfer and skill sharing between various AI agents.
↳Coordinating parallel agent instances to avoid duplicate work and conflicts.
↳Building self-improving AI systems that learn from past interactions.
metaharness logometaharness
↳Creating a Repo-Specific Coding Agent: Generate a custom AI agent to assist with coding, maintenance, and automation tasks for a specific GitHub repository.
↳Optimizing LLM Costs in Agent Workflows: Utilize the model router to automatically select the cheapest model for each task while maintaining quality, reducing overall operational costs.
↳Continuous Improvement of Agent Performance: Employ Darwin Mode to allow agents to self-evolve and refine their configurations through sandbox testing and measurable improvements.
↳Publishing Branded Internal AI Tools: Publish custom, repo-tuned AI agents as npm packages for organizational use, ensuring consistent tooling and versioning.
↳Integrating Agents with Various LLM Platforms: Deploy the generated harnesses across multiple LLM host environments like Claude Code, OpenAI Codex, or GitHub Actions for broad compatibility.
05

Best For

thread-keeper logothread-keeper
—
metaharness logometaharness
Trending
FAQ

FAQ

What is the difference between thread-keeper and metaharness?
Both thread-keeper and metaharness are in the Multi-Agent category. thread-keeper has 13 stars, while metaharness has 713 stars.
Which is better, thread-keeper or metaharness?
The best choice depends on your use case. Choose thread-keeper if Maintaining context across different LLM sessions and tools., and metaharness if Creating a Repo-Specific Coding Agent: Generate a custom AI agent to assist with coding, maintenance, and automation tasks for a specific GitHub repository..
Is thread-keeper free or open source?
Yes, thread-keeper is open source on GitHub (MIT).
Is metaharness free or open source?
Yes, metaharness is open source on GitHub (MIT).
Cloud Infrastructure
Ad

Deploy on DigitalOcean

Host your MCP servers, Docker containers, and AI agents with $200 free credit over 60 days.

Claim $200 Free Credit
→

Related