chat-logbook 0.1.2 → 0.2.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.
Files changed (2) hide show
  1. package/README.md +6 -6
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -66,12 +66,6 @@ Because chat-logbook relies on what Claude Code persists to disk, **only convers
66
66
 
67
67
  ## FAQ
68
68
 
69
- ### Why can't I see my `/btw` conversations?
70
-
71
- The `/btw` feature in Claude Code is designed to be ephemeral — questions and answers appear in a temporary overlay and are never written to conversation history files. Since chat-logbook reads from these files, `/btw` exchanges are not available.
72
-
73
- This is by design: `/btw` is intended for quick, throwaway questions. If you want a conversation to be preserved and visible in chat-logbook, use a regular message instead of `/btw`.
74
-
75
69
  ### Is my data safe?
76
70
 
77
71
  Yes. chat-logbook is fully local — no data ever leaves your machine. It only **reads** from `~/.claude/` and never modifies your original conversation files. The SQLite database it creates for your tags, annotations, and other metadata is stored separately at `~/.chat-logbook/`.
@@ -80,6 +74,12 @@ Yes. chat-logbook is fully local — no data ever leaves your machine. It only *
80
74
 
81
75
  No. chat-logbook reads from local `~/.claude/` files, which are only created by the Claude Code CLI running on your machine. Conversations run via Claude Code on the web (cloud VMs) are not stored locally and are not accessible to chat-logbook.
82
76
 
77
+ ### Why can't I see my `/btw` conversations?
78
+
79
+ The `/btw` feature in Claude Code is designed to be ephemeral — questions and answers appear in a temporary overlay and are never written to conversation history files. Since chat-logbook reads from these files, `/btw` exchanges are not available.
80
+
81
+ This is by design: `/btw` is intended for quick, throwaway questions. If you want a conversation to be preserved and visible in chat-logbook, use a regular message instead of `/btw`.
82
+
83
83
  ## Roadmap
84
84
 
85
85
  - **Title editing** — Customize session titles for easier identification
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "chat-logbook",
3
- "version": "0.1.2",
3
+ "version": "0.2.0",
4
4
  "description": "A local-first conversation manager for Claude Code",
5
5
  "license": "MIT",
6
6
  "type": "module",