From 75af5d315f5635a20d310bd8bebaa09f116381eb Mon Sep 17 00:00:00 2001 From: Subash Natarajan Date: Fri, 17 Jul 2026 16:57:09 +0530 Subject: [PATCH] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 568fdcc..e32858e 100644 --- a/README.md +++ b/README.md @@ -23,7 +23,7 @@ Describe your situation - `@fde` routes to the right method and writes the match ## The problem -Your AI agent's memory is scoped to a **repo**. Client work isn't: one engagement spans several repos, a dozen stakeholders, and decisions made in meetings your agent never saw. That context lives in rooms, chats, and hallway conversations - nothing writes it down where your tools can use it. +Your AI coding agent's memory is scoped to a **repo**. Client work isn't: one engagement spans several repos, a dozen stakeholders, and decisions made in meetings your agent never saw. That context lives in rooms, chats, and hallway conversations - nothing writes it down where your tools can use it. fdeops adds the missing layer: memory scoped to the **client** - plain markdown at `~/fde-engagements//.fde/`, written as a side effect of doing the work. Local only, zero dependencies, no network, no telemetry.