feat(thu-fullrun): overlay attention, skills sync, credits & settings refresh (tinyhumansai#479)

* Update Conversations component to enhance user messaging for budget limits. Changed the warning text for exhausted weekly inference budget to improve clarity and user experience.

* feat(schemas): add new configuration option for vision model usage

- Introduced a new optional boolean field `use_vision_model` in the schemas for enabling vision LLM for screenshot analysis.
- Updated the screen intelligence schemas to include a required `consent` field for starting sessions, replacing the previous `sample_interval_ms` field.
- Enhanced the `ttl_secs` field description for clarity and modified the `capture_policy` to `screen_monitoring` for better understanding of its purpose.

* feat(CoreStateProvider): enhance state management with optimistic updates and error handling

- Implemented optimistic local commits for `setAnalyticsEnabled` and `setOnboardingCompletedFlag` to provide instant UI feedback while ensuring state consistency through authoritative snapshot refreshes.
- Added error handling for the `refresh` function calls in `setAnalyticsEnabled`, `setOnboardingCompletedFlag`, and `clearSession` to log failures, improving robustness in state management during user interactions.
- Updated dependencies in the `useCallback` hooks to include `refresh`, ensuring proper state updates and synchronization with the core.

* feat(paths): centralize runtime path resolution for user-scoped skills data

- Introduced a new module `paths.rs` to handle the resolution of runtime paths for skills, ensuring that `skills_data` and `workspace` directories are scoped per user.
- Updated `bootstrap_skill_runtime` and `bootstrap_skills_runtime` functions to utilize the new path resolution logic, improving consistency and clarity in directory management.
- Enhanced error logging for directory creation failures to include the specific path that failed, aiding in debugging.
- Added a new optional field `overlay_ttl_ms` in the autocomplete schemas to support overlay time-to-live configuration.

* feat(ScreenIntelligencePanel): optimize config synchronization to prevent user edit clobbering

- Introduced a reference to track the last synced configuration signature, ensuring that user edits are preserved during periodic updates from the CoreStateProvider.
- Updated the effect to compare serialized configuration values, allowing for re-sync only when actual changes occur, enhancing user experience and preventing unintended data loss.

* feat(SkillManager): implement initial sync after OAuth completion

- Added functionality to trigger an initial data sync immediately after OAuth completion, ensuring users see fresh data without waiting for the next scheduled sync.
- Updated comments to clarify the change in sync behavior due to recent modifications in the Rust core, which no longer auto-triggers sync on OAuth completion.

* fix(UsageLimitModal, Conversations): enhance user messaging for budget limits

- Updated warning messages in both UsageLimitModal and Conversations components to provide clearer information regarding weekly limits and reset times.
- Improved clarity in user notifications to enhance overall experience when budget limits are reached.

* refactor(SkillSetupModal): improve session mode handling for skill configuration

- Updated the SkillSetupModal component to lock the mode at mount time, ensuring users remain in the setup wizard during their session even if the skill is marked as complete.
- Simplified mode management by replacing the forceSetup state with a sessionMode state, allowing explicit mode switching while maintaining a consistent user experience.

* feat(SkillManager): enhance setup flow for OAuth-based skills

- Updated the `startSetup` method to handle OAuth-based skills more effectively by implementing a fallback to core RPC for skills without a frontend runtime.
- Improved error handling to treat missing `onSetupStart` implementations as successful completion for pure OAuth skills, allowing the setup wizard to display the "Connected!" screen.
- Added detailed logging for both local runtime and core RPC fallback scenarios to improve traceability during the setup process.

* feat(Home): enhance local AI status handling and asset management

- Introduced a new state for local AI assets, allowing for better tracking of model file readiness.
- Updated the loading logic to fetch both local AI status and assets concurrently, improving performance and error handling.
- Implemented a mechanism to hide the Local Model Runtime card once all models are fully downloaded, enhancing user experience.
- Added comprehensive comments to clarify the logic behind model readiness checks based on asset states.

* refactor(Credits): update credit balance structure and terminology

- Renamed credit categories in the RewardsCouponSection and PayAsYouGoCard components for clarity, changing "General credits" to "Promo credits" and "Top-up credits" to "Team top-up."
- Updated the credit balance API to reflect the new structure, replacing `balanceUsd` and `topUpBalanceUsd` with `promotionBalanceUsd` and `teamTopupUsd`.
- Adjusted normalization logic in the credits API to accommodate the new credit balance fields.
- Modified tests to ensure correct handling of the updated credit balance structure.

* feat(Settings): reorganize billing settings and update descriptions

- Added a new top-level billing section to the settings, promoting it out of the Account & Security category for better visibility.
- Updated the description for the Account & Security section to remove billing references, focusing on recovery phrase, team management, and linked account access.
- Adjusted the settings navigation to accommodate the new billing section, ensuring proper routing and user experience.

* refactor(Config): change logging level from info to debug for environment overrides

- Updated logging statements in the Config implementation to use debug level instead of info, reducing verbosity during runtime while maintaining necessary traceability for configuration loading.

* feat(Overlay): implement overlay attention event handling and refactor overlay app structure

- Introduced a new overlay module to manage attention events, allowing the core to publish messages to the overlay window.
- Enhanced the OverlayApp component to handle dictation and attention events, improving user interaction with the overlay.
- Refactored the overlay state management to support different modes (idle, stt, attention) and added auto-dismiss functionality for attention messages.
- Removed the Browser Access Toggle from the Skills page, streamlining the UI and focusing on core functionalities.
- Updated tests to reflect changes in the Skills component and removed unnecessary mocks related to browser access.

* fix(OverlayBubbleChip): reset typewriter animation on new bubble identity

- Updated the OverlayBubbleChip component to reset the typewriter animation correctly when a new bubble is displayed by using the `key` prop.
- Refactored the cleanup logic in the useEffect hook to ensure proper interval management and state reset, enhancing the user experience with bubble transitions.

* refactor(rest): streamline key_bytes_from_string function and improve readability

- Simplified the condition for checking the ASCII key length and character restrictions in the key_bytes_from_string function.
- Consolidated the import statements for base64 engines into a single line for better clarity.
- Adjusted test data formatting for improved readability in the key_bytes_from_string_tests module.

* enhance(logging): improve color detection logic for terminal output

- Updated the color detection logic in the logging module to prioritize environment variables (`NO_COLOR`, `FORCE_COLOR`, `CLICOLOR_FORCE`) for better control over color output.
- Added detailed comments explaining the color resolution order, enhancing code clarity and maintainability.

* test(Home): add mock for openhumanLocalAiAssetsStatus in tests

- Enhanced the Home and HomeBootstrapButtons test files by adding a mock implementation for openhumanLocalAiAssetsStatus, which resolves to an object with null result and empty logs. This improves the test setup for local AI asset status handling.

* refactor(SkillSetupModal): improve session mode handling and loading state

- Updated the SkillSetupModal component to ensure session mode is determined after the first snapshot resolution, preventing premature defaults to the setup wizard.
- Introduced a loading state to display a message while waiting for the skill setup status, enhancing user experience during the modal's initial render.
- Refactored the SkillManager to throw errors for real failures during setup, ensuring proper error handling and user feedback.

* refactor(Config): simplify logging for invalid proxy scope values

- Consolidated the logging statement for invalid OPENHUMAN_PROXY_SCOPE values into a single line, improving code readability while maintaining the warning functionality.

Author: senamakel

app/src-tauri/src/core_process.rs

@@ -1,3 +1,4 @@
+use std::io::IsTerminal;
 use std::path::PathBuf;
 use std::sync::Arc;
 
@@ -7,6 +8,23 @@ use tokio::sync::Mutex;
 use tokio::task::JoinHandle;
 use tokio::time::{timeout, Duration};
 
+/// Propagate ANSI color hints to the spawned core child.
+///
+/// Core's tracing formatter auto-detects color via `stderr.is_terminal()`,
+/// but when core runs as a grandchild under `yarn tauri dev` the inherited
+/// stderr may not register as a TTY even though the ultimate terminal
+/// supports ANSI. If the Tauri process itself is attached to a TTY we
+/// forward `FORCE_COLOR=1` so core emits colored log lines; `NO_COLOR`
+/// (user opt-out) always wins and short-circuits the propagation.
+fn apply_core_color_env(cmd: &mut Command) {
+    if std::env::var_os("NO_COLOR").is_some() {
+        return;
+    }
+    if std::io::stderr().is_terminal() {
+        cmd.env("FORCE_COLOR", "1");
+    }
+}
+
 #[derive(Clone, Copy, Debug, Eq, PartialEq)]
 pub enum CoreRunMode {
     InProcess,
@@ -119,6 +137,7 @@ impl CoreProcessHandle {
                             .arg(self.port.to_string());
                         cmd
                     };
+                    apply_core_color_env(&mut cmd);
                     let child = cmd
                         .spawn()
                         .map_err(|e| format!("failed to spawn core process: {e}"))?;
@@ -156,6 +175,7 @@ impl CoreProcessHandle {
                         cmd
                     };
 
+                    apply_core_color_env(&mut cmd);
                     let child = cmd
                         .spawn()
                         .map_err(|e| format!("failed to spawn core process: {e}"))?;

app/src/components/rewards/RewardsCouponSection.tsx

@@ -163,18 +163,18 @@ const RewardsCouponSection = () => {
       <div className="grid gap-4 sm:grid-cols-3">
         <div className="rounded-xl border border-stone-200 bg-stone-50 p-4">
           <div className="text-xs font-medium uppercase tracking-wide text-stone-400">
-            General credits
+            Promo credits
           </div>
           <div className="mt-2 text-2xl font-semibold text-stone-900">
-            {creditBalance ? formatUsd(creditBalance.balanceUsd) : loading ? '…' : '—'}
+            {creditBalance ? formatUsd(creditBalance.promotionBalanceUsd) : loading ? '…' : '—'}
           </div>
         </div>
         <div className="rounded-xl border border-stone-200 bg-stone-50 p-4">
           <div className="text-xs font-medium uppercase tracking-wide text-stone-400">
-            Top-up credits
+            Team top-up
           </div>
           <div className="mt-2 text-2xl font-semibold text-stone-900">
-            {creditBalance ? formatUsd(creditBalance.topUpBalanceUsd) : loading ? '…' : '—'}
+            {creditBalance ? formatUsd(creditBalance.teamTopupUsd) : loading ? '…' : '—'}
           </div>
         </div>
         <div className="rounded-xl border border-stone-200 bg-stone-50 p-4">

app/src/components/rewards/__tests__/RewardsCouponSection.test.tsx

@@ -28,8 +28,8 @@ describe('RewardsCouponSection', () => {
 
   it('loads balances and refreshes history after a successful redemption', async () => {
     mocks.mockCreditsApi.getBalance
-      .mockResolvedValueOnce({ balanceUsd: 3, topUpBalanceUsd: 1, topUpBaselineUsd: null })
-      .mockResolvedValueOnce({ balanceUsd: 8, topUpBalanceUsd: 1, topUpBaselineUsd: null });
+      .mockResolvedValueOnce({ promotionBalanceUsd: 3, teamTopupUsd: 1 })
+      .mockResolvedValueOnce({ promotionBalanceUsd: 8, teamTopupUsd: 1 });
     mocks.mockCreditsApi.getUserCoupons
       .mockResolvedValueOnce([])
       .mockResolvedValueOnce([
@@ -70,11 +70,7 @@ describe('RewardsCouponSection', () => {
   });
 
   it('shows backend redemption errors without clearing the existing state', async () => {
-    mocks.mockCreditsApi.getBalance.mockResolvedValue({
-      balanceUsd: 3,
-      topUpBalanceUsd: 0,
-      topUpBaselineUsd: null,
-    });
+    mocks.mockCreditsApi.getBalance.mockResolvedValue({ promotionBalanceUsd: 3, teamTopupUsd: 0 });
     mocks.mockCreditsApi.getUserCoupons.mockResolvedValue([]);
     mocks.mockCreditsApi.redeemCoupon.mockRejectedValueOnce({
       error: 'This coupon has already been used.',
@@ -94,8 +90,8 @@ describe('RewardsCouponSection', () => {
 
   it('shows pending coupon copy and keeps the current balance until the reward is fulfilled', async () => {
     mocks.mockCreditsApi.getBalance
-      .mockResolvedValueOnce({ balanceUsd: 3, topUpBalanceUsd: 0, topUpBaselineUsd: null })
-      .mockResolvedValueOnce({ balanceUsd: 3, topUpBalanceUsd: 0, topUpBaselineUsd: null });
+      .mockResolvedValueOnce({ promotionBalanceUsd: 3, teamTopupUsd: 0 })
+      .mockResolvedValueOnce({ promotionBalanceUsd: 3, teamTopupUsd: 0 });
     mocks.mockCreditsApi.getUserCoupons
       .mockResolvedValueOnce([])
       .mockResolvedValueOnce([

app/src/components/settings/SettingsHome.tsx

@@ -79,7 +79,7 @@ const SettingsHome = () => {
     {
       id: 'account',
       title: 'Account & Security',
-      description: 'Billing, recovery phrase, team management, and linked account access',
+      description: 'Recovery phrase, team management, and linked account access',
       icon: (
         <svg className="w-5 h-5" fill="none" stroke="currentColor" viewBox="0 0 24 24">
           <path strokeLinecap="round" strokeLinejoin="round" strokeWidth={2} d="M5 12h14M12 5v14" />
@@ -88,6 +88,23 @@ const SettingsHome = () => {
       onClick: () => navigateToSettings('account'),
       dangerous: false,
     },
+    {
+      id: 'billing',
+      title: 'Billing & Usage',
+      description: 'Subscription plan, pay-as-you-go credits, and payment methods',
+      icon: (
+        <svg className="w-5 h-5" fill="none" stroke="currentColor" viewBox="0 0 24 24">
+          <path
+            strokeLinecap="round"
+            strokeLinejoin="round"
+            strokeWidth={2}
+            d="M3 10h18M7 15h1m4 0h1m-7 4h12a3 3 0 003-3V8a3 3 0 00-3 3v8a3 3 0 003 3z"
+          />
+        </svg>
+      ),
+      onClick: () => navigateToSettings('billing'),
+      dangerous: false,
+    },
     {
       id: 'automation',
       title: 'Automation & Channels',

app/src/components/settings/hooks/useSettingsNavigation.ts

@@ -155,8 +155,11 @@ export const useSettingsNavigation = (): SettingsNavigationHook => {
       case 'ai-tools':
         return [settingsCrumb];
 
-      // Leaf panels under account
+      // Top-level billing leaf (promoted out of Account & Security)
       case 'billing':
+        return [settingsCrumb];
+
+      // Leaf panels under account
       case 'recovery-phrase':
       case 'team':
       case 'connections':

app/src/components/settings/panels/ScreenIntelligencePanel.tsx

@@ -1,4 +1,4 @@
-import { type ComponentProps, useEffect, useMemo, useState } from 'react';
+import { type ComponentProps, useEffect, useMemo, useRef, useState } from 'react';
 
 import ScreenIntelligenceDebugPanel from '../../../components/intelligence/ScreenIntelligenceDebugPanel';
 import { useScreenIntelligenceState } from '../../../features/screen-intelligence/useScreenIntelligenceState';
@@ -79,10 +79,21 @@ const ScreenIntelligencePanel = () => {
   const [isSavingConfig, setIsSavingConfig] = useState(false);
   const [configError, setConfigError] = useState<string | null>(null);
 
+  // CoreStateProvider polls every 2s (CoreStateProvider.tsx POLL_MS), producing a
+  // new `status` object reference on every tick even when the underlying config is
+  // unchanged. Keying this effect on `status?.config` identity would therefore
+  // clobber in-progress user edits every 2 seconds. Compare the serialized value
+  // instead, so we only re-sync when the server config has actually changed.
+  const lastSyncedConfigSigRef = useRef<string | null>(null);
   useEffect(() => {
     if (!status?.config) {
       return;
     }
+    const sig = JSON.stringify(status.config);
+    if (lastSyncedConfigSigRef.current === sig) {
+      return;
+    }
+    lastSyncedConfigSigRef.current = sig;
     setEnabled(status.config.enabled ?? false);
     setPolicyMode(
       status.config.policy_mode === 'whitelist_only' ? 'whitelist_only' : 'all_except_blacklist'

app/src/components/settings/panels/billing/PayAsYouGoCard.tsx

@@ -20,10 +20,15 @@ const PayAsYouGoCard = ({
   onTopUp,
   onBalanceRefresh,
 }: PayAsYouGoCardProps) => {
-  const promoCredits = creditBalance?.balanceUsd ?? 0;
-  const topUpCredits = creditBalance?.topUpBalanceUsd ?? 0;
-  const topUpBaseline = creditBalance?.topUpBaselineUsd ?? null;
-  const availableCredits = promoCredits + topUpCredits;
+  // Backend `GET /payments/credits/balance` returns
+  //   { promotionBalanceUsd, teamTopupUsd }
+  // `promotionBalanceUsd` lives on the user document
+  // (`IUserUsage.promotionBalanceUsd`) and unifies signup bonus, coupons,
+  // and referral rewards. `teamTopupUsd` is the team-level paid top-up pool.
+  // Together they make the pay-as-you-go spendable balance.
+  const promoCredits = creditBalance?.promotionBalanceUsd ?? 0;
+  const teamTopupCredits = creditBalance?.teamTopupUsd ?? 0;
+  const availableCredits = promoCredits + teamTopupCredits;
 
   // Coupon state (local — no need to share with other sections)
   const [couponCode, setCouponCode] = useState('');
@@ -78,30 +83,11 @@ const PayAsYouGoCard = ({
             <span className="text-xs text-stone-400">Signup + promo credits</span>
             <span className="text-xs font-medium text-stone-900">${promoCredits.toFixed(2)}</span>
           </div>
-          <div className="space-y-1">
-            <div className="flex items-center justify-between">
-              <span className="text-xs text-stone-400">Top-up credits</span>
-              <span className="text-xs font-medium text-stone-900">
-                ${topUpCredits.toFixed(2)}
-                {topUpBaseline != null && topUpBaseline > 0 && (
-                  <span className="text-stone-500 font-normal"> / ${topUpBaseline.toFixed(2)}</span>
-                )}
-              </span>
-            </div>
-            {topUpBaseline != null && topUpBaseline > 0 && (
-              <div className="h-1 bg-stone-700/60 rounded-full overflow-hidden">
-                <div
-                  className={`h-full rounded-full transition-all duration-300 ${
-                    topUpCredits <= 0
-                      ? 'bg-coral-500'
-                      : topUpCredits / topUpBaseline < 0.2
-                        ? 'bg-amber-500'
-                        : 'bg-primary-500'
-                  }`}
-                  style={{ width: `${Math.min(100, (topUpCredits / topUpBaseline) * 100)}%` }}
-                />
-              </div>
-            )}
+          <div className="flex items-center justify-between">
+            <span className="text-xs text-stone-400">Team top-up credits</span>
+            <span className="text-xs font-medium text-stone-900">
+              ${teamTopupCredits.toFixed(2)}
+            </span>
           </div>
         </div>
       ) : isLoadingCredits ? (

app/src/components/skills/SkillSetupModal.tsx

@@ -31,13 +31,29 @@ export default function SkillSetupModal({
   const modalRef = useRef<HTMLDivElement>(null);
   const snap = useSkillSnapshot(skillId);
   const setupComplete = snap?.setup_complete ?? false;
-  // Track whether the user has explicitly chosen to reconfigure (setup mode)
-  // even though setup is already complete.
-  const [forceSetup, setForceSetup] = useState(false);
-  // Derive mode: show manage if setup is complete (or no setup needed),
-  // unless the user explicitly chose to reconfigure.
-  const mode = forceSetup ? "setup" : (!hasSetup || setupComplete ? "manage" : "setup");
-  const setMode = (m: "manage" | "setup") => setForceSetup(m === "setup");
+  // Lock the mode in once we have a concrete snapshot — `useSkillSnapshot`
+  // returns `null` on the first render while it fetches, so reading
+  // `setup_complete` at mount time would always see `false` and wrongly
+  // default an already-connected skill into the setup wizard.
+  //
+  // We keep `sessionMode` stable after the first resolution so that an
+  // OAuth flow that flips `setup_complete` to true mid-wizard does not
+  // yank the user out of the wizard's own "complete" success screen.
+  // The user can still switch modes explicitly via `setMode` below
+  // (e.g. SkillManagementPanel's "Reconfigure" button).
+  const [sessionMode, setSessionMode] = useState<"manage" | "setup" | null>(
+    () => (!hasSetup ? "manage" : null),
+  );
+
+  useEffect(() => {
+    if (sessionMode !== null) return;
+    // Wait for the first concrete snapshot before deciding.
+    if (snap === null) return;
+    setSessionMode(setupComplete ? "manage" : "setup");
+  }, [sessionMode, snap, setupComplete]);
+
+  const setMode = (m: "manage" | "setup") => setSessionMode(m);
+  const mode = sessionMode;
 
   // Handle escape key
   useEffect(() => {
@@ -71,7 +87,11 @@ export default function SkillSetupModal({
   };
 
   const headerTitle =
-    mode === "manage" ? `Manage ${skillName}` : `Connect ${skillName}`;
+    mode === null
+      ? skillName
+      : mode === "manage"
+        ? `Manage ${skillName}`
+        : `Connect ${skillName}`;
 
   const modalContent = (
     <div
@@ -142,7 +162,11 @@ export default function SkillSetupModal({
 
         {/* Content */}
         <div className="p-4">
-          {mode === "manage" ? (
+          {mode === null ? (
+            <div className="flex items-center justify-center py-8 text-sm text-stone-400">
+              Loading…
+            </div>
+          ) : mode === "manage" ? (
             <SkillManagementPanel
               skillId={skillId}
               onClose={onClose}

app/src/components/upsell/UsageLimitModal.tsx

@@ -43,7 +43,7 @@ export default function UsageLimitModal({
   if (!open) return null;
 
   const bodyText = isBudgetExhausted
-    ? 'Your included weekly inference budget is exhausted. Upgrade your plan or top up credits to continue.'
+    ? `You've hit your weekly limit.${resetTime ? ` It resets ${formatResetTime(resetTime)}.` : ''} Upgrade your plan or top up credits to avoid limits.`
     : `You've hit your 10-hour inference rate limit.${resetTime ? ` It resets ${formatResetTime(resetTime)}.` : ''} Upgrade for higher limits.`;
 
   return (

app/src/lib/skills/manager.ts

@@ -148,18 +148,59 @@ class SkillManager {
   /**
    * Start the setup flow for a skill. Returns the first step, or null if
    * the skill doesn't implement setup/start (e.g. OAuth-only skills).
+   *
+   * OAuth-based skills never instantiate a frontend `SkillRuntime` — they
+   * live only in the Rust core (see `shared.tsx` "no need to start the
+   * QuickJS runtime first"). For those we fall back to the core RPC
+   * `openhuman.skills_setup_start`, mirroring the fallback pattern in
+   * `notifyOAuthComplete`. If the core errors (e.g. the skill doesn't
+   * implement `onSetupStart` at all, which is common for pure OAuth
+   * skills), we treat it as "no more setup steps" — the wizard interprets
+   * that as success and shows the "Connected!" screen.
    */
   async startSetup(skillId: string): Promise<SetupStep | null> {
     console.log("[SkillManager] startSetup", skillId);
     const runtime = this.runtimes.get(skillId);
-    if (!runtime) {
-      console.log("[SkillManager] runtime not found", skillId);
-      throw new Error(`Skill ${skillId} runtime not found`);
+    if (runtime) {
+      emitSkillStateChange(skillId);
+      console.log("[SkillManager] setup started (local runtime)", skillId);
+      return runtime.setupStart();
     }
 
-    emitSkillStateChange(skillId);
-    console.log("[SkillManager] setup started", skillId);
-    return runtime.setupStart();
+    // No frontend runtime — dispatch via core RPC pass-through.
+    //
+    // The core side returns `null` (not an error) when the skill has no
+    // `onSetupStart` handler — see `handle_js_call` in
+    // `src/openhuman/skills/qjs_skill_instance/js_handlers.rs`, which
+    // falls through to `return "null"` when the function is missing.
+    // So any exception thrown here is a *real* failure (skill not
+    // running, RPC transport error, JS exception in the handler, …)
+    // and must be propagated so the caller can surface it to the user
+    // instead of silently pretending setup succeeded.
+    try {
+      const result = (await callCoreRpc({
+        method: "openhuman.skills_setup_start",
+        params: { skill_id: skillId },
+      })) as { step?: SetupStep } | null;
+      emitSkillStateChange(skillId);
+      console.log(
+        "[SkillManager] setup started (core RPC fallback)",
+        skillId,
+        result,
+      );
+      if (!result || !result.step) {
+        return null;
+      }
+      return result.step;
+    } catch (err) {
+      console.warn(
+        "[SkillManager] setup_start core fallback failed",
+        skillId,
+        err,
+      );
+      emitSkillStateChange(skillId);
+      throw err;
+    }
   }
 
   /**
@@ -344,6 +385,22 @@ class SkillManager {
       }
     }
 
+    // Kick off an initial sync so the user sees fresh data immediately
+    // after connecting, rather than waiting for the next cron tick.
+    // The Rust core no longer auto-triggers sync on oauth/complete
+    // (removed in commit 840b1d3c), so the frontend drives it here.
+    // Fire-and-forget: any failure is logged but must not block the
+    // OAuth completion flow.
+    try {
+      console.log(`[SkillManager] kicking initial sync after OAuth for '${skillId}'`);
+      await this.triggerSync(skillId);
+    } catch (syncErr) {
+      console.warn(
+        `[SkillManager] initial post-OAuth sync failed for '${skillId}':`,
+        syncErr,
+      );
+    }
+
     emitSkillStateChange(skillId);
   }