Skip to content

Clarify provider setup, refresh failures and memory processing - #224

Open
Sma1lboy wants to merge 5 commits into
mainfrom
fix/provider-guidance-20261001
Open

Sma1lboy wants to merge 5 commits into
mainfrom
fix/provider-guidance-20261001

Conversation

@Sma1lboy

@Sma1lboy Sma1lboy commented Oct 1, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Independent app-only UX copy and narrow provider-state recovery fixes. No AI provider, credential, sandbox or billing behavior changes.

Before → after

  • “Local AI Providers” → AI providers; local history vs external processing and costs are explicit
  • Missing key/sign-in/install messages → concrete setup and re-check instructions
  • Key existence labeled Ready → Configured, without implying an API validation request
  • Refresh could retain stale Ready statuses and reject silently → checking/error/retry feedback; late results cannot overwrite the latest check
  • Default selection vs colleague-specific choice is explained
  • Empty-channel setup no longer claims nobody can answer based only on the default provider; suggestions are described as drafts
  • Background memory provider transmission and charges are explicit; missing status is not fabricated as zero jobs, and failed loading can be retried

Tests

  • Full suite: 586 passed, 3 pre-existing skipped
  • New regression tests: 8/8 included above (missing bridge, rejected/unsuccessful IPC, stale status, retry, request races and provider hints)
  • Automation TypeScript check: passed
  • Changed-source ESLint: zero errors, two existing agents-page hook warnings
  • Strict native before/after verification passed on exact head 1cd26f4d123df0b6d5699eb6b0cd2bdf69069b08: actual Electron on macOS, two isolated profiles, 26 successful automation operations per variant. Six screenshot and log artifacts, visually inspected.
  • Exact-head unit tests passed

Limits

  • Cloud-local automation:prepare hits Unix-socket EPERM; completed macOS CI supplies the real-app verification
  • Whole-app local type-check was terminated by environment; no full type-check pass claimed
  • No credentials, billable model calls, provider chats, production changes, merges or deployment
  • Legacy Build Check can falsely report green after Forge OOM; independently fixed and validated in Make Electron CI fail on incomplete bundles and missing DMGs #225. Do not use that legacy badge alone as packaging proof
  • Existing external Vercel – foxyfox-docs check fails; website preview passes. No hosting settings changed

Full rationale and acceptance coverage: docs/ux-review-providers.md.

@vercel

vercel Bot commented Oct 1, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
foxyfox-docs Error Error Oct 1, 2026 11:56am UTC
1 Skipped Deployment
Project Deployment Actions Updated
foxyfox-website Skipped Skipped Oct 1, 2026 11:56am UTC

Request Review

@vercel
vercel Bot temporarily deployed to Preview – foxyfox-website October 1, 2026 11:56 Inactive
@Sma1lboy
Sma1lboy marked this pull request as ready for review October 1, 2026 20:13

This branch had an error being deployed

1 failed and 1 inactive deployments
Preview – foxyfox-docs — 1cd26f4d Deployed Oct 1, 2026 by vercel[bot]
Preview – foxyfox-website — 1cd26f4d Deployed Oct 1, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant