nmem-cli 0.7.6__tar.gz → 0.8.0__tar.gz
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.
- nmem_cli-0.8.0/.gitignore +1 -0
- {nmem_cli-0.7.6 → nmem_cli-0.8.0}/PKG-INFO +16 -1
- {nmem_cli-0.7.6 → nmem_cli-0.8.0}/README.md +15 -0
- {nmem_cli-0.7.6 → nmem_cli-0.8.0}/pyproject.toml +1 -1
- {nmem_cli-0.7.6 → nmem_cli-0.8.0}/src/nmem_cli/__init__.py +1 -1
- {nmem_cli-0.7.6 → nmem_cli-0.8.0}/src/nmem_cli/cli.py +812 -43
- {nmem_cli-0.7.6 → nmem_cli-0.8.0}/src/nmem_cli/session_import.py +78 -27
- {nmem_cli-0.7.6 → nmem_cli-0.8.0}/src/nmem_cli/tui/__init__.py +14 -7
- {nmem_cli-0.7.6 → nmem_cli-0.8.0}/src/nmem_cli/tui/__main__.py +1 -1
- {nmem_cli-0.7.6 → nmem_cli-0.8.0}/src/nmem_cli/tui/api_client.py +1 -0
- nmem_cli-0.7.6/.gitignore +0 -5
- {nmem_cli-0.7.6 → nmem_cli-0.8.0}/src/nmem_cli/license_payload.py +0 -0
- {nmem_cli-0.7.6 → nmem_cli-0.8.0}/src/nmem_cli/py.typed +0 -0
- {nmem_cli-0.7.6 → nmem_cli-0.8.0}/src/nmem_cli/tui/app.py +0 -0
- {nmem_cli-0.7.6 → nmem_cli-0.8.0}/src/nmem_cli/tui/screens/__init__.py +0 -0
- {nmem_cli-0.7.6 → nmem_cli-0.8.0}/src/nmem_cli/tui/screens/dashboard.py +0 -0
- {nmem_cli-0.7.6 → nmem_cli-0.8.0}/src/nmem_cli/tui/screens/graph.py +0 -0
- {nmem_cli-0.7.6 → nmem_cli-0.8.0}/src/nmem_cli/tui/screens/help.py +0 -0
- {nmem_cli-0.7.6 → nmem_cli-0.8.0}/src/nmem_cli/tui/screens/memories.py +0 -0
- {nmem_cli-0.7.6 → nmem_cli-0.8.0}/src/nmem_cli/tui/screens/memory_detail.py +0 -0
- {nmem_cli-0.7.6 → nmem_cli-0.8.0}/src/nmem_cli/tui/screens/settings.py +0 -0
- {nmem_cli-0.7.6 → nmem_cli-0.8.0}/src/nmem_cli/tui/screens/thread_detail.py +0 -0
- {nmem_cli-0.7.6 → nmem_cli-0.8.0}/src/nmem_cli/tui/screens/threads.py +0 -0
- {nmem_cli-0.7.6 → nmem_cli-0.8.0}/src/nmem_cli/tui/widgets/__init__.py +0 -0
|
@@ -0,0 +1 @@
|
|
|
1
|
+
config.env
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
Metadata-Version: 2.4
|
|
2
2
|
Name: nmem-cli
|
|
3
|
-
Version: 0.
|
|
3
|
+
Version: 0.8.0
|
|
4
4
|
Summary: CLI and TUI for Nowledge Mem - AI memory management
|
|
5
5
|
Project-URL: Homepage, https://mem.nowledge.co/
|
|
6
6
|
Project-URL: Repository, https://github.com/nowledge-co/
|
|
@@ -180,6 +180,21 @@ Use environment variables when you want a temporary override for the current she
|
|
|
180
180
|
|
|
181
181
|
`nmem config client ...` controls how this machine connects outward to Mem. It is separate from `nmem config access ...`, which controls how a Mem server is exposed to other devices on your network or through Access Anywhere.
|
|
182
182
|
|
|
183
|
+
## MCP Host Configuration
|
|
184
|
+
|
|
185
|
+
Direct HTTP MCP clients do not read `~/.nowledge-mem/config.json` by themselves. The host owns its MCP transport, so remote Mem needs headers in that host's MCP settings.
|
|
186
|
+
|
|
187
|
+
Generate the right snippet from the client config you already saved:
|
|
188
|
+
|
|
189
|
+
```bash
|
|
190
|
+
nmem config mcp show --host codex
|
|
191
|
+
nmem config mcp show --host gemini-cli
|
|
192
|
+
nmem config mcp show --host cursor
|
|
193
|
+
nmem config mcp show --host claude-desktop
|
|
194
|
+
```
|
|
195
|
+
|
|
196
|
+
For a fixed Mem space, add `--space "Research Agent"`. The generated snippet includes your API key when one is configured, so paste it only into the target host's private MCP config.
|
|
197
|
+
|
|
183
198
|
## Environment Variables
|
|
184
199
|
|
|
185
200
|
| Variable | Description | Default |
|
|
@@ -147,6 +147,21 @@ Use environment variables when you want a temporary override for the current she
|
|
|
147
147
|
|
|
148
148
|
`nmem config client ...` controls how this machine connects outward to Mem. It is separate from `nmem config access ...`, which controls how a Mem server is exposed to other devices on your network or through Access Anywhere.
|
|
149
149
|
|
|
150
|
+
## MCP Host Configuration
|
|
151
|
+
|
|
152
|
+
Direct HTTP MCP clients do not read `~/.nowledge-mem/config.json` by themselves. The host owns its MCP transport, so remote Mem needs headers in that host's MCP settings.
|
|
153
|
+
|
|
154
|
+
Generate the right snippet from the client config you already saved:
|
|
155
|
+
|
|
156
|
+
```bash
|
|
157
|
+
nmem config mcp show --host codex
|
|
158
|
+
nmem config mcp show --host gemini-cli
|
|
159
|
+
nmem config mcp show --host cursor
|
|
160
|
+
nmem config mcp show --host claude-desktop
|
|
161
|
+
```
|
|
162
|
+
|
|
163
|
+
For a fixed Mem space, add `--space "Research Agent"`. The generated snippet includes your API key when one is configured, so paste it only into the target host's private MCP config.
|
|
164
|
+
|
|
150
165
|
## Environment Variables
|
|
151
166
|
|
|
152
167
|
| Variable | Description | Default |
|