memoir-cli 3.2.1 → 3.3.0

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.
@@ -1,215 +0,0 @@
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