From 48849cada22a79daed4b68f596ff28bf7fd8864f Mon Sep 17 00:00:00 2001 From: franzer Date: Mon, 6 Jul 2026 12:09:43 -0600 Subject: [PATCH] docs: reorder and trim Key Features in README Move Key Features up beside Use Cases so the orientation content is grouped ahead of installation and usage. Trim the table to the three headline capabilities (Blame, Git-ref Sync, Cross-tool Memory); the remaining features are already covered by their dedicated sections. --- README.md | 21 ++++++++------------- 1 file changed, 8 insertions(+), 13 deletions(-) diff --git a/README.md b/README.md index a2514bd..25b5281 100644 --- a/README.md +++ b/README.md @@ -18,6 +18,14 @@ Lore records your AI coding sessions and links them to git commits. Run `lore bl - **Knowledge transfer**: AI conversations stay with the code when people leave - **Search**: Find that conversation where you solved a similar problem +## Key Features + +| Feature | Description | +|---------|-------------| +| **Blame** | Trace any line of code to the AI session that produced it | +| **Git-ref Sync** | Sync reasoning through your existing git remotes, encrypted; share by passphrase | +| **Cross-tool Memory** | Mirror one tool's project memory so any LLM can read it over MCP | + ## Installation ### Homebrew (macOS) @@ -97,19 +105,6 @@ Linked sessions (1): Let me add rate limiting to prevent brute force attacks. ``` -## Key Features - -| Feature | Description | -|---------|-------------| -| **Blame** | Trace any line of code to the AI session that produced it | -| **Git-ref Sync** | Sync reasoning through your existing git remotes, encrypted; share by passphrase | -| **Cross-tool Memory** | Mirror one tool's project memory so any LLM can read it over MCP | -| **Session Capture** | One history across 10+ AI coding tools | -| **Git Linking** | Connect sessions to commits | -| **Full-text Search** | Find any past conversation | -| **MCP Server** | Let AI tools query your history | -| **Background Daemon** | Real-time capture (optional) | - ## Sync Lore syncs reasoning history through your existing git remotes, with no server and no account. Sessions are encrypted on your machine before they touch a remote, so the git host only ever sees ciphertext.