Gentleman-Programming/gentle-ai
Gentle-AI configures the AI coding agents you already use: Claude Code, Cursor, OpenCode, Codex, Pi, and more.
About Gentleman-Programming/gentle-ai
Gentleman-Programming/gentle-ai is an open-source project on GitHub, mainly written in Go. Gentle-AI configures the AI coding agents you already use: Claude Code, Cursor, OpenCode, Codex, Pi, and more. It currently holds 6,871 stars and 752 forks with 0 open issues, and was last pushed on an unknown date (repository created unknown).
Project Overview
AI Homed tracks it on the Today's Trending board.
GitHub Repository Details
README
Gentle-AI™
The deterministic engineering environment for the AI agent you already use.
Website • Quickstart • Docs • Wiki
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.
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
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.
---
ODD — The everyday workflow
Organic Driven Development (ODD) is the recommended path for everyday work: explore the existing code, clarify real decisions, implement authorized changes, and run proportionate checks. Ask for an outcome, for example: "Add CSV export using the existing report filters." Small changes stay lightweight; substantial work keeps one recoverable feature document, not a mandatory phase pipeline.
That document, odd/tasks/.md, combines intent, scope, checklist, evidence, next step, and concise rationale for meaningful accepted changes. Engram mirrors the full document under project-scoped odd//tasks; accepted changes revise affected tasks while preserving valid completed work. TDD follows configured mode and runner, not the mere presence of tests. RDD is a separate, user-owned review choice.
Why not SDD every day? Its proposal/spec/design/tasks artifacts and phase handoffs add coordination that ordinary work often does not need. Choose SDD explicitly when you want those formal artifacts; size, ambiguity, and risk alone do not select it. SDD remains supported, not deprecated.
---
SDD — Formal phases when you choose them
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, and Verify checks implementation evidence against the specification. TDD is also available in ODD; it does not require an SDD phase.
---
RDD — Check finished work at the right depth
Receipt-Driven Development (RDD) is opt-in and stays off until you enable it. 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.
---
Deterministic by design — Know the next valid step
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.
---
Gentle Shell — A complete workspace for Pi
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.
---
16 agents — Keep the agent you already use
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.
---
Also in the box
| Component | What it does |
| :--- | :--- |
| Skills library | Loaded automatically when the task matches |
| Context7 MCP | Optional, selectable live framework and library documentation |
| CodeGraph | Read-only symbol graph of your codebase |
| Security deny-list | Blocks ~/.ssh, .env and credential files |
| Config backups | Snapshotted before every single write |
| Doctor | gentle-ai doctor — read-only health report |
| Personas | Optional personas; Gentleman is a caring but rigorous mentor who guides you toward your goal |
| Themes | Gentleman and Gentleman-Cute |
| Per-phase model assignment | Assign 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/v2/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 go | What you'll find | | :--- | :--- | | Intended Usage | The mental model. If you read one page, read this one. | | Quickstart · Usage | Install, prerequisites, every CLI command and flag | | Agents | Feature matrix and per-agent notes for all 16 | | ODD · Routing | Everyday direct/delegated work and explicitly selected SDD | | Review · Architecture | The RDD contract, lifecycle and threat model | | Engram · Components | Memory commands, skills, presets and personas | | Contributing · Codebase Guide | Extend or contribute | | Telemetry | What 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.

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 →.
---
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.