@yuiseki/gyazocli 0.7.0 → 0.8.0

package/dist/commands/sync.js

@@ -13,12 +13,24 @@ function registerSyncCommand(program) {
         .option('--days <number>', 'number of days to sync (used when --date is omitted)')
         .option('--date <yyyy|yyyy-mm|yyyy-mm-dd>', 'sync only this date/month/year range')
         .option('--max-pages <number>', 'max pages to fetch', '10')
+        .option('--query <query>', 'fill the cache from a search instead of the listing')
         .action(async (options) => {
         await (0, credentials_1.ensureAccessToken)();
         if (options.date && options.days) {
             console.error('Error: --date and --days cannot be used together.');
             process.exit(1);
         }
+        if (options.query && (options.date || options.days)) {
+            // Search results are not ordered the same way for every query: a plain
+            // query comes back newest first, while a `date:` one starts at the
+            // beginning of its range. Nothing here can bound a walk by date
+            // safely, and the query language can: put the range in the query.
+            console.error('Error: --query cannot be used with --date or --days.');
+            console.error('Hint: bound the range inside the query, as');
+            console.error('  --query "has:exif date:2026-08"');
+            console.error('  --query "has:exif since:2026-08-01 until:2026-08-31"');
+            process.exit(1);
+        }
         const maxPages = (0, options_1.parsePositiveIntegerOption)(options.maxPages, '--max-pages');
         let startDate;
         let endDate;
@@ -37,20 +49,29 @@ function registerSyncCommand(program) {
             startDate.setDate(startDate.getDate() - days - 1);
             startDate.setHours(0, 0, 0, 0);
         }
-        console.log(`Syncing images between ${startDate.toISOString()} and ${endDate.toISOString()}...`);
+        if (options.query) {
+            console.log(`Syncing images matching ${JSON.stringify(options.query)}...`);
+        }
+        else {
+            console.log(`Syncing images between ${startDate.toISOString()} and ${endDate.toISOString()}...`);
+        }
         const hourlyIndices = new Map();
         for (let page = 1; page <= maxPages; page++) {
-            const images = await (0, api_1.listImages)(page, 100);
+            const images = options.query
+                ? await (0, api_1.searchImages)(options.query, page, 100)
+                : await (0, api_1.listImages)(page, 100);
             if (images.length === 0)
                 break;
             let reachedLimit = false;
             for (const img of images) {
                 const createdAt = new Date(img.created_at);
-                if (createdAt > endDate) {
+                // A query says for itself what it covers, and the results are not
+                // ordered predictably enough to stop early on a date.
+                if (!options.query && createdAt > endDate) {
                     // Skip images newer than target range.
                     continue;
                 }
-                if (createdAt < startDate) {
+                if (!options.query && createdAt < startDate) {
                     reachedLimit = true;
                     break;
                 }

package/dist/index.js

@@ -26,7 +26,7 @@ program
     .name('gyazo')
     .description('Gyazo Memory CLI for AI Secretary')
     .option('--mcp-server', 'run as a Model Context Protocol server over stdio')
-    .version('0.7.0');
+    .version('0.8.0');
 (0, config_1.registerConfigCommand)(program);
 (0, list_1.registerListCommand)(program);
 (0, get_1.registerGetCommand)(program);

package/docs/ADR/003-cli-structure.md

@@ -13,7 +13,7 @@ Adopt and document the existing top-level command structure.
 
 ### 1. Program Metadata
 - Binary name: `gyazo`
-- Version: `0.7.0`
+- Version: `0.8.0`
 - Description: `Gyazo Memory CLI for AI Secretary`
 
 ### 2. Commands
@@ -118,6 +118,8 @@ Adopt and document the existing top-level command structure.
     - `--days <number>` (default: `1`, used when `--date` is omitted)
     - `--date <yyyy|yyyy-mm|yyyy-mm-dd>`
     - `--max-pages <number>` (default: `10`)
+    - `--query <query>` (fill from a search instead of the listing; not with
+      `--date` or `--days`, because the range belongs inside the query)
 - `gyazo import <type> <dir>`
   - Supported types: `json`, `hourly`
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@yuiseki/gyazocli",
-  "version": "0.7.0",
+  "version": "0.8.0",
   "description": "Gyazo Memory CLI for AI Secretary",
   "repository": {
     "type": "git",

package/skills/gyazo/SKILL.md

@@ -97,12 +97,20 @@ endpoint returns the first 100 and cannot page.
 ```bash
 gyazo sync --days 7                  # yesterday back through 7 days
 gyazo sync --date 2026-08            # a whole month
+gyazo sync --query "has:exif OR has:location" --max-pages 20
 ```
 
 `sync` covers yesterday backwards and never today, because today is still
 happening. For anything from today use `ls --today`, `search`, or a ranking
 command with `--today`.
 
+`--query` fills the cache from a search instead of the listing, which is how to
+gather one kind of capture without walking past everything else: photographs
+are a small fraction of a day's screenshots. Put any date range inside the
+query (`date:2026-08`, `since:... until:...`) rather than in `--date`, which
+`--query` refuses. Budget about 40 seconds per page of 100 captures that are
+not cached yet.
+
 ## Answering questions with captures
 
 - A day is a local day. `--date 2026-08-30` means that date in this machine's