← Discover MCPs and Agents
g
AgentAI & MLGitHub

gentle-ai

Gentle-AI configures the AI coding agents you already use: Claude Code, Cursor, OpenCode, Codex, Pi, and more. Choose persistent memory, Organic-Driven Development, curated skills, MCP servers, personas, and optional bounded review. Open source, no agent lock-in.

Links

README

From the repo.

Gentle-AI neon rose banner: the rose blooms in, the GENTLE-AI wordmark is written on, and the tagline Ecosystem, Framework, Workflows appears

Gentle-AI™

The deterministic engineering environment for the AI agent you already use.

Release Stars 16 agents Platform License: MIT

WebsiteQuickstartDocsWiki


Your agent writes code, then forgets everything. It has no opinion about your project, and no way to prove what it did beyond asking you to read every line. Gentle-AI gives it memory, a workflow, and evidence.


If Gentle-AI made your agent worth trusting, a star helps other people find it.

Star History Chart

WORKS WITH THE AGENT YOU ALREADY HAVE

Pi · OpenCode · Claude Code · Codex · Cursor · VS Code Copilot · Gemini CLI · Kilo Code
Kimi Code · Kiro IDE · Qwen Code · Hermes · Antigravity · Windsurf · OpenClaw · Trae

16 integrations · native configuration · compare capabilities →

Features


Engram™ — Keep your project context

Three work sessions separated by a restart and by context compaction. Each break cuts the session layer but stops at the memory layer underneath. The first session saves a decision, the next one asks memory before asking you, and weeks later the same question is answered from memory instead of by re-reading the repository.

The cost of a fresh session is not the tokens — it is you, re-explaining the same decisions every morning. Engram removes that: your agent writes down what it learns as it goes and reaches for it before it reaches for you, so context accumulates instead of resetting.

Docs →


ODD — Keep small work small

ODD authorizes and understands a request. Read-only work ends separately; authorized work stays lightweight when small or keeps a recoverable record when substantial, then is implemented, checked, and closed. SDD remains an explicit choice.

Small changes should not need a planning pipeline, and larger work should not lose its context between sessions. Organic Driven Development (ODD) keeps understood changes lightweight and gives substantial, authorized work one recoverable feature document. The agent explores before changing code, checks the results, and keeps progress current so work can resume without rebuilding the plan. Formal SDD phases remain an explicit choice.

Docs →


SDD — Formal phases when you choose them

The SDD cycle is selected only by explicit request or accepted proposal. Explore can use optional Research; Proposal, Spec, Design and Tasks create formal planning artifacts; Apply uses configured TDD. Optional Verify reports practical diagnostics, including for partial work, but does not gate Archive: a separate path leads from Apply straight to Archive when Verify is skipped. Archive records actual state and history, including unfinished work when explicitly archived. It is not shipping, approval, or RDD.

When you explicitly choose Spec-Driven Development, proposal, specification, design, and task artifacts make the plan reviewable before implementation. File-backed storage keeps them on disk; Engram-backed storage keeps them in memory. Apply follows the configured TDD mode. Research and Verify are optional: Verify can diagnose partial work and report practical findings, but it is not an archive gate. Archive records the actual state and history, including unfinished work when you explicitly archive it; it does not ship or approve the change, and SDD does not invoke RDD. TDD is also available in ODD; it does not require an SDD phase.

Docs →


RDD — Check finished work at the right depth

How RDD checks a finished change. The exact change is frozen to a lineage, revision and target, then a read-only risk assessment picks the depth: passive gets a structural readback with zero reviewer lenses, medium gets one focused lens, high gets the canonical 4R — Risk, Resilience, Readability and Reliability. At most one bounded correction is allowed, and one exact acknowledgement closes the transaction. Delivery stays human-owned.

Receipt-Driven Development (RDD) is on by default and opt-out: run gentle-ai review mode disable to turn it off. Explicit global or clone-local OFF choices remain OFF. Its point is that a review cannot drift: the candidate is frozen before anything reads it, so the evidence belongs to the exact version you are about to rely on — not to whatever the worktree looked like a moment later. The depth comes from that frozen candidate rather than from the model's judgment, and the result is informational. Commit, push and release stay your call.

Docs →


Deterministic by design — Know the next valid step

A different agent, a different model and a brand-new session all converge on the gentle-ai binary. It reads the change state from files on disk and returns the only valid next transition, so no model votes on what comes next. The answer is always one of four public states: Working, Checking, Ready, or Needs your decision.

