memoir-cli 3.2.0 → 3.2.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/LAUNCH_POSTS.md +247 -0
- package/MARKETING.md +143 -0
- package/POSTS-READY-TO-GO.md +215 -0
- package/README.md +95 -120
- package/demo.svg +201 -0
- package/landing-page-v2.html +690 -0
- package/mcp-publisher +0 -0
- package/package.json +24 -24
- package/server.json +20 -0
package/LAUNCH_POSTS.md
ADDED
|
@@ -0,0 +1,247 @@
|
|
|
1
|
+
# Memoir Launch Posts — Ready to Copy & Paste
|
|
2
|
+
|
|
3
|
+
---
|
|
4
|
+
|
|
5
|
+
## 1. Hacker News — Show HN
|
|
6
|
+
|
|
7
|
+
**Title:** Show HN: Memoir – Sync your AI coding memory across 11 tools and every device
|
|
8
|
+
|
|
9
|
+
**Text:**
|
|
10
|
+
|
|
11
|
+
I switch between a Mac and a PC daily. Every time, my Claude Code rules, Gemini instructions, Cursor settings — gone. Trapped in hidden dotfiles on whichever machine I used last.
|
|
12
|
+
|
|
13
|
+
I built memoir to fix this. It's a CLI that backs up, restores, and syncs your AI memory across devices and tools. It supports 11 tools: Claude Code, Gemini CLI, ChatGPT, OpenAI Codex, Cursor, GitHub Copilot, Windsurf, Zed, Cline, Continue.dev, and Aider.
|
|
14
|
+
|
|
15
|
+
```
|
|
16
|
+
memoir push # back up everything — AI configs, projects, session state
|
|
17
|
+
memoir restore # restore on any machine — AI picks up mid-conversation
|
|
18
|
+
```
|
|
19
|
+
|
|
20
|
+
What makes it different from dotfile managers:
|
|
21
|
+
|
|
22
|
+
1. **AI-aware translation.** `memoir migrate --from claude --to cursor` uses AI to rewrite your instructions following each tool's conventions — not just file copy.
|
|
23
|
+
|
|
24
|
+
2. **Session handoff.** memoir captures what you were doing (files changed, errors hit, decisions made) and injects it on restore so your AI picks up mid-conversation.
|
|
25
|
+
|
|
26
|
+
3. **Workspace sync.** Git repos are auto-cloned, non-git projects are bundled, and uncommitted changes are saved as patches and reapplied.
|
|
27
|
+
|
|
28
|
+
4. **MCP server.** `memoir mcp` gives your editor 6 tools to search, read, and save memories without leaving the conversation.
|
|
29
|
+
|
|
30
|
+
5. **E2E encrypted.** AES-256-GCM. Secret scanning auto-redacts API keys and tokens before sync. Zero-knowledge — we can't read your data.
|
|
31
|
+
|
|
32
|
+
It syncs three layers no other tool connects: AI memory (configs + instructions), session state (what you were doing), and workspace (your actual projects).
|
|
33
|
+
|
|
34
|
+
```
|
|
35
|
+
npm install -g memoir-cli
|
|
36
|
+
```
|
|
37
|
+
|
|
38
|
+
~100kb installed. MIT licensed. Cloud sync available (free tier: 3 backups). Would love feedback — especially on what workflows you'd want next. Thinking about shareable context links so you can onboard a teammate with one URL.
|
|
39
|
+
|
|
40
|
+
https://github.com/camgitt/memoir
|
|
41
|
+
|
|
42
|
+
---
|
|
43
|
+
|
|
44
|
+
## 2. Reddit — r/programming
|
|
45
|
+
|
|
46
|
+
**Title:** I built a CLI that syncs your AI coding memory across 11 tools and every device
|
|
47
|
+
|
|
48
|
+
**Body:**
|
|
49
|
+
|
|
50
|
+
Every AI coding tool stores your preferences in its own hidden config files. Claude has `~/.claude/` and `CLAUDE.md`. Cursor has `.cursorrules`. Gemini has `GEMINI.md`. None of them talk to each other, and none of them sync between machines.
|
|
51
|
+
|
|
52
|
+
I got tired of re-teaching my AI tools every time I switched from my Mac to my PC, so I built **memoir** — a CLI that backs up, restores, and translates your AI memory across devices and tools.
|
|
53
|
+
|
|
54
|
+
**What it does:**
|
|
55
|
+
|
|
56
|
+
- `memoir push` — backs up AI configs, project knowledge, and your current coding session
|
|
57
|
+
- `memoir restore` — restores everything on any machine (Mac, Windows, Linux)
|
|
58
|
+
- `memoir migrate --from claude --to cursor` — AI-powered translation between tools (rewrites conventions, doesn't just copy files)
|
|
59
|
+
- `memoir mcp` — MCP server so your editor can search/save memories in-conversation
|
|
60
|
+
|
|
61
|
+
**What makes it interesting:**
|
|
62
|
+
|
|
63
|
+
It doesn't just sync config files. It captures *session state* — what files you changed, what decisions you made, what you were debugging — and injects that context when you restore. Your AI literally picks up where you left off.
|
|
64
|
+
|
|
65
|
+
It also syncs your actual workspace: git repos are auto-cloned, non-git projects are bundled and unpacked, uncommitted changes are saved as patches.
|
|
66
|
+
|
|
67
|
+
E2E encrypted (AES-256-GCM), secret scanning built in, MIT licensed.
|
|
68
|
+
|
|
69
|
+
```
|
|
70
|
+
npm install -g memoir-cli
|
|
71
|
+
```
|
|
72
|
+
|
|
73
|
+
GitHub: https://github.com/camgitt/memoir
|
|
74
|
+
Website: https://memoir.sh
|
|
75
|
+
|
|
76
|
+
Would love to hear what workflows people would find useful. Currently thinking about shareable context links for team onboarding.
|
|
77
|
+
|
|
78
|
+
---
|
|
79
|
+
|
|
80
|
+
## 3. Reddit — r/cursor
|
|
81
|
+
|
|
82
|
+
**Title:** Sync your .cursorrules and AI context across machines (and 10 other AI tools)
|
|
83
|
+
|
|
84
|
+
**Body:**
|
|
85
|
+
|
|
86
|
+
Quick question for multi-machine Cursor users — how are you keeping your `.cursorrules` and settings in sync across devices?
|
|
87
|
+
|
|
88
|
+
I built **memoir** because I kept losing my AI context switching between machines. It's a CLI that syncs Cursor configs alongside 10 other AI tools — Claude Code, Gemini CLI, ChatGPT, Codex, Copilot, Windsurf, Zed, Cline, Continue.dev, and Aider. 11 tools total.
|
|
89
|
+
|
|
90
|
+
The part that's been most useful for me:
|
|
91
|
+
|
|
92
|
+
```
|
|
93
|
+
memoir migrate --from claude --to cursor
|
|
94
|
+
```
|
|
95
|
+
|
|
96
|
+
This uses AI to actually *translate* your Claude CLAUDE.md into a proper `.cursorrules` that follows Cursor's conventions. Not a file copy — a real rewrite.
|
|
97
|
+
|
|
98
|
+
It also captures your current coding session and lets you resume on another machine. Your AI picks up mid-conversation.
|
|
99
|
+
|
|
100
|
+
```
|
|
101
|
+
npm install -g memoir-cli
|
|
102
|
+
memoir init
|
|
103
|
+
memoir push # backs up .cursorrules + settings + projects
|
|
104
|
+
memoir restore # restores everything on another machine
|
|
105
|
+
```
|
|
106
|
+
|
|
107
|
+
E2E encrypted, MIT licensed, free tier available.
|
|
108
|
+
|
|
109
|
+
GitHub: https://github.com/camgitt/memoir
|
|
110
|
+
|
|
111
|
+
What other Cursor-specific workflows would be useful? Happy to add things.
|
|
112
|
+
|
|
113
|
+
---
|
|
114
|
+
|
|
115
|
+
## 4. Reddit — r/neovim
|
|
116
|
+
|
|
117
|
+
**Title:** memoir — sync your AI coding context (Aider, Cline, Continue.dev) across machines from the terminal
|
|
118
|
+
|
|
119
|
+
**Body:**
|
|
120
|
+
|
|
121
|
+
For terminal-first devs using AI tools alongside Neovim — I built a CLI that syncs your AI memory across machines and tools.
|
|
122
|
+
|
|
123
|
+
If you're using Aider, Cline, or Continue.dev, you've probably got config files and project instructions scattered across `~/.aider.conf.yml`, `.clinerules`, `.continuerules`, etc. memoir backs all of that up and restores it on any machine.
|
|
124
|
+
|
|
125
|
+
```
|
|
126
|
+
memoir push # backs up AI configs + projects + session state
|
|
127
|
+
memoir restore # restores on any machine
|
|
128
|
+
memoir migrate --from aider --to cline # AI-powered translation
|
|
129
|
+
```
|
|
130
|
+
|
|
131
|
+
It also ships an MCP server (`memoir mcp`) that gives your tools 6 commands to search, read, and save memories without leaving your workflow.
|
|
132
|
+
|
|
133
|
+
The workspace sync is nice too — git repos auto-clone, non-git projects get bundled, uncommitted changes are saved as patches and reapplied.
|
|
134
|
+
|
|
135
|
+
Everything's E2E encrypted (AES-256-GCM) with secret scanning. MIT licensed.
|
|
136
|
+
|
|
137
|
+
```
|
|
138
|
+
npm install -g memoir-cli
|
|
139
|
+
```
|
|
140
|
+
|
|
141
|
+
https://github.com/camgitt/memoir
|
|
142
|
+
|
|
143
|
+
Would love feedback from the terminal crowd. What AI tool integrations would you want to see next?
|
|
144
|
+
|
|
145
|
+
---
|
|
146
|
+
|
|
147
|
+
## 5. X/Twitter Launch Thread
|
|
148
|
+
|
|
149
|
+
**Tweet 1 (hook):**
|
|
150
|
+
AI tools forget you every time you switch machines.
|
|
151
|
+
|
|
152
|
+
I built memoir — a CLI that syncs your AI memory across 11 tools and every device.
|
|
153
|
+
|
|
154
|
+
One command to save. One command to restore. Your AI picks up mid-conversation.
|
|
155
|
+
|
|
156
|
+
Here's what it does 🧵
|
|
157
|
+
|
|
158
|
+
**Tweet 2:**
|
|
159
|
+
The problem: Claude has CLAUDE.md. Cursor has .cursorrules. Gemini has GEMINI.md.
|
|
160
|
+
|
|
161
|
+
None of them sync. None of them talk to each other.
|
|
162
|
+
|
|
163
|
+
Switch machines? Start from zero. Switch tools? Re-teach everything.
|
|
164
|
+
|
|
165
|
+
memoir fixes this.
|
|
166
|
+
|
|
167
|
+
**Tweet 3:**
|
|
168
|
+
```
|
|
169
|
+
memoir push # save everything
|
|
170
|
+
memoir restore # restore anywhere
|
|
171
|
+
```
|
|
172
|
+
|
|
173
|
+
It syncs three layers:
|
|
174
|
+
→ AI memory (configs across 11 tools)
|
|
175
|
+
→ Session state (what you were doing)
|
|
176
|
+
→ Workspace (your actual projects)
|
|
177
|
+
|
|
178
|
+
**Tweet 4:**
|
|
179
|
+
The killer feature: AI-powered translation between tools.
|
|
180
|
+
|
|
181
|
+
```
|
|
182
|
+
memoir migrate --from claude --to cursor
|
|
183
|
+
```
|
|
184
|
+
|
|
185
|
+
This doesn't just copy files. It rewrites your Claude instructions into proper .cursorrules following Cursor's conventions.
|
|
186
|
+
|
|
187
|
+
Works between all 11 tools.
|
|
188
|
+
|
|
189
|
+
**Tweet 5:**
|
|
190
|
+
Session handoff is the other thing nothing else does.
|
|
191
|
+
|
|
192
|
+
memoir captures what files you changed, what decisions you made, what you were debugging.
|
|
193
|
+
|
|
194
|
+
On restore, it injects that context. Your AI literally picks up where you left off.
|
|
195
|
+
|
|
196
|
+
**Tweet 6:**
|
|
197
|
+
Security:
|
|
198
|
+
→ E2E encrypted (AES-256-GCM)
|
|
199
|
+
→ Secret scanning catches API keys, tokens, passwords
|
|
200
|
+
→ Auto-redacted before sync
|
|
201
|
+
→ Zero-knowledge — we can't read your data
|
|
202
|
+
|
|
203
|
+
**Tweet 7:**
|
|
204
|
+
```
|
|
205
|
+
npm install -g memoir-cli
|
|
206
|
+
```
|
|
207
|
+
|
|
208
|
+
Free & open source. MIT licensed. ~100kb.
|
|
209
|
+
|
|
210
|
+
Cloud sync available. MCP server included so your editor can search memories in-conversation.
|
|
211
|
+
|
|
212
|
+
GitHub: github.com/camgitt/memoir
|
|
213
|
+
Website: memoir.sh
|
|
214
|
+
|
|
215
|
+
Try it and let me know what you think ↓
|
|
216
|
+
|
|
217
|
+
---
|
|
218
|
+
|
|
219
|
+
## Posting Strategy
|
|
220
|
+
|
|
221
|
+
### Timing
|
|
222
|
+
- **Hacker News:** Tuesday or Wednesday, 8-9am ET (peak HN traffic)
|
|
223
|
+
- **Reddit r/programming:** Same day as HN, 2-3 hours after
|
|
224
|
+
- **Reddit r/cursor:** Day after HN post
|
|
225
|
+
- **Reddit r/neovim:** Day after HN post (different audience, won't cannibalize)
|
|
226
|
+
- **X/Twitter thread:** Same day as HN, post in the morning, then reply-thread throughout the day
|
|
227
|
+
|
|
228
|
+
### Engagement Rules
|
|
229
|
+
1. **Reply to every comment** within the first 2 hours — HN and Reddit rank by early engagement
|
|
230
|
+
2. **Don't be defensive** — if someone says "this is just dotfiles," acknowledge it and explain the session handoff + translation layer
|
|
231
|
+
3. **Ask questions back** — "What tools are you using?" and "What would you want synced?" drives comments
|
|
232
|
+
4. **Have a demo GIF ready** — link to your demo.gif in early replies
|
|
233
|
+
5. **Upvote timing** — ask 2-3 friends to upvote within the first 30 minutes (critical for HN front page)
|
|
234
|
+
|
|
235
|
+
### Expected Objections & Responses
|
|
236
|
+
|
|
237
|
+
**"This is just a dotfiles manager"**
|
|
238
|
+
→ "Dotfiles managers sync files. memoir syncs AI context — it captures your session state (what you were debugging, what decisions you made) and injects it on restore. It also translates between tools using AI, not file copy. The workspace sync with uncommitted patches is a layer above dotfiles too."
|
|
239
|
+
|
|
240
|
+
**"Why not just use git?"**
|
|
241
|
+
→ "Git syncs code. memoir syncs the AI layer on top of it — your CLAUDE.md, .cursorrules, session context, and tool configs. Plus it handles non-git projects (bundles them), and saves uncommitted work as patches. It's the layer between your code and your AI."
|
|
242
|
+
|
|
243
|
+
**"I don't use multiple machines"**
|
|
244
|
+
→ "Fair — but do you use multiple AI tools? `memoir migrate` translates your context between them. And the MCP server is useful on a single machine for searching across all your AI memories."
|
|
245
|
+
|
|
246
|
+
**"Security concerns with syncing AI configs"**
|
|
247
|
+
→ "E2E encrypted before it leaves your machine (AES-256-GCM). Built-in secret scanner catches API keys, tokens, passwords — auto-redacted. Zero-knowledge architecture. Run `memoir doctor` to see exactly what gets synced."
|
package/MARKETING.md
ADDED
|
@@ -0,0 +1,143 @@
|
|
|
1
|
+
# memoir Marketing Plan
|
|
2
|
+
|
|
3
|
+
## Key Metric
|
|
4
|
+
Weekly active `memoir_recall` calls. Not installs, not stars, not waitlist. If AI tools are calling memoir_recall regularly, the product is working.
|
|
5
|
+
|
|
6
|
+
---
|
|
7
|
+
|
|
8
|
+
## Phase 1: Directory Listings (Week 1)
|
|
9
|
+
|
|
10
|
+
### 1. awesome-mcp-servers PR
|
|
11
|
+
**Repo:** https://github.com/punkpeye/awesome-mcp-servers (or appcypher)
|
|
12
|
+
**PR title:** Add Memoir to Development Tools
|
|
13
|
+
**Line to add** (alphabetical, between Mastra and Maven):
|
|
14
|
+
```
|
|
15
|
+
- [Memoir](https://github.com/camgitt/memoir) - Persistent memory for AI coding tools via MCP. Your AI remembers across sessions, tools, and machines
|
|
16
|
+
```
|
|
17
|
+
|
|
18
|
+
### 2. mcp.so Submission
|
|
19
|
+
**Submit:** https://github.com/chatmcp/mcpso/issues/new
|
|
20
|
+
**Title:** Add Memoir — persistent memory MCP server for AI coding tools
|
|
21
|
+
**Body:**
|
|
22
|
+
|
|
23
|
+
```
|
|
24
|
+
## Server Info
|
|
25
|
+
- **Name:** memoir-cli
|
|
26
|
+
- **Repository:** https://github.com/camgitt/memoir
|
|
27
|
+
- **npm:** https://www.npmjs.com/package/memoir-cli
|
|
28
|
+
- **Website:** https://memoir.sh
|
|
29
|
+
- **Author:** camgitt
|
|
30
|
+
- **License:** MIT
|
|
31
|
+
- **Language:** JavaScript (ESM)
|
|
32
|
+
- **Transport:** stdio
|
|
33
|
+
|
|
34
|
+
## Description
|
|
35
|
+
MCP server that gives AI coding tools persistent memory across sessions. Your AI can search, read, and save memories automatically. Works with Claude Code, Cursor, Windsurf, and any MCP-compatible client.
|
|
36
|
+
|
|
37
|
+
## MCP Tools
|
|
38
|
+
| Tool | Description |
|
|
39
|
+
|------|-------------|
|
|
40
|
+
| `memoir_recall` | Search across all AI memories |
|
|
41
|
+
| `memoir_remember` | Save context for future sessions |
|
|
42
|
+
| `memoir_read` | Read a specific memory file |
|
|
43
|
+
| `memoir_list` | List all memory files by tool |
|
|
44
|
+
| `memoir_status` | Show detected AI tools |
|
|
45
|
+
| `memoir_profiles` | Switch work/personal profiles |
|
|
46
|
+
|
|
47
|
+
## Installation
|
|
48
|
+
npm install -g memoir-cli
|
|
49
|
+
|
|
50
|
+
## Client Setup
|
|
51
|
+
Add to ~/.mcp.json:
|
|
52
|
+
{ "mcpServers": { "memoir": { "command": "memoir-mcp" } } }
|
|
53
|
+
|
|
54
|
+
## Tags
|
|
55
|
+
memory, mcp, ai-tools, developer-tools, persistent-context, cli, claude, cursor
|
|
56
|
+
```
|
|
57
|
+
|
|
58
|
+
### 3. PulseMCP
|
|
59
|
+
**Submit:** https://www.pulsemcp.com/submit
|
|
60
|
+
Fill in: name, GitHub URL, npm URL, description.
|
|
61
|
+
|
|
62
|
+
### 4. Smithery.ai
|
|
63
|
+
```bash
|
|
64
|
+
npx smithery auth login
|
|
65
|
+
npx smithery mcp publish "https://github.com/camgitt/memoir" -n @camgitt/memoir
|
|
66
|
+
```
|
|
67
|
+
|
|
68
|
+
### 5. Official MCP Registry
|
|
69
|
+
Requires adding `mcpName` to package.json and using mcp-publisher CLI.
|
|
70
|
+
```bash
|
|
71
|
+
npx @anthropic/mcp-publisher init
|
|
72
|
+
npx @anthropic/mcp-publisher publish
|
|
73
|
+
```
|
|
74
|
+
|
|
75
|
+
---
|
|
76
|
+
|
|
77
|
+
## Phase 2: Launch Posts (Week 1-2)
|
|
78
|
+
|
|
79
|
+
### Show HN
|
|
80
|
+
See SHOW_HN.md. Post Tuesday or Wednesday 8-10am ET.
|
|
81
|
+
|
|
82
|
+
### Reddit Posts (1 per sub, spread across 3 days)
|
|
83
|
+
|
|
84
|
+
**r/ClaudeAI:**
|
|
85
|
+
Title: I built an MCP server that gives Claude long-term memory across sessions
|
|
86
|
+
Body: "Got tired of re-explaining my project to Claude every conversation. Built an MCP server called memoir that lets Claude search and save memories automatically. Tell it your auth setup once — it remembers next week. Free, open source, MIT licensed. Works with Cursor and 9 other tools too. https://github.com/camgitt/memoir Would love feedback."
|
|
87
|
+
|
|
88
|
+
**r/cursor:**
|
|
89
|
+
Title: MCP server that syncs your project context between Cursor, Claude Code, and other tools
|
|
90
|
+
Body: "Built memoir — an MCP server that gives your AI tools shared memory. You explain something in Cursor, and Claude Code knows it too. Also handles migrating your .cursorrules to other tools. Free CLI, MIT licensed. https://github.com/camgitt/memoir"
|
|
91
|
+
|
|
92
|
+
**r/ChatGPTCoding:**
|
|
93
|
+
Title: Open source tool that gives AI coding tools persistent memory (works with 11 tools)
|
|
94
|
+
Body: "memoir is an MCP server + CLI that syncs your AI memory across Claude, Cursor, ChatGPT, Gemini, and 7 more tools. Your AI remembers your codebase across sessions. Also backs up all your AI configs and restores them on a new machine in 60 seconds. https://memoir.sh"
|
|
95
|
+
|
|
96
|
+
---
|
|
97
|
+
|
|
98
|
+
## Phase 3: Social + Content (Week 2-3)
|
|
99
|
+
|
|
100
|
+
### X/Twitter Clips
|
|
101
|
+
- 15-sec screen recording: memoir_recall in Claude Code
|
|
102
|
+
- 15-sec screen recording: memoir migrate from Cursor to Claude
|
|
103
|
+
- 15-sec screen recording: memoir restore on a fresh machine
|
|
104
|
+
- Post across AlgoThesis + personal accounts
|
|
105
|
+
|
|
106
|
+
### Blog Post
|
|
107
|
+
Title: "How MCP Gives Your AI Tools Persistent Memory"
|
|
108
|
+
Target keywords: "MCP memory server", "Claude Code memory", "AI coding context"
|
|
109
|
+
Publish on memoir.sh/blog, cross-post to dev.to
|
|
110
|
+
|
|
111
|
+
---
|
|
112
|
+
|
|
113
|
+
## Phase 4: First 10 Users (Week 2-3)
|
|
114
|
+
|
|
115
|
+
### Discord Communities
|
|
116
|
+
- Claude Code official Discord
|
|
117
|
+
- Cursor community Discord
|
|
118
|
+
- AI/ML Discord servers
|
|
119
|
+
- Don't promote — ask for feedback: "Building an MCP memory layer, would love testers"
|
|
120
|
+
|
|
121
|
+
### Direct Outreach
|
|
122
|
+
- Find people complaining about AI context loss on Twitter/Reddit
|
|
123
|
+
- Reply with genuine help, mention memoir if relevant
|
|
124
|
+
- Not spammy — just useful
|
|
125
|
+
|
|
126
|
+
---
|
|
127
|
+
|
|
128
|
+
## NOT Doing Yet
|
|
129
|
+
- Stripe/payments (need users first)
|
|
130
|
+
- Product Hunt (low conversion for CLI tools)
|
|
131
|
+
- Teams tier (need solo users first)
|
|
132
|
+
- Paid ads (premature)
|
|
133
|
+
- Conference talks (too early)
|
|
134
|
+
|
|
135
|
+
---
|
|
136
|
+
|
|
137
|
+
## Timeline
|
|
138
|
+
| Week | Focus | Goal |
|
|
139
|
+
|------|-------|------|
|
|
140
|
+
| 1 | Directory listings + Show HN | Listed in 5+ directories, 50+ stars |
|
|
141
|
+
| 2 | Reddit + Discord + X clips | 10 active users |
|
|
142
|
+
| 3 | Blog post + iterate on feedback | 25 active users, first feature from user feedback |
|
|
143
|
+
| 4 | Repeat what worked, double down | 50+ weekly memoir_recall calls |
|
|
@@ -0,0 +1,215 @@
|
|
|
1
|
+
# Ready-to-Post Social Media — Copy & Paste Now
|
|
2
|
+
|
|
3
|
+
Post these THIS WEEK. Don't wait for perfection.
|
|
4
|
+
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
## 1. Reddit r/programming — POST TODAY
|
|
8
|
+
|
|
9
|
+
**URL:** https://www.reddit.com/r/programming/submit
|
|
10
|
+
|
|
11
|
+
**Title:** I built a CLI that syncs your AI coding memory across 11 tools and every device
|
|
12
|
+
|
|
13
|
+
**Body:**
|
|
14
|
+
|
|
15
|
+
Every AI coding tool stores your preferences in its own hidden config files. Claude has `~/.claude/` and `CLAUDE.md`. Cursor has `.cursorrules`. Gemini has `GEMINI.md`. None of them talk to each other, and none of them sync between machines.
|
|
16
|
+
|
|
17
|
+
I got tired of re-teaching my AI tools every time I switched from my Mac to my PC, so I built **memoir** — a CLI that backs up, restores, and translates your AI memory across devices and tools.
|
|
18
|
+
|
|
19
|
+
**What it does:**
|
|
20
|
+
|
|
21
|
+
- `memoir push` — backs up AI configs, project knowledge, and your current coding session
|
|
22
|
+
- `memoir restore` — restores everything on any machine (Mac, Windows, Linux)
|
|
23
|
+
- `memoir migrate --from claude --to cursor` — AI-powered translation between tools (rewrites conventions, doesn't just copy files)
|
|
24
|
+
- `memoir mcp` — MCP server so your editor can search/save memories in-conversation
|
|
25
|
+
|
|
26
|
+
**What makes it interesting:**
|
|
27
|
+
|
|
28
|
+
It doesn't just sync config files. It captures *session state* — what files you changed, what decisions you made, what you were debugging — and injects that context when you restore. Your AI literally picks up where you left off.
|
|
29
|
+
|
|
30
|
+
It also syncs your actual workspace: git repos are auto-cloned, non-git projects are bundled and unpacked, uncommitted changes are saved as patches.
|
|
31
|
+
|
|
32
|
+
E2E encrypted (AES-256-GCM), secret scanning built in, MIT licensed.
|
|
33
|
+
|
|
34
|
+
```
|
|
35
|
+
npm install -g memoir-cli
|
|
36
|
+
```
|
|
37
|
+
|
|
38
|
+
GitHub: https://github.com/camgitt/memoir
|
|
39
|
+
Website: https://memoir.sh
|
|
40
|
+
|
|
41
|
+
Would love to hear what workflows people would find useful. Currently thinking about shareable context links for team onboarding.
|
|
42
|
+
|
|
43
|
+
---
|
|
44
|
+
|
|
45
|
+
## 2. Reddit r/cursor — POST TOMORROW
|
|
46
|
+
|
|
47
|
+
**URL:** https://www.reddit.com/r/cursor/submit
|
|
48
|
+
|
|
49
|
+
**Title:** Sync your .cursorrules and AI context across machines (and 10 other AI tools)
|
|
50
|
+
|
|
51
|
+
**Body:**
|
|
52
|
+
|
|
53
|
+
Quick question for multi-machine Cursor users — how are you keeping your `.cursorrules` and settings in sync across devices?
|
|
54
|
+
|
|
55
|
+
I built **memoir** because I kept losing my AI context switching between machines. It's a CLI that syncs Cursor configs alongside 10 other AI tools — Claude Code, Gemini CLI, ChatGPT, Codex, Copilot, Windsurf, Zed, Cline, Continue.dev, and Aider. 11 tools total.
|
|
56
|
+
|
|
57
|
+
The part that's been most useful for me:
|
|
58
|
+
|
|
59
|
+
```
|
|
60
|
+
memoir migrate --from claude --to cursor
|
|
61
|
+
```
|
|
62
|
+
|
|
63
|
+
This uses AI to actually *translate* your Claude CLAUDE.md into a proper `.cursorrules` that follows Cursor's conventions. Not a file copy — a real rewrite.
|
|
64
|
+
|
|
65
|
+
It also captures your current coding session and lets you resume on another machine. Your AI picks up mid-conversation.
|
|
66
|
+
|
|
67
|
+
```
|
|
68
|
+
npm install -g memoir-cli
|
|
69
|
+
memoir init
|
|
70
|
+
memoir push # backs up .cursorrules + settings + projects
|
|
71
|
+
memoir restore # restores everything on another machine
|
|
72
|
+
```
|
|
73
|
+
|
|
74
|
+
E2E encrypted, MIT licensed, free tier available.
|
|
75
|
+
|
|
76
|
+
GitHub: https://github.com/camgitt/memoir
|
|
77
|
+
|
|
78
|
+
What other Cursor-specific workflows would be useful? Happy to add things.
|
|
79
|
+
|
|
80
|
+
---
|
|
81
|
+
|
|
82
|
+
## 3. Reddit r/ClaudeAI — POST DAY AFTER
|
|
83
|
+
|
|
84
|
+
**URL:** https://www.reddit.com/r/ClaudeAI/submit
|
|
85
|
+
|
|
86
|
+
**Title:** Built a CLI to sync your CLAUDE.md and Claude Code memory across machines
|
|
87
|
+
|
|
88
|
+
**Body:**
|
|
89
|
+
|
|
90
|
+
For those of you using Claude Code on multiple machines — how are you keeping your CLAUDE.md files and ~/.claude/ settings in sync?
|
|
91
|
+
|
|
92
|
+
I built **memoir** to solve this. It's a CLI that backs up and restores your Claude Code memory (plus 10 other AI tools) across any machine.
|
|
93
|
+
|
|
94
|
+
```
|
|
95
|
+
memoir push # backs up ~/.claude/, CLAUDE.md files, session state, projects
|
|
96
|
+
memoir restore # restores everything on another machine
|
|
97
|
+
```
|
|
98
|
+
|
|
99
|
+
The part I find most useful: **session handoff**. memoir captures what you were working on — files changed, errors hit, decisions made — and injects that context when you restore. Claude literally picks up where you left off on a different machine.
|
|
100
|
+
|
|
101
|
+
It also does AI-powered translation if you use multiple tools:
|
|
102
|
+
|
|
103
|
+
```
|
|
104
|
+
memoir migrate --from claude --to cursor
|
|
105
|
+
# Rewrites your CLAUDE.md into proper .cursorrules
|
|
106
|
+
```
|
|
107
|
+
|
|
108
|
+
And it ships an MCP server (`memoir mcp`) with 6 tools your editor can use to search and save memories in-conversation.
|
|
109
|
+
|
|
110
|
+
E2E encrypted, secret scanning built in, MIT licensed, ~100kb installed.
|
|
111
|
+
|
|
112
|
+
```
|
|
113
|
+
npm install -g memoir-cli
|
|
114
|
+
```
|
|
115
|
+
|
|
116
|
+
GitHub: https://github.com/camgitt/memoir
|
|
117
|
+
Website: https://memoir.sh
|
|
118
|
+
|
|
119
|
+
Would love feedback from the Claude community. What would make this more useful for your workflow?
|
|
120
|
+
|
|
121
|
+
---
|
|
122
|
+
|
|
123
|
+
## 4. X/Twitter Thread — POST SAME DAY AS REDDIT
|
|
124
|
+
|
|
125
|
+
Copy each tweet as a separate post in a thread:
|
|
126
|
+
|
|
127
|
+
**Tweet 1:**
|
|
128
|
+
AI tools forget you every time you switch machines.
|
|
129
|
+
|
|
130
|
+
I built memoir — a CLI that syncs your AI memory across 11 tools and every device.
|
|
131
|
+
|
|
132
|
+
One command to save. One command to restore. Your AI picks up mid-conversation.
|
|
133
|
+
|
|
134
|
+
Here's what it does:
|
|
135
|
+
|
|
136
|
+
**Tweet 2:**
|
|
137
|
+
The problem: Claude has CLAUDE.md. Cursor has .cursorrules. Gemini has GEMINI.md.
|
|
138
|
+
|
|
139
|
+
None of them sync. None of them talk to each other.
|
|
140
|
+
|
|
141
|
+
Switch machines? Start from zero. Switch tools? Re-teach everything.
|
|
142
|
+
|
|
143
|
+
memoir fixes this.
|
|
144
|
+
|
|
145
|
+
**Tweet 3:**
|
|
146
|
+
memoir push # save everything
|
|
147
|
+
memoir restore # restore anywhere
|
|
148
|
+
|
|
149
|
+
It syncs three layers:
|
|
150
|
+
- AI memory (configs across 11 tools)
|
|
151
|
+
- Session state (what you were doing)
|
|
152
|
+
- Workspace (your actual projects)
|
|
153
|
+
|
|
154
|
+
**Tweet 4:**
|
|
155
|
+
The killer feature: AI-powered translation between tools.
|
|
156
|
+
|
|
157
|
+
memoir migrate --from claude --to cursor
|
|
158
|
+
|
|
159
|
+
This doesn't just copy files. It rewrites your Claude instructions into proper .cursorrules following Cursor's conventions.
|
|
160
|
+
|
|
161
|
+
Works between all 11 tools.
|
|
162
|
+
|
|
163
|
+
**Tweet 5:**
|
|
164
|
+
Session handoff is the other thing nothing else does.
|
|
165
|
+
|
|
166
|
+
memoir captures what files you changed, what decisions you made, what you were debugging.
|
|
167
|
+
|
|
168
|
+
On restore, it injects that context. Your AI literally picks up where you left off.
|
|
169
|
+
|
|
170
|
+
**Tweet 6:**
|
|
171
|
+
npm install -g memoir-cli
|
|
172
|
+
|
|
173
|
+
Free & open source. MIT licensed. ~100kb.
|
|
174
|
+
|
|
175
|
+
Cloud sync available. MCP server included so your editor can search memories in-conversation.
|
|
176
|
+
|
|
177
|
+
GitHub: github.com/camgitt/memoir
|
|
178
|
+
Website: memoir.sh
|
|
179
|
+
|
|
180
|
+
Try it and let me know what you think
|
|
181
|
+
|
|
182
|
+
---
|
|
183
|
+
|
|
184
|
+
## 5. Cold DM Template (for devs tweeting about AI context loss)
|
|
185
|
+
|
|
186
|
+
**Search Twitter for:** "lost my cursorrules" OR "claude forgot" OR "new machine setup" OR "re-teaching AI" OR "CLAUDE.md sync"
|
|
187
|
+
|
|
188
|
+
**DM template:**
|
|
189
|
+
|
|
190
|
+
Hey! Saw your tweet about [specific pain point]. I built an open-source CLI called memoir that solves exactly this — it syncs your AI memory (CLAUDE.md, .cursorrules, etc.) across machines and tools.
|
|
191
|
+
|
|
192
|
+
One command to back up, one to restore. Your AI picks up mid-conversation.
|
|
193
|
+
|
|
194
|
+
github.com/camgitt/memoir
|
|
195
|
+
|
|
196
|
+
Would love your feedback if you try it!
|
|
197
|
+
|
|
198
|
+
---
|
|
199
|
+
|
|
200
|
+
## Posting Schedule
|
|
201
|
+
|
|
202
|
+
| Day | Platform | Post |
|
|
203
|
+
|-----|----------|------|
|
|
204
|
+
| Today (Thu) | r/programming | Post #1 |
|
|
205
|
+
| Today (Thu) | X/Twitter | Thread (Post #4) |
|
|
206
|
+
| Friday | r/cursor | Post #2 |
|
|
207
|
+
| Friday | r/ClaudeAI | Post #3 |
|
|
208
|
+
| Sat-Sun | X/Twitter | Cold DMs to 10-20 devs |
|
|
209
|
+
|
|
210
|
+
## Rules
|
|
211
|
+
1. Reply to EVERY comment within 2 hours
|
|
212
|
+
2. Don't be defensive about "it's just dotfiles" — explain session handoff
|
|
213
|
+
3. Ask questions back: "What tools are you using?"
|
|
214
|
+
4. Link the demo SVG/GIF in early replies
|
|
215
|
+
5. Ask 2-3 friends to upvote within first 30 min
|