umadev
Turn your logged-in CLI agents into an 8-role AI dev team with governance and audits.
UmaDev is the rare open-source agent that treats code review as a real engineering practice. If you already live in Claude Code or Codex and want governance, cross-review, and evidence-based delivery, it's worth adopting today. Skip it if you want a hands-off, wait-for-magic prototyping tool.
Verified 7d ago · liveness 68/100 · cite: rightaichoice.com/tools/umadev
- Solo developers who want a full AI dev team without juggling multiple agents
- Small teams that need governance, audit trails, and compliance mapping for code generation
- Developers already using Claude Code, Codex, OpenCode, Grok Build, or Kimi Code who want structured workflows
- Engineers building production apps where quality gates matter more than speed
- Users who want a fully autonomous agent with zero human review gates
- Teams that require cloud-hosted API keys or managed infrastructure (local-only CLI)
- Users looking for a pure IDE plugin experience (it's a standalone TUI/CLI tool)
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
3 free scans · no card needed
Skip UmaDev if you want a fully autonomous, zero-review agent or a cloud-hosted managed service, or if you don't already have a logged-in CLI coding agent installed.
You must have a paid subscription to at least one of the underlying CLI agents (Claude Code, Codex, etc.)—UmaDev itself is free, but the base agents are not.
UmaDev is free and open-source (MIT), making it a zero-cost option compared to managed tools like Bolt or Lovable, which charge subscription fees. The real cost is the underlying CLI agents, which you may already have.
In short
umadev — Turn your logged-in CLI agents into an 8-role AI dev team with governance and audits. Best for Solo developers who want a full AI dev team without juggling multiple agents, Small teams that need governance, audit trails, and compliance mapping for code generation, Developers already using Claude Code, Codex, OpenCode, Grok Build, or Kimi Code who want structured workflows. Free to use.
What's new in umadev
Checked 7 days agoAcross the latest 5 updates: 5 changelog entries.
UmaDev v1.0.73 released — Continuation state machine closed-loop; write intent no longer misclassified as read-only; review failures bounded.
Fixes continuation state machine, write intent misclassification, and bounds review failures.
UmaDev v1.0.72: deep audit of boundaries, permissions, and release chain
Full-project deep audit; status queries read host facts directly; permission bypass fixes; release chain hardened.
UmaDev v1.0.70: interaction channels audited, permission bypass fixed
Fixed permission bypass; delivery and lifecycle hardening; accurate usage accounting.
UmaDev v1.0.69: systematic harden of base interaction channels
Permission control root cause fixed; settlement made honest; HostRequestSettled retraction basis added.
UmaDev v1.0.67: current request priority and capability-based adaptation
Current user request is the sole authorization source; evidence and memory become traceable; base capability adaptation.
What people actually say about umadev — 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.
6 mentions across 2 sources (YouTube, GitHub) · researched Jul 1, 2026.
- +Open-source and MIT licensed — no vendor lock-in.
- +Orchestrates eight distinct AI roles for comprehensive coverage.
- +Runs entirely locally, keeping code and data private.
- +Enforces 112 governance rules to improve code quality.
- +Includes human-in-the-loop gates for documentation and frontend previews.
- −Almost no real user reviews or community feedback exists.
- −YouTube search results are entirely about unrelated beauty products.
- −Dependency on third-party CLI tools outside UmaDev's control.
- −Setup and learning curve likely steep for beginners.
- −Quality gate threshold (90%) may block delivery with minor issues.
- • You must have active subscriptions for Claude Code, Codex CLI, or OpenCode, which have their own costs.
Viability Score
How well maintained and how widely used is umadev? 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
Last calculated: August 2026
How we score →Key Features
- Orchestrates 5 base CLIs: Claude Code, Codex, OpenCode, Grok Build, Kimi Code
- 8 AI dev roles: PM, architect, designer, frontend, backend, QA, security, DevOps
- 113 governance checks and 34 formal rules
- Quality gate with configurable pass line (default 90%)
- Five task modes: Chat, Explain, QuickEdit, Debug, Build
- Independent cross-reviews in read-only fork sessions
- Plan/DAG with live steering via /plan (skip, veto, add, reorder)
- Project memory with local hybrid RAG (BM25 + optional semantic + HyDE)
- Repo-map parsing of symbols and import edges
- Auditable delivery pack (ZIP + HTML scorecard) with SOC 2, ISO 27001, EU AI Act mapping
- Self-healing TUI with Windows support (PTY, /exit cleanups)
- MCP server mode to expose governance to other tools
- Trust gradients (plan/guarded/auto) with confirmation for irreversible actions
- Git transaction atomicity and permission tiers (v1.0.65)
- Write intent closure and read-only fixes (v1.0.64)
About umadev
UmaDev is an open-source, MIT-licensed Rust binary that transforms your local, log-in-first CLI agents—Claude Code, Codex, OpenCode, Grok Build, and Kimi Code—into an eight-person AI dev team. It orchestrates specialized roles (PM, architect, designer, frontend, backend, QA, security, DevOps) from a single requirement, routing tasks through five modes—Chat, Explain, QuickEdit, Debug, Build—so small fixes skip the heavy pipeline and only real builds get the full project plan. Unlike wrappers that hand one model your prompt and accept its answer, UmaDev separates writing from review: the main session writes alone, while independent, read-only fork sessions perform cross-reviews by product, architecture, QA, security, and other roles. A visible DAG plan (stored in .umadev/plan.json) is executed step by step, with live steering via /plan—you can skip, veto, add, or reorder tasks mid-run. The system enforces 113 content governance checks and 34 formal rules (clause), with a configurable quality gate (default 90%) and two deliberate human-in-the-loop confirmation gates, including for preview and irreversible actions. UmaDev builds project memory across sessions—facts, pitfalls, validated experiences, and run notes are persisted and retrieved via local hybrid RAG (BM25 + optional local semantic + HyDE). It understands your existing codebase through repo-map (symbols and import edges) and injects only the context needed for the current task. No model API keys are held, no logins are saved; the underlying CLI uses its own models. Every delivery produces an auditable pack: an output/ directory with PRD, architecture, UI/UX, OpenAPI, execution plan, and open decisions; .umadev/audit/ with runtime-proof.json, deploy-proof.json, contract reconciliation, and security review; and a release/ handoff with review reports, scorecards, proof packs, and PR text. These map to SOC 2, ISO 27001, and EU AI Act, making compliance evidence concrete. Compared to Bolt or Lovable, UmaDev is
Behind the Verdict
UmaDev positions itself as an orchestration layer over existing CLI agents, and it delivers on that promise with unusual depth. The core idea—separating writing from review via independent read-only fork sessions—directly addresses the common failure mode where a single model both writes and validates its own output, producing self-confirming but flawed results. The visible DAG plan, stored in .umadev/plan.json, gives you real-time visibility and control: you can skip, veto, add, or reorder tasks mid-run, which is a level of steering most agent tools lack. The governance layer is a standout. With 113 content governance checks and 34 formal rules, plus a configurable quality gate (default 90%), it enforces standards that go beyond simple linting—design tokens, anti-AI-slop rules, and structured review feedback. The auditable delivery pack (output/, .umadev/audit/, release/) maps directly to SOC 2, ISO 27001, and EU AI Act, which is a critical feature for teams that need compliance evidence. However, this is not a tool for everyone. It requires you to have a logged-in CLI agent already installed, and it doesn't provide models or API keys. The full 10-stage pipeline is heavy for small tasks, though the mode routing (Chat, Explain, QuickEdit, Debug, Build) mitigates that. The setup process has some gotchas (npm permissions, sudo issues), and the TUI is a learning curve for those used to IDE plugins. Where it fits: solo developers and small teams who already use Claude Code, Codex, OpenCode, Grok Build, or Kimi Code and want structured, governed workflows with audit trails. Where it doesn't: users seeking a zero-review autonomous agent or a cloud-hosted managed service. If you prefer rapid visual prototyping with minimal process, tools like Bolt or Lovable will be more direct. Recent updates (v1.0.67 through v1.0.73) show a strong focus on hardening: write intent no longer misclassified as read-only, permission bypasses fixed, review failures bounded, and the release chain verified. This continuous improvement makes UmaDev a reliable, if complex, addition to an AI-assisted development stack.
Researching umadev? Get your full AI stack in 60 seconds.
Free, no signup — tell us your goal and get tools matched to your budget & existing stack.
Real-world workflow fit
Concrete scenarios for the personas umadev actually fits — and what changes day-one when you adopt it.
You have an existing project and want to add a payment module with production-ready code and tests.
Outcome: You run `umadev init`, describe the task, and UmaDev routes to Build mode, generating a plan, executing it, and producing an auditable delivery pack with proof of testing and security review.
You need to deliver a client project with documentation and audit trails that map to SOC 2 or ISO 27001.
Outcome: UmaDev generates PRD, architecture, UI/UX docs, and an audit trail in .umadev/audit/, along with a scorecard.html that can be shared with clients or auditors.
You want to run governance checks in CI to prevent AI-generated anti-patterns like emoji icons and hardcoded colors.
Outcome: You use UmaDev as an MCP server in CI to run 113 governance checks and 34 formal rules automatically, catching violations before merge.
Use Cases
- Rapidly prototype a booking system with a single prompt and get production-grade code with tests
- Generate an auditable delivery package for a client project, including compliance mapping
- Enforce coding standards across a team by running governance rules in CI
- Automate the repetitive parts of CRUD app development while keeping human oversight at key checkpoints
- Onboard new developers by using UmaDev's knowledge base and structured documentation outputs
Limitations
- UmaDev does not provide models or API keys; it relies on separately installed, logged-in local base CLIs (Claude Code, Codex, OpenCode, Grok Build, Kimi Code) which use their own models.
- The full 10-stage build pipeline is intended for substantial tasks; simpler tasks route through faster paths (Chat/Explain/QuickEdit/Debug/Build).
- Installation requires careful handling of npm permissions or use of native installers; Windows, macOS, and Linux are supported with binary distributions.
as of 2026-08-16
Verification history
We have re-verified umadev 6 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.
- — re-checked, vendor evidence unchanged
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
Free to cite with attribution — this page re-verifies continuously.
12-month cost
Project the real annual outlay, including the implied monthly cost when only an annual tier is published.
Vendor list price only. Add-on usage, seat overages, and contract minimums are surfaced under Hidden costs & gotchas.
Plans compared
For each published umadev tier: who it actually fits, and what it adds vs. the previous tier. Cross-reference the cost calculator above for projected annual outlay.
Free
$0/mo
Ideal for
Solo developers and small teams who already have a logged-in CLI agent and want governance and audit trails without extra cost.
What this tier adds
This is the only tier and is fully open-source under MIT, with all features included—no paid upgrade path.
Where the pricing makes sense
The company stage and team size where umadev's pricing actually pencils out — and where peers do it cheaper.
UmaDev is free and open-source (MIT), making it a zero-cost option compared to managed tools like Bolt or Lovable, which charge subscription fees. The real cost is the underlying CLI agents, which you may already have.
Setup time & first value
How long it actually takes to get something useful out of umadev — broken out by persona, not the marketing-page minute.
For a developer with an existing CLI agent installed, setup takes about 5 minutes: install via npm or native installer, run `umadev init`, and start a session. If you need to install a base CLI first, add 10-30 minutes depending on the provider.
Switching to or from umadev
How to bring data in from common predecessors and how to get it back out — written for the switcher, not the buyer.
- →From Bolt/Lovable: You can start using UmaDev on any existing project—no migration needed, just initialize and describe your task.
- ↗To other tools: Since UmaDev is a local CLI, you can switch back to manual development anytime; your code and plans remain on disk.
Integrations
Resources & Guides
- Documentationumadev.goder.ai
Docs · umadev
Full product docs from umadev.goder.ai
- Documentationumadev.goder.ai
Docs · umadev
Full product docs from umadev.goder.ai
- Documentationumadev.goder.ai
Docs · umadev
Full product docs from umadev.goder.ai
- Documentationumadev.goder.ai
Docs · umadev
Full product docs from umadev.goder.ai
- Documentationumadev.goder.ai
Docs · umadev
Full product docs from umadev.goder.ai
- Documentationumadev.goder.ai
Docs · umadev
Full product docs from umadev.goder.ai
Tutorials & Learning
Official links
Tools that pair well with umadev
Common stack mates teams adopt alongside umadev, with the specific reason each pairing earns its keep.
Featured Head-to-Head Comparisons
Umadev vs Bito
Bito is the right choice for engineering teams who need system-wide context across multiple repositories and deep integrations with Jira, Slack, and IDEs like Cursor. UmaDev is better for solo developers or small teams who want a free, open-source, local AI development pipeline with built-in quality gates and audit trails. If you're a large enterprise, pick Bito; if you're an individual tinkerer, pick UmaDev.
Umadev vs Cognition Ai
Choose Cognition AI if you're an enterprise team needing autonomous end-to-end engineering with a financial guarantee and cross-platform support. Choose umadev if you're a solo developer or small team wanting an open-source, audit-driven AI team that enforces quality gates and compliance — all locally for free. Both are powerful, but they serve opposite ends of the control-vs-autonomy spectrum.
Umadev vs Poolside Ai
Choose Poolside AI if you're an enterprise in a regulated industry needing on-prem, custom models with full governance. Choose umaDev if you're a solo developer or small team wanting a free, open-source, structured AI development workflow with quality gates and audit trails, running on your existing CLI tools.
Alternatives to umadev
View allBlackbox AI
Secure, high-speed AI inference and coding agents for enterprise teams.
Frequently Asked Questions
Used umadev? Help shape our editorial sentiment research.