A model that guesses the next step guesses differently tomorrow, and differently again for your teammate. That is the gap between a workflow and a suggestion. The gentle-ai binary owns native SDD status and RDD review transitions, and because it reads state from files rather than from a context window, two people on two machines get the same answer — and so does the same person a month later.

Docs →


Gentle Shell — A complete workspace for Pi

Gentle Shell running an SDD sub-agent, with the todo list and live context and spend information

The way Gentle-AI was intended. Gentle-AI brings our native Pi extensions together in one focused development environment: orchestrate specialized agents, monitor usage for supported provider accounts, and review code changes in a built-in diff.

Docs →


16 agents — Keep the agent you already use

The installer configuring multiple agents

Gentle-AI brings its shared workflow to Pi, OpenCode, Claude Code, Codex, and twelve more agents. Each integration uses that agent's native capabilities, so available features such as delegation and RDD review can differ.

Docs →


Also in the box

ComponentWhat it does
Skills libraryLoaded automatically when the task matches
Context7 MCPOptional, selectable live framework and library documentation
CodeGraphRead-only symbol graph of your codebase
Security deny-listBlocks ~/.ssh, .env and credential files
Config backupsSnapshotted before every single write
Doctorgentle-ai doctor — read-only health report
PersonasOptional personas; Gentleman is a caring but rigorous mentor who guides you toward your goal
ThemesGentleman and Gentleman-Cute
Per-phase model assignmentAssign a model to each phase in Pi and OpenCode

Every component, skill and preset: Full breakdown →

Get started

# macOS (Homebrew)
brew install gentleman-programming/tap/gentle-ai

# macOS / Linux (curl)
curl -fsSL https://raw.githubusercontent.com/Gentleman-Programming/gentle-ai/main/scripts/install.sh | bash

# Windows (PowerShell) — source install, needs Go 1.25.10+
go install github.com/gentleman-programming/gentle-ai/v3/cmd/gentle-ai@latest
gentle-ai          # pick your agents, components and persona
gentle-ai doctor   # verify — read-only, changes nothing

Then use your agent normally. Your configs are snapshotted before every write, and Gentle-AI never installs an AI agent for you — it configures what you already have.

Beta channel, signature verification and per-distro prerequisites: Quickstart →

Documentation

Where to goWhat you'll find
Intended UsageThe mental model. If you read one page, read this one.
Quickstart · UsageInstall, prerequisites, every CLI command and flag
AgentsFeature matrix and per-agent notes for all 16
ODD · RoutingEveryday direct/delegated work and explicitly selected SDD
Review · ArchitectureThe RDD contract, lifecycle and threat model
Engram · ComponentsMemory commands, skills, presets and personas
Contributing · Codebase GuideExtend or contribute
TelemetryWhat we count, and how to turn it off

Community

Everything labelled up-for-grabs is scoped, approved and unclaimed — pick one and it's yours.

Community Roadmap Contributing Guide Contributors



Gentle-AI contributors

This project exists because of these people.

Built with Gentle-AI

Shipped something with Gentle-AI? Wear the rose. Paste this into your README and the badge links back here:

<a href="https://github.com/Gentleman-Programming/gentle-ai">
  <img width="220" src="https://raw.githubusercontent.com/Gentleman-Programming/gentle-ai/main/docs/assets/brand/built-with-gentle-ai.png" alt="Built with Gentle-AI" />
</a>

Prefer plain Markdown?

[![Built with Gentle-AI](https://raw.githubusercontent.com/Gentleman-Programming/gentle-ai/main/docs/assets/brand/built-with-gentle-ai.png)](https://github.com/Gentleman-Programming/gentle-ai)

Keep the image URL exactly as shown — it is how I find and feature the projects that carry the badge.

About the author

Built by Alan Buscaglia (Gentleman Programming): 15 years of enterprise architecture, a community of thousands of developers testing these tools daily, and one rule for AI-assisted work — verifying beats generating.

Teams adopting AI and finding it isn't working — resistance, everyone prompting their own way, no shared quality bar — can reach out about engagements built on these same open-source tools →.

Website YouTube GitHub Email



Gentle-AI is crafted with Gentle-AI



License: MIT

Trademark notice: The Gentle AI™ and Engram™ names and logos are trademarks of Alan Buscaglia. Both marks are used throughout this document; the symbol appears on the first prominent mention of each, and this notice covers the rest. The MIT License applies to the code; it does not permit implying endorsement or official affiliation. See TRADEMARKS.md.

Collected info

  • 7,120 stars
  • 774 forks
  • Language: Go
  • Source updated: 9/22/2026