Meta Kim is live · free · last verified 24 Oct 2026 · viability monitor

Meta Kim

Meta Kim

Meta Kim: an open-source AI coding governance framework for auditable Claude Code, Codex and Cursor work

69/100MonitorFreeFree

If vibe coding has quietly become your build process, Meta Kim is the cheapest way to make it auditable: open source, no license fee, and blunt about the intent-to-evidence-to-verify-to-write-back loop. It slots into the assistants you already run and gates shell commands before they hit a real repo. The catch is the same as its strength — it's a CLI framework you configure yourself, so the audit trail only exists if you actually follow the cycle.

Verdict generated

Verified 6d ago · liveness 69/100 · cite: rightaichoice.com/tools/meta-kim

Best for
  • Solopreneurs shipping full products with AI as their entire team
  • Small teams practicing vibe coding who need repeatable, checkable workflows
  • Developers juggling multiple AI assistants and losing context between them
  • Game developers prototyping fast with AI while keeping an auditable trail
Not ideal for
  • Complete beginners with little or no AI coding or CLI experience
  • Teams that need an enterprise governance console with a point-and-click policy UI
  • Developers who prefer unstructured manual coding without process overhead
Visit Website

IntermediateFor a developer already fluent in Claude Code or Cursor: roughly an afternoon to wire the framework into your assistants and define your first goal with acceptance criteria. For a team spanning several assistants plus Coze, Dify or N8n: budget a day or two before the intent-verify-writeback loop feels automatic. Complete beginners should expect materially longer, since the CLI and the processCLIAPI availableVerified 6d ago
Pricing
Free
FreeFree tier4 hidden costs
Learning curve
Intermediate
For a developer already fluent in Claude Code or Cursor: roughly an afternoon to wire the framework into your assistants and define your first goal with acceptance criteria. For a team spanning several assistants plus Coze, Dify or N8n: budget a day or two before the intent-verify-writeback loop feels automatic. Complete beginners should expect materially longer, since the CLI and the process
Runs on
CLI
API available · 8 integrations
Who it's for
Solo developer shipping an MVP with AI assistantsSmall studio team prototyping a game featureDeveloper running an agent-driven automation across Coze, Dify or N8n
Live sentiment
Is Meta Kim actually worth it?

We scan live Reddit threads, YouTube comments, X posts, G2 reviews and other communities — and hand you an honest verdict in under a minute.

  • Honest verdict, not marketing
  • Real pros & cons from real users
  • Attributed quotes with receipts
Run a free scan

3 free scans · no card needed

Skip it if

Skip Meta Kim if you need a point-and-click governance console with an admin dashboard, or you have no CLI or multi-assistant AI coding workflow to govern yet.

Skip-it-if note generated
The 30-second take
Biggest gripe

There is no license fee, but you pay in setup time: configuring the framework against several assistants and orchestration tools is an afternoon before it earns anything back.

Price reality

Meta Kim carries no license cost and is open source, which puts it well below enterprise AI governance platforms that charge per seat with an admin console. That gap is the whole trade: you save the subscription and spend the difference in setup and CLI configuration. If your budget line for AI coding governance is zero and your team is technical, this is the cheapest credible option; if you need a supported console and someone to call, budget for a commercial platform instead.

Generated

In short

Meta Kim — Meta Kim: an open-source AI coding governance framework for auditable Claude Code, Codex and Cursor work. Best for Solopreneurs shipping full products with AI as their entire team, Small teams practicing vibe coding who need repeatable, checkable workflows, Developers juggling multiple AI assistants and losing context between them. Free to use.

What is Meta Kim?

Meta Kim — Meta Kim: an open-source AI coding governance framework for auditable Claude Code, Codex and Cursor work. Best for Solopreneurs shipping full products with AI as their entire team, Small teams practicing vibe coding who need repeatable, checkable workflows, Developers juggling multiple AI assistants and losing context between them. Free to use.

