session-steward 0.11.1 → 0.12.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.
package/CHANGELOG.md CHANGED
@@ -1,5 +1,21 @@
1
1
  # Changelog
2
2
 
3
+ ## [0.12.0] - 2026-09-24
4
+
5
+ ### Added
6
+
7
+ - Manage automatic cleanup schedules in the browser, including schedules created through MCP. Create, edit, pause, run, or remove a schedule, and start or stop background runs.
8
+
9
+ ## [0.11.2] - 2026-09-23
10
+
11
+ ### Added
12
+
13
+ - Added `session-steward update` with version output and a sudo prompt when needed.
14
+
15
+ ### Changed
16
+
17
+ - Updated compatibility coverage for current Codex and Claude releases, including Codex memory v2 storage.
18
+
3
19
  ## [0.11.1] - 2026-09-14
4
20
 
5
21
  ### Added
@@ -174,6 +190,8 @@
174
190
  - Support for custom Codex home folders and a saved folder preference.
175
191
  - Streaming and bounded-memory discovery for large session collections and transcripts.
176
192
 
193
+ [0.12.0]: https://github.com/mallikcheripally/session-steward/compare/v0.11.2...v0.12.0
194
+ [0.11.2]: https://github.com/mallikcheripally/session-steward/compare/v0.11.1...v0.11.2
177
195
  [0.11.1]: https://github.com/mallikcheripally/session-steward/compare/v0.11.0...v0.11.1
178
196
  [0.11.0]: https://github.com/mallikcheripally/session-steward/compare/v0.10.3...v0.11.0
179
197
  [0.10.3]: https://github.com/mallikcheripally/session-steward/compare/v0.10.2...v0.10.3
package/README.md CHANGED
@@ -116,7 +116,7 @@ You can then ask your client to find inactive sessions, compare recognized sessi
116
116
 
117
117
  Session Steward marks cleanup, restore, and schedule management as destructive MCP actions so the client can apply its configured approval policy.
118
118
 
119
- Scheduled cleanup continues in the background after you close the client. You can ask to pause, resume, run, change, or remove a schedule. Before uninstalling Session Steward, stop scheduled cleanup:
119
+ Automatic cleanup continues in the background after you close the client. Create and manage schedules through MCP or the browser. Before uninstalling Session Steward, stop the scheduler:
120
120
 
121
121
  ```bash
122
122
  session-steward-scheduler --stop
@@ -192,10 +192,12 @@ Archiving a Claude Desktop session does not delete it. It remains available unti
192
192
  ## Update or uninstall
193
193
 
194
194
  ```bash
195
- npm install --global session-steward@latest
195
+ session-steward update
196
196
  npm uninstall --global session-steward
197
197
  ```
198
198
 
199
+ If npm needs root access, the update command asks before retrying with `sudo`.
200
+
199
201
  Uninstalling does not remove provider sessions, recovery backups, or saved folder preferences.
200
202
 
201
203
  ## Troubleshooting
@@ -13,6 +13,20 @@ assertSupportedNode();
13
13
  if (process.argv[2] === "mcp") {
14
14
  process.argv.splice(2, 1);
15
15
  await import("./session-steward-mcp.mjs");
16
+ } else if (process.argv[2] === "update") {
17
+ process.argv.splice(2, 1);
18
+ if (process.argv.length !== 2) {
19
+ process.stderr.write("Usage: session-steward update\n");
20
+ process.exitCode = 1;
21
+ } else {
22
+ const { updateSessionSteward } = await import("../lib/self-update.mjs");
23
+ try {
24
+ process.exitCode = await updateSessionSteward();
25
+ } catch (error) {
26
+ process.stderr.write(`Could not run the update: ${error.message}\n`);
27
+ process.exitCode = 1;
28
+ }
29
+ }
16
30
  } else {
17
31
  await startBrowser();
18
32
  }
@@ -33,9 +47,11 @@ async function startBrowser() {
33
47
  if (values.help) {
34
48
  process.stdout.write(`Usage: session-steward [options]
35
49
  session-steward mcp [options]
50
+ session-steward update
36
51
 
37
52
  Commands:
38
53
  mcp Run the MCP server over stdio
54
+ update Install the latest version with npm
39
55
 
40
56
  Options:
41
57
  --codex-home <path> Use a custom Codex session folder