chat-logbook 0.12.0 → 0.14.0

package/README.md

@@ -4,7 +4,7 @@
 
 A local-first library for the conversations you've had with your AI tools. Read by chat-logbook, kept on your machine, browsable and searchable in one place — even after your AI tool has deleted the original.
 
-> **Status.** A personal side project, moving at side-project pace — development and responses happen as time allows. Early release: browsing, rendering, soft-delete, and a local archive that survives vendor cleanup all work today. Search and tags are next. See [Roadmap](#roadmap).
+> **Status.** A personal side project, moving at side-project pace — development and responses happen as time allows. Early release: browsing, rendering, tags, soft-delete, and a local archive that survives vendor cleanup all work today. Search is next. See [Roadmap](#roadmap).
 
 ## What chat-logbook is
 
@@ -33,6 +33,7 @@ The full problem statement, user stories, and direction live in the [PRD](docs/P
   and conversation content.
 - **Rich conversation rendering.** Markdown, syntax-highlighted code blocks, collapsible tool calls with one-line summaries, and collapsible thinking blocks.
 - **Virtual scrolling.** Long conversations scroll smoothly.
+- **A chat list that scales.** The list loads on demand as you scroll and stays fast even with tens of thousands of chats.
 - **Solarized Dark theme.** Easy on the eyes, consistent with Claude
   Code's terminal look.
 - **Soft delete with Trash.** Hide chats you don't want to see; restore
@@ -40,8 +41,10 @@ The full problem statement, user stories, and direction live in the [PRD](docs/P
 - **Sortable lists.** Sort your chats by title, created time, or updated time, and the choice sticks between visits. Trash sorts independently — by deleted time by default.
 - **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 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.
+- **Live updates.** While Claude Code is actively writing to a chat, new messages appear in chat-logbook within seconds — no restart needed. New and changed chats surface in the list on their own, without a manual refresh.
 - **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.
+- **Tags.** Create tags, give them colors, and assign them to chats. They show as colored chips on the chat and in the list. Rename or delete them anytime.
+- **Filter by tag or project.** Narrow the chat list to a project, or to chats that carry all of several selected tags.
 
 ## Quick start
 
@@ -109,13 +112,9 @@ No. chat-logbook reads files those tools write on your machine. It doesn't talk
 
 ## Roadmap
 
-Two phases of work are in flight, in this order.
-
-**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 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.
 
-Beyond these three, several smaller things are on the list without firm timing — live updates while an AI tool is writing, annotations and highlights for marking what matters, editing your own past messages, CLI commands for working with conversations from a terminal. Some will ship; some are still being weighed.
+Beyond this, several smaller things are on the list without firm timing — live updates while an AI tool is writing, annotations and highlights for marking what matters, editing your own past messages, CLI commands for working with conversations from a terminal. Some will ship; some are still being weighed.
 
 Explicit non-goals: semantic / vector search, cloud sync inside the OSS core, modification of source directories like `~/.claude/`, and bulk export to bespoke formats (the archive itself is the export). See the [PRD](docs/PRD.md) for the full out-of-scope list.
 

package/api/dist/drizzle/0004_add_tags.sql

@@ -0,0 +1,16 @@
+CREATE TABLE `tags` (
+	`id` text PRIMARY KEY NOT NULL,
+	`name` text NOT NULL,
+	`color` text NOT NULL,
+	`created_at` integer NOT NULL,
+	`updated_at` integer NOT NULL
+);
+--> statement-breakpoint
+CREATE TABLE `chat_tags` (
+	`chat_id` text NOT NULL,
+	`tag_id` text NOT NULL,
+	PRIMARY KEY(`chat_id`, `tag_id`),
+	FOREIGN KEY (`tag_id`) REFERENCES `tags`(`id`) ON UPDATE no action ON DELETE cascade
+);
+--> statement-breakpoint
+CREATE INDEX `chat_tags_tag_id_idx` ON `chat_tags` (`tag_id`);

package/api/dist/drizzle/0005_add_deleted_at_index.sql

@@ -0,0 +1 @@
+CREATE INDEX `chats_meta_deleted_at_idx` ON `chats_meta` (`deleted_at`,`id`) WHERE `deleted_at` IS NOT NULL;

package/api/dist/drizzle/0006_add_chat_sort_keys.sql

@@ -0,0 +1,7 @@
+CREATE TABLE `chat_sort_keys` (
+	`id` text PRIMARY KEY NOT NULL,
+	`text_key` text,
+	`sort_key` text
+);
+--> statement-breakpoint
+CREATE INDEX `chat_sort_keys_sort_key_idx` ON `chat_sort_keys` (`sort_key`,`id`);

package/api/dist/drizzle/archive/0008_add_chats_project_idx.sql

@@ -0,0 +1 @@
+CREATE INDEX `chats_project_idx` ON `chats` (`project`);

package/api/dist/drizzle/archive/0009_add_chats_updated_at.sql

@@ -0,0 +1,21 @@
+-- Denormalized "most recent activity" column for the server-side activity sort
+-- (ADR-0017, issue #129). Nullable on ADD COLUMN, then backfilled below so every
+-- existing row gets a value; new rows are initialized by the ingest write seam.
+ALTER TABLE `chats` ADD COLUMN `updated_at` integer;
+--> statement-breakpoint
+-- Backfill: most recent message ts per chat, falling back to first_seen_at for a
+-- chat that has no messages yet, so updated_at is never NULL.
+UPDATE `chats`
+SET `updated_at` = coalesce(
+  (SELECT max(`m`.`ts`)
+     FROM `messages` `m`
+    WHERE `m`.`agent` = `chats`.`agent`
+      AND `m`.`source_id` = `chats`.`source_id`),
+  `chats`.`first_seen_at`
+);
+--> statement-breakpoint
+-- Covering keyset indexes: (sortKey, id) so each list sort's ORDER BY + LIMIT is
+-- an index range scan that stops after one page.
+CREATE INDEX `chats_created_keyset_idx` ON `chats` (`first_seen_at`,`id`);
+--> statement-breakpoint
+CREATE INDEX `chats_updated_keyset_idx` ON `chats` (`updated_at`,`id`);

package/api/dist/drizzle/archive/0010_add_chats_created_at.sql

@@ -0,0 +1,26 @@
+-- Denormalized "conversation start" column for the createdAt list sort (issue
+-- #143, reconciling ADR-0017). The createdAt axis must page by what the reader
+-- displays — min(messages.ts) — not first_seen_at (the ingest time), so the
+-- paged order and the shown createdAt agree. Nullable on ADD COLUMN, then
+-- backfilled below so every existing row gets a value; new rows are initialized
+-- by the ingest write seam.
+ALTER TABLE `chats` ADD COLUMN `created_at` integer;
+--> statement-breakpoint
+-- Backfill: earliest message ts per chat, falling back to first_seen_at for a
+-- chat that has no messages yet, so created_at is never NULL and matches the
+-- reader's displayed createdAt (min(messages.ts) ?? first_seen_at).
+UPDATE `chats`
+SET `created_at` = coalesce(
+  (SELECT min(`m`.`ts`)
+     FROM `messages` `m`
+    WHERE `m`.`agent` = `chats`.`agent`
+      AND `m`.`source_id` = `chats`.`source_id`),
+  `chats`.`first_seen_at`
+);
+--> statement-breakpoint
+-- Repoint the createdAt keyset index from first_seen_at to created_at: the
+-- covering (sortKey, id) so the createdAt ORDER BY + LIMIT stays an index range
+-- scan that stops after one page, in either direction.
+DROP INDEX `chats_created_keyset_idx`;
+--> statement-breakpoint
+CREATE INDEX `chats_created_keyset_idx` ON `chats` (`created_at`,`id`);

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

@@ -57,6 +57,27 @@
       "when": 1779200000000,
       "tag": "0007_drop_session_scan_state",
       "breakpoints": true
+    },
+    {
+      "idx": 8,
+      "version": "6",
+      "when": 1779300000000,
+      "tag": "0008_add_chats_project_idx",
+      "breakpoints": true
+    },
+    {
+      "idx": 9,
+      "version": "6",
+      "when": 1779400000000,
+      "tag": "0009_add_chats_updated_at",
+      "breakpoints": true
+    },
+    {
+      "idx": 10,
+      "version": "6",
+      "when": 1779500000000,
+      "tag": "0010_add_chats_created_at",
+      "breakpoints": true
     }
   ]
 }

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

@@ -29,6 +29,27 @@
       "when": 1779500000000,
       "tag": "0003_add_deleted_at",
       "breakpoints": true
+    },
+    {
+      "idx": 4,
+      "version": "6",
+      "when": 1780000000000,
+      "tag": "0004_add_tags",
+      "breakpoints": true
+    },
+    {
+      "idx": 5,
+      "version": "6",
+      "when": 1780500000000,
+      "tag": "0005_add_deleted_at_index",
+      "breakpoints": true
+    },
+    {
+      "idx": 6,
+      "version": "6",
+      "when": 1781000000000,
+      "tag": "0006_add_chat_sort_keys",
+      "breakpoints": true
     }
   ]
 }