@link-assistant/hive-mind 1.69.16 → 1.69.18

package/CHANGELOG.md

@@ -1,5 +1,27 @@
 # @link-assistant/hive-mind
 
+## 1.69.18
+
+### Patch Changes
+
+- 9aa5659: Fix `--auto-fork` mode failing when continuing an existing fork PR whose
+  fork name already contained the upstream-owner prefix. `setupRepository`
+  in `solve.repository.lib.mjs` was applying the
+  `--prefix-fork-name-with-owner-name` option to `forkRepoName` (which is
+  the authoritative head repo name from the PR's `headRepository.name`),
+  producing a doubled prefix like
+  `konard/labtgbot-labtgbot-telegram-claude-agent` and a 404 lookup. The
+  prefix option now only controls fork _creation_, not fork _lookup_:
+  when `forkRepoName` is present, the expected fork is
+  `${forkOwner}/${forkRepoName}` and no alternate-name fallback is
+  attempted. Resolves #1803.
+
+## 1.69.17
+
+### Patch Changes
+
+- 46422f1: Increase the default `HIVE_MIND_USAGE_API_CACHE_TTL_MS` from 10 → 13 minutes so the Claude Usage API (`/api/oauth/usage`) is queried less frequently and we stop tripping the upstream "Resets in 3m Xs" rate-limit message. Operators can still override the value via the environment variable. Resolves #1798.
+
 ## 1.69.16
 
 ### Patch Changes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@link-assistant/hive-mind",
-  "version": "1.69.16",
+  "version": "1.69.18",
   "description": "AI-powered issue solver and hive mind for collaborative problem solving",
   "main": "src/hive.mjs",
   "type": "module",

package/src/config.lib.mjs

@@ -528,12 +528,14 @@ export const getClaudeEnv = (options = {}) => {
 // Cache TTL configurations (in milliseconds)
 // The Usage API (Claude limits) has stricter rate limiting than regular APIs
 // See: https://github.com/link-assistant/hive-mind/issues/1074
+// See: https://github.com/link-assistant/hive-mind/issues/1798
 export const cacheTtl = {
   // General API cache TTL (GitHub API, etc.)
   api: parseIntWithDefault('HIVE_MIND_API_CACHE_TTL_MS', 3 * 60 * 1000), // 3 minutes
-  // Claude Usage API cache TTL - must be at least 20 minutes to avoid rate limiting
-  // The API returns null values when called too frequently
-  usageApi: parseIntWithDefault('HIVE_MIND_USAGE_API_CACHE_TTL_MS', 10 * 60 * 1000), // 10 minutes
+  // Claude Usage API cache TTL - increased by 3 minutes (from 10 → 13) per issue #1798
+  // because users still hit "Resets in 3m xs" rate-limit responses. The API
+  // returns null values or 429 when called too frequently.
+  usageApi: parseIntWithDefault('HIVE_MIND_USAGE_API_CACHE_TTL_MS', 13 * 60 * 1000), // 13 minutes
   // System metrics cache TTL (RAM, CPU, disk)
   system: parseIntWithDefault('HIVE_MIND_SYSTEM_CACHE_TTL_MS', 2 * 60 * 1000), // 2 minutes
 };

package/src/limits.lib.mjs

@@ -1271,17 +1271,20 @@ export function formatCodexLimitsSection(codexLimits, codexError = null, options
  * Values are loaded from config.lib.mjs which supports environment variable overrides.
  *
  * IMPORTANT: The Claude Usage API has stricter rate limiting than regular APIs.
- * Calling it more frequently than every 20 minutes may result in null values being returned.
+ * Calling it too frequently may return null values or a 429 "Resets in Xm Xs" error.
+ * Default raised from 10 → 13 minutes in issue #1798 (the previous 10-minute TTL still
+ * occasionally tripped a ~3-minute rate-limit window).
  * See: https://github.com/link-assistant/hive-mind/issues/1074
+ * See: https://github.com/link-assistant/hive-mind/issues/1798
  *
  * Configurable via environment variables:
  * - HIVE_MIND_API_CACHE_TTL_MS: General API cache TTL (default: 180000 = 3 minutes)
- * - HIVE_MIND_USAGE_API_CACHE_TTL_MS: Claude Usage API cache TTL (default: 1200000 = 20 minutes)
+ * - HIVE_MIND_USAGE_API_CACHE_TTL_MS: Claude Usage API cache TTL (default: 780000 = 13 minutes)
  * - HIVE_MIND_SYSTEM_CACHE_TTL_MS: System metrics cache TTL (default: 120000 = 2 minutes)
  */
 export const CACHE_TTL = {
   API: cacheTtl.api, // 3 minutes for regular API calls (GitHub)
-  USAGE_API: cacheTtl.usageApi, // 20 minutes for Claude Usage API (rate limited)
+  USAGE_API: cacheTtl.usageApi, // 13 minutes for Claude Usage API (rate limited)
   SYSTEM: cacheTtl.system, // 2 minutes for system metrics (RAM, CPU, disk)
 };
 
@@ -1345,9 +1348,10 @@ export function resetLimitCache() {
 
 export async function getCachedClaudeLimits(verbose = false) {
   const cache = getLimitCache();
-  // Use USAGE_API TTL (20 minutes) for Claude limits to avoid rate limiting
-  // The Claude Usage API returns null values when called too frequently
+  // Use USAGE_API TTL (13 min by default, see issue #1798) for Claude limits to avoid rate limiting.
+  // The Claude Usage API returns null values or 429 errors when called too frequently.
   // See: https://github.com/link-assistant/hive-mind/issues/1074
+  // See: https://github.com/link-assistant/hive-mind/issues/1798
   const cached = cache.get('claude', CACHE_TTL.USAGE_API);
   if (cached) {
     if (verbose) console.log('[VERBOSE] /limits-cache: Using cached Claude limits (TTL: ' + Math.round(CACHE_TTL.USAGE_API / 60000) + ' minutes)');
@@ -1365,8 +1369,9 @@ export async function getCachedClaudeLimits(verbose = false) {
     cache.set('claude', result, CACHE_TTL.USAGE_API);
   } else if (result.error && result.error.includes('Rate limited')) {
     // Cache rate-limit errors to prevent hammering the API
-    // Use the same 20-minute TTL as successful responses
+    // Use the same USAGE_API TTL (13 min by default) as successful responses
     // See: https://github.com/link-assistant/hive-mind/issues/1446
+    // See: https://github.com/link-assistant/hive-mind/issues/1798
     cache.set('claude-rate-limited', result, CACHE_TTL.USAGE_API);
     if (verbose) console.log('[VERBOSE] /limits-cache: Cached rate-limit error for ' + Math.round(CACHE_TTL.USAGE_API / 60000) + ' minutes');
   }

package/src/solve.repository.lib.mjs

@@ -818,12 +818,12 @@ Thank you!`;
     await log(`\n${formatAligned('🍴', 'Fork mode:', 'DETECTED from PR')}`);
     await log(`${formatAligned('', 'Fork owner:', forkOwner)}`);
 
-    // Use actual head repo name from PR data (headRepository.name) if available, otherwise guess from base repo name
+    // Issue #1803: prefix flag controls fork CREATION; for lookup, trust forkRepoName from PR head data.
     const headRepoName = forkRepoName || repo;
     const standardForkName = `${forkOwner}/${headRepoName}`;
     const prefixedForkName = `${forkOwner}/${owner}-${headRepoName}`;
-    const expectedForkName = argv.prefixForkNameWithOwnerName ? prefixedForkName : standardForkName;
-    const alternateForkName = argv.prefixForkNameWithOwnerName ? standardForkName : prefixedForkName;
+    const expectedForkName = forkRepoName ? `${forkOwner}/${forkRepoName}` : argv.prefixForkNameWithOwnerName ? prefixedForkName : standardForkName;
+    const alternateForkName = forkRepoName ? null : argv.prefixForkNameWithOwnerName ? standardForkName : prefixedForkName;
 
     await log(`${formatAligned('✅', 'Using fork:', expectedForkName)}\n`);
 
@@ -832,9 +832,9 @@ Thank you!`;
     let forkCheckResult = await $`gh repo view ${expectedForkName} --json name 2>/dev/null`;
     let actualForkName = expectedForkName;
 
-    if (forkCheckResult.code !== 0 && !argv.prefixForkNameWithOwnerName) {
-      // Only try alternate name if NOT using --prefix-fork-name-with-owner-name
-      // When the option is enabled, we should only use the prefixed fork name
+    if (forkCheckResult.code !== 0 && alternateForkName && !argv.prefixForkNameWithOwnerName) {
+      // Only try alternate name if --prefix-fork-name-with-owner-name is off AND we're guessing
+      // (forkRepoName authoritative → alternateForkName is null and no fallback is attempted).
       forkCheckResult = await $`gh repo view ${alternateForkName} --json name 2>/dev/null`;
       if (forkCheckResult.code === 0) {
         actualForkName = alternateForkName;

package/src/telegram-show-limits.lib.mjs

@@ -5,8 +5,8 @@
  * the args before they are forwarded to /solve, /hive (or /task --split). When
  * set, the bot:
  *   1. Fetches usage limits for the selected tool (Claude or Codex) using the
- *      shared cached helpers in limits.lib.mjs (TTL: 20 minutes for the usage
- *      API to avoid rate limiting).
+ *      shared cached helpers in limits.lib.mjs (USAGE_API TTL: 13 minutes by
+ *      default — see issue #1798 — to avoid rate limiting).
  *   2. Embeds a compact "Limits at start" snapshot below the infoBlock so the
  *      starting/executing message shows the user how much budget they had at
  *      the moment the command was queued.