chat-logbook 0.7.1 → 0.9.0

package/README.md

@@ -50,7 +50,7 @@ The full problem statement, user stories, and direction live in the
 
 ## What works today
 
-- **Three-column layout.** Resizable panels for filters, session list,
+- **Three-column layout.** Resizable panels for filters, chat list,
   and conversation content.
 - **Rich conversation rendering.** Markdown, syntax-highlighted code
   blocks, collapsible tool calls with one-line summaries, and collapsible
@@ -58,17 +58,21 @@ The full problem statement, user stories, and direction live in the
 - **Virtual scrolling.** Long conversations scroll smoothly.
 - **Solarized Dark theme.** Easy on the eyes, consistent with Claude
   Code's terminal look.
-- **Soft delete with Trash.** Hide sessions you don't want to see; restore
+- **Soft delete with Trash.** Hide chats you don't want to see; restore
   them anytime.
-- **Custom session titles.** Rename any session — click its title in the
+- **Custom chat titles.** Rename any chat — click its title in the
   list or conversation header, or select it and press `F2` / `↵`. Clear
   the title to fall back to the first message.
 - **Local archive.** Every conversation chat-logbook reads is copied into
   `~/.chat-logbook/archive.db`. The UI reads from the archive, so a
-  session stays visible even after the source JSONL is gone.
-- **Live updates.** While Claude Code is actively writing to a session,
+  chat stays visible even after the source JSONL is gone.
+- **Live updates.** While Claude Code is actively writing to a chat,
   new messages appear in chat-logbook within seconds — no restart
   needed.
+- **Chat metadata at a glance.** A ⓘ button on the conversation
+  header opens a popover showing when the chat started, when it was
+  last updated, the agent, the project working directory, and the
+  chat's IDs — with one-click copy.
 
 ## Quick start
 
@@ -94,7 +98,7 @@ chat-logbook is running at http://localhost:3100
 ```
 
 A browser window opens automatically, showing a list of your Claude Code
-sessions on the left and conversation content on the right.
+chats on the left and conversation content on the right.
 
 ### Troubleshooting
 
@@ -156,13 +160,13 @@ doesn't talk to their servers and isn't endorsed by them.
 
 Two phases of work are in flight, in this order.
 
-**Custom titles and tags.** Rename a session to something you'll
+**Custom titles and tags.** Rename a chat to something you'll
 recognize, attach tags with custom colors, and filter the list by tag or
 by project. This is the path from "I have a lot of conversations" to
 "I can find the one I need."
 
 **Spotlight search.** A keyboard-driven overlay (`⌘K` or `/`) that
-searches across sessions, messages, tags, and projects from one input.
+searches across chats, messages, tags, and projects from one input.
 A match lands you on the exact message with the term highlighted, and
 you can jump between every match without leaving the overlay.
 

package/api/dist/drizzle/0002_rename_sessions_meta_to_chats_meta.sql

@@ -0,0 +1 @@
+ALTER TABLE `sessions_meta` RENAME TO `chats_meta`;

package/api/dist/drizzle/archive/0005_rename_session_to_chat.sql

@@ -0,0 +1,17 @@
+ALTER TABLE `sessions` RENAME TO `chats`;--> statement-breakpoint
+ALTER TABLE `chats` RENAME COLUMN `short_code` TO `chat_id`;--> statement-breakpoint
+ALTER TABLE `chats` RENAME COLUMN `source_session_id` TO `source_id`;--> statement-breakpoint
+ALTER TABLE `raw_messages` RENAME COLUMN `session_id` TO `source_id`;--> statement-breakpoint
+DROP INDEX `raw_messages_idem_idx`;--> statement-breakpoint
+CREATE UNIQUE INDEX `raw_messages_idem_idx` ON `raw_messages` (`agent`,`source_id`,`payload_hash`);--> statement-breakpoint
+ALTER TABLE `messages` RENAME COLUMN `session_id` TO `source_id`;--> statement-breakpoint
+DROP INDEX `messages_canonical_idx`;--> statement-breakpoint
+CREATE UNIQUE INDEX `messages_canonical_idx` ON `messages` (`agent`,`source_id`,`message_id`);--> statement-breakpoint
+ALTER TABLE `session_scan_state` RENAME COLUMN `session_id` TO `source_id`;--> statement-breakpoint
+DROP INDEX `session_scan_state_idx`;--> statement-breakpoint
+CREATE UNIQUE INDEX `session_scan_state_idx` ON `session_scan_state` (`agent`,`source_id`);--> statement-breakpoint
+ALTER TABLE `ingestion_events` RENAME COLUMN `session_id` TO `source_id`;--> statement-breakpoint
+DROP INDEX `sessions_agent_source_idx`;--> statement-breakpoint
+CREATE UNIQUE INDEX `chats_agent_source_idx` ON `chats` (`agent`,`source_id`);--> statement-breakpoint
+DROP INDEX `sessions_short_code_unique`;--> statement-breakpoint
+CREATE UNIQUE INDEX `chats_chat_id_unique` ON `chats` (`chat_id`);

package/api/dist/drizzle/archive/0006_add_project_path.sql

@@ -0,0 +1 @@
+ALTER TABLE `chats` ADD `project_path` text;

package/api/dist/drizzle/archive/meta/_journal.json

@@ -36,6 +36,20 @@
       "when": 1778671090820,
       "tag": "0004_worried_mojo",
       "breakpoints": true
+    },
+    {
+      "idx": 5,
+      "version": "6",
+      "when": 1779000000000,
+      "tag": "0005_rename_session_to_chat",
+      "breakpoints": true
+    },
+    {
+      "idx": 6,
+      "version": "6",
+      "when": 1779100000000,
+      "tag": "0006_add_project_path",
+      "breakpoints": true
     }
   ]
 }

package/api/dist/drizzle/meta/_journal.json

@@ -15,6 +15,13 @@
       "when": 1778025600000,
       "tag": "0001_rekey_sessions_meta",
       "breakpoints": true
+    },
+    {
+      "idx": 2,
+      "version": "6",
+      "when": 1779000000000,
+      "tag": "0002_rename_sessions_meta_to_chats_meta",
+      "breakpoints": true
     }
   ]
 }