FreeIntermediateAPI availableCLI

Meta Kim (aiking.dev) is an open-source governance framework for AI-assisted coding, built by KimYx — a 15-year game industry producer and co-founder of a studio that shipped music-and-dance titles across China, Vietnam, Indonesia, Malaysia, Singapore and the Philippines. It targets developers, solopreneurs and small teams already building with Claude Code, Codex, Cursor or OpenClaw who keep hitting two problems: outputs vary run to run, and nobody can explain later why a change landed. The framework pushes every interaction through a fixed cycle — clarify intent, route the task to the right capability, collect evidence, verify the result, then write the lesson back into a knowledge base so the next run starts from something. Goals and Loops automation breaks a large objective into iterative loops and tracks long-running work, checking each step against predefined acceptance criteria before moving on. A safety checklist gates shell commands before execution, which matters the moment an agent has write access to a real repository. Orchestration reaches beyond the coding assistants into Coze, Dify and N8n, and Git handles version tracking of resulting changes. A 2026 blog post on giving AI long-term memory extends the knowledge-base idea: the framework carries context forward so you stop re-explaining the same setup every session. Recent project-blog posts (August 2026) added a reference layer — an index of 24 personal open-source AI knowledge bases, an index of legacy tools and historical materials, prompt template resources, AI programming and product writing, and AI industry observations. The positioning is narrow on purpose. Meta Kim is a CLI-first process layer you configure against assistants you already pay for — not a governance console, not a no-code dashboard, and not a replacement for Claude Code or Cursor. If you want a point-and-click policy UI with SSO and org-wide reporting, an enterprise governance platform is the honest answer. If you want an

Key features

  • Open-source governance framework for AI-assisted coding
  • Clarify intent before execution to cut ambiguous prompts
  • Route tasks to the right AI capability per job
  • Collect and review evidence for each AI-driven change
  • Verify results against predefined acceptance criteria
  • Write lessons back to a knowledge base for future runs
  • Long-term memory so context carries across sessions
  • Goals and Loops automation for breaking down complex goals
  • Track long-running agent tasks with per-step verification
  • Safety checklist gates shell commands before execution
  • Multi-assistant support: Claude Code, Codex, Cursor, OpenClaw
  • Agent orchestration with Coze, Dify and N8n
  • CLI-based operation for developer workflows
  • Git version control compatibility for change tracking
  • Index of 24 personal open-source AI knowledge bases and prompt templates

Behind the verdict

Most AI governance tools are sold to someone in compliance, not to the person actually running Claude Code at 11pm. Meta Kim flips that: it's a process layer for the developer, shipped as an open-source CLI framework you point at the assistants already on your machine. We'd reach for it when a solo build or a small team has crossed the line where 'it worked last time' is no longer good enough — when you need to reconstruct why a change landed and what evidence backed it. The intent-route-evidence-verify-writeback cycle is the product. In practice that means fewer ambiguous prompts going straight to execution, acceptance criteria checked before the next step, and a lesson written back so you're not re-explaining your codebase every session. The 2026 blog post on giving AI long-term memory is the clearest signal of where KimYx is pushing: carry context forward instead of re-briefing from scratch. Where it bites: this is configuration work, not installation. You define the checklists, the routing, the acceptance criteria — and if you skip that, you get the ceremony without the audit trail. Beginners with no CLI background will bounce off it quickly. There's no point-and-click policy editor, no SSO, no org-wide dashboard, so anyone shopping for an enterprise governance console should look elsewhere and pay for it. Compared with a governance platform bolted onto an IDE, Meta Kim's advantage is price and portability. It's free, it isn't tied to one assistant, and it happily spans Claude Code, Codex, Cursor and OpenClaw alongside Coze, Dify and N8n orchestration. That breadth is also the risk — multi-tool setups drift, and someone has to keep the framework current as each assistant changes. One caveat on freshness: the vendor site is a personal homepage, so framework

Models under the hood

GLM-5.2Kimi K3Hunyuan 3Qwen Image3

as of 2026-10-23

Limitations

  • Meta Kim runs through the CLI of your existing AI coding tools, so there is no graphical interface for setup — you need comfort with the command line.
  • It expects prior mileage with AI assistants; the intent-route-verify-writeback discipline is heavy for a first project.
  • Documentation may lag active development, and advanced features such as automated lesson write-back can require manual configuration.
  • The August 2026 additions (knowledge base, prompt template and legacy tool indexes) are curated indexes of external material, not framework documentation.
  • Orchestration spans Claude Code, Codex, OpenClaw, Cursor, Coze, Dify, N8n and Git, so a multi-tool environment is assumed rather than optional.

as of 2026-10-04

Researching Meta Kim? Get your full AI stack in 60 seconds.

Free, no signup — tell us your goal and get tools matched to your budget & existing stack.

Is Meta Kim still active?

Meta Kim is live · free · last verified 24 Oct 2026 · viability monitor.

Viability score

69/100
Monitor

How well maintained and how widely used is Meta Kim? Built from what the vendor actually publishes (docs, changelog, tutorials, integrations, pricing), whether the site is live, and how much real users discuss it. How we calculate this

Recent activity
90
Traction
100
Site health
95
User sentiment
48
What the vendor publishes
20

Last calculated: October 2026

How we score →

What's new in Meta Kim

Checked 7 days ago

Across the latest 1 update: 1 community discussion.

What do users say about Meta Kim?

What people actually say about Meta Kim — is it worth it?

We ran a structured research pass across product reviews, community discussions, and post-purchase forum threads to surface the patterns vendors won't publish themselves. Below: the recurring strengths, the hidden costs people mention most, and the cohort that consistently regrets adopting this tool.

Researched

39 mentions across 3 sources (YouTube, GitHub, Lemmy) · researched Aug 19, 2026.

48% positive52% critical

Average across the 3 sources that answered — each source counts once, not each post.

Recurring strengths
  • +Provides genuine governance and traceability for AI coding workflows.
  • +Works across multiple popular AI assistants including Claude Code, Codex, and Cursor.
  • +Lesson write-back turns AI into a learning partner, addressing context loss.
  • +Open-source and free with no hidden pricing.
  • +Goal and Loop automation helps manage long-running complex tasks.
Recurring frustrations
  • −Update process is broken, causing frustration during routine maintenance.
  • −CLI-first design excludes non-technical users and has a steep learning curve.
  • −Overwhelmingly niche—very limited community presence outside GitHub.
  • −No pruning mechanism leads to potential knowledge noise and bloat over time.
  • −Minimal documentation for setup, especially for users new to CLI tools.
Patterns worth knowing
Governance philosophy is appreciated but needs better implementation
Seen on GitHub, YouTube
Update process has serious bugs that break the tool
Seen on GitHub
Long-term knowledge base needs pruning to avoid noise explosion
Seen on GitHub
Learning curve
intermediateProductive in ~A few hours
Hidden costs people mention
  • • No direct monetary costs, but setup requires significant time and learning effort

How we verified this

Every listed fact about Meta Kim— pricing, features, links, status — is re-read from the vendor's own pages by our verification pipeline and each change is logged with a date; the last pass ran on 24 Oct 2026. Pages mix model-assisted synthesis with human review; see how we verify.

Verification history

We have re-verified Meta Kim 12 times since . Each pass re-reads the vendor's own pages and re-checks every listed field against that evidence; passes where nothing had changed are marked as such.

  1. — changed pricing page
  2. — changed who it suits, our verdict, pricing tiers, description, summary, features
  3. — changed pricing page
  4. — changed features, pricing tiers, description, who should skip it, who it suits, our verdict, summary, SSL certificate
  5. — changed pricing page
  6. — changed pricing fit, who it suits, description, our verdict, features, hidden costs, integrations, limitations, switching in, switching out, who should skip it, pricing tiers, setup time, summary, use cases

Showing the 6 most recent of 12 verification passes.

Free to cite with attribution — this page re-verifies continuously.

How much does Meta Kim cost in 2026?

Meta Kim: Free to use. Pricing last verified 24 Oct 2026.

Plans compared

Every published Meta Kim tier, its price as the vendor publishes it, who it fits, and what it adds over the tier below. The 12-month cost projection follows.

Meta Kim pricing plans compared
PlanPriceBillingWho it's for
Open SourceFree—Solo developers and small technical teams who already code with Claude Code, Codex, Cursor or OpenClaw and want governance without a license line item.Adds: Starting tier with no license cost: full framework source, Goals and Loops automation, evidence review, verification, shell-command safety checklist and the reference indexes.

12-month cost

Project the real annual outlay, including the implied monthly cost when only an annual tier is published.

Annual total
Free
Over 12 months
Effective monthly
—
—

Vendor list price only. Add-on usage, seat overages, and contract minimums are surfaced under Hidden costs & gotchas.

Hidden costs & gotchas

What the public pricing page doesn't put in bold. Captured from pricing-page footnotes, contract terms, and recurring complaints.

  • There is no license fee, but you pay in setup time: configuring the framework against several assistants and orchestration tools is an afternoon before it earns anything back.
  • Running multiple assistants concurrently (Claude Code, Codex, Cursor, OpenClaw) means multiple subscriptions and their own usage limits, billed separately from Meta Kim.
  • Automated lesson write-back may need manual configuration, which turns into maintenance time each time your toolchain changes.
  • Documentation can trail active development, so upgrading may cost debugging hours you would not spend on a maintained commercial product.

Where the pricing makes sense

The company stage and team size where Meta Kim's pricing actually pencils out — and where peers do it cheaper.

Meta Kim carries no license cost and is open source, which puts it well below enterprise AI governance platforms that charge per seat with an admin console. That gap is the whole trade: you save the subscription and spend the difference in setup and CLI configuration. If your budget line for AI coding governance is zero and your team is technical, this is the cheapest credible option; if you need a supported console and someone to call, budget for a commercial platform instead.

Hidden-cost and price-fit notes generated

Has Meta Kim's pricing changed?

No plan price for Meta Kim has moved since we began logging in Aug 2026; the pricing page is re-read on every verification pass.

Who should pick Meta Kim?

Pick Meta Kim if you are Solopreneurs shipping full products with AI as their entire team, Small teams practicing vibe coding who need repeatable, checkable workflows, Developers juggling multiple AI assistants and losing context between them, Game developers prototyping fast with AI while keeping an auditable trail.

Look elsewhere if you are Complete beginners with little or no AI coding or CLI experience, Teams that need an enterprise governance console with a point-and-click policy UI, Developers who prefer unstructured manual coding without process overhead, Anyone looking for a no-code or point-and-click solution.

Skip it if Skip Meta Kim if you need a point-and-click governance console with an admin dashboard, or you have no CLI or multi-assistant AI coding workflow to govern yet.

Generated

Real-world workflow fit

Concrete scenarios for the personas Meta Kim actually fits — and what changes day-one when you adopt it.

Solo developer shipping an MVP with AI assistants

Breaks the MVP into goals, sets acceptance criteria per loop, then runs refactor and build tasks through Claude Code and Codex with the safety checklist gating shell commands.

Outcome: A recorded trail of what each assistant changed and why, plus a knowledge base entry per loop, so the next session starts from accumulated context instead of a blank prompt.

Small studio team prototyping a game feature

Routes art-pipeline and gameplay-logic tasks to the best-suited assistant by capability tag, with evidence review and result verification before any change is accepted.

Outcome: Prototype iterations stay traceable and reviewable, which matters when the same repo is touched by several assistants across a week.

Developer running an agent-driven automation across Coze, Dify or N8n

Sets long-running orchestration tasks with per-step verification, and writes lessons back so repeated jobs inherit the fixes from prior runs.

Outcome: Automated agent work runs against predefined criteria rather than blind trust, with Git tracking the resulting changes.

Workflow scenarios generated

Use cases

  • Orchestrate a long-running refactoring task across Claude Code and Codex with per-step progress tracking.
  • Define a product goal and break it into loops that each produce a verifiable deliverable.
  • Set up a knowledge base that collects lessons from every AI session to improve future prompts.
  • Route specific coding tasks to the best-suited AI assistant based on capability tags.
  • Create a repeatable workflow for building an MVP with multiple AI tools without losing the audit trail.
  • Gate shell commands behind a safety checklist before an agent executes them on a live repo.

Setup time & first value

How long it actually takes to get something useful out of Meta Kim — broken out by persona, not the marketing-page minute.

For a developer already fluent in Claude Code or Cursor: roughly an afternoon to wire the framework into your assistants and define your first goal with acceptance criteria. For a team spanning several assistants plus Coze, Dify or N8n: budget a day or two before the intent-verify-writeback loop feels automatic. Complete beginners should expect materially longer, since the CLI and the process

Switching to or from Meta Kim

How to bring data in from common predecessors and how to get it back out — written for the switcher, not the buyer.

Migrating in
  • →From ad-hoc prompting in Claude Code or Cursor: install the framework and re-express your current task as a goal with explicit acceptance criteria.
  • →From a shared prompt document or Notion playbook: convert the prompts into prompt templates and move the notes into the lesson knowledge base.
  • →From a single-assistant workflow: add a second assistant and let capability routing decide which one takes each task.
Migrating out
  • ↗To an enterprise AI governance console: export your evidence and lesson records, then rebuild acceptance criteria as policy rules in the console.
  • ↗To plain assistant workflows: keep the prompt templates and knowledge base as reference material; the loop enforcement is what you give up.
  • ↗To a different orchestration stack: the Coze, Dify and N8n connections are re-pointed rather than rebuilt, but per-step verification logic needs re-testing.

Tutorials & Learning

YouTube returned 6 videos for “Meta Kim”, and we withheld 6: 6 did not mention Meta Kim. We are showing none, because we could not prove any of them are about Meta Kim.

Official links

What are the best Meta Kim alternatives?

The closest alternatives to Meta Kim we list are Ui Ux Pro Max Skill, OpenSpec and Hue. Ranked by direct product-type match, not category overlap.

Closest alternatives to Meta Kim
AlternativePricingStarts atLast verified
Ui Ux Pro Max SkillFreeFree—
OpenSpecFreeFree—
HueFreeFree—

Alternatives to Meta Kim

View all
Ui Ux Pro Max Skill

Ui Ux Pro Max Skill

Free open-source design-intelligence skill that feeds UI styles, palettes, fonts, and chart rules into Claude Code, Cursor, and other AI coding assistants.

FreeTry
OpenSpec

OpenSpec

OpenSpec is an open-source spec-driven development framework that keeps AI coding agents building the right thing, with verify and archive

FreeTry
Hue

Hue

Open-source skill that turns any brand into a design system Claude Code and Codex can build with

FreeTry

Tools that pair well with Meta Kim

Common stack mates teams adopt alongside Meta Kim, with the specific reason each pairing earns its keep.

Meta Kim vs its closest rival

Meta Kim's closest head-to-head is with Spider Cloud — These tools serve completely different needs. Spider Cloud is a high-performance data extraction API for AI agents (RAG, scraping), while Meta Kim is an open-source governance layer for AI coding assistants. Choose Spider Cloud if you need reliable, cost-effective web data for your LLMs; choose Meta Kim if you want structured, traceable AI-assisted coding workflows. Verdict generated

Head-to-head comparisons

Frequently asked questions

Used Meta Kim? Help shape our editorial sentiment research.