Question 1

How to fix exec-server error -32603 'os error 123' (invalid filename syntax) when launching a program from a path with spaces on Windows?

Accepted Answer

Cause: In `apps/desktop/src/main/remote-agent/controller/execServerRelay.ts`, `mapExecServerParams()` calls `workspace.mapCommand()` on every argv element including `argv[0]`. When the virtual program directory maps to a Windows path containing spaces (e.g. `C:\Program Files\PowerShell\7`), shell quoting becomes part of the executable filename (e.g. `"C:/Program Files/PowerShell/7"/pwsh.exe`). Since no shell parses the quotes before `CreateProcess`, Windows rejects it with `ERROR_INVALID_NAME` (os error 123). Fix: use `workspace.mapAlias()` for `argv[0]` only, keep `mapCommand()` for the rest:

```diff
- if (Array.isArray(result.argv)) result.argv = result.argv.map((part) => typeof part === 'string' ? workspace.mapCommand(part, resolveExecutorShell().dialect) : part);
+ if (Array.isArray(result.argv)) result.argv = result.argv.map((part, index) => {
+   if (typeof part !== 'string') return part;
+   return index === 0 ? workspace.mapAlias(part) : workspace.mapCommand(part, resolveExecutorShell().dialect);
+ });
```

This maps only registered aliases and leaves native paths, bare PATH names, and relative names unchanged. Verify with: `pnpm --dir apps/desktop exec vitest run src/main/remote-agent/__tests__/execServerProjection.e2e.test.ts --maxWorkers=1` and `pnpm --filter desktop run --if-present typecheck`.

Question 2

Why does re-saving group settings without changes trigger a REVISION_CONFLICT error in Cindy desktop app?

Accepted Answer

Root cause: In `apps/desktop/src/renderer/features/bots/ChatGroupSettings.tsx`, the `draftRevision` ref is only set at initialization and on the first edit (when entering dirty state). After a successful save, the effect that syncs refreshed group data updates the form fields but never advances `draftRevision`. So if you click 'Save' again without editing, the request still sends the old `expectedRevision` (e.g., 1 instead of 2), which the server may misreport as a config conflict.

Fix: In the `useEffect` that syncs form data from updated group data, add:
```ts
if (!dirty.current && typeof group.revision === 'number') draftRevision.current = group.revision;
```
and add `group.revision` to the effect's dependency array. This advances the version only when the user has no pending edits, preserving real concurrent-edit conflict protection.

Verification: Add regression tests in `__tests__/ChatGroupSettings.test.tsx` covering (1) after a save refreshes the revision, a second submit carries the latest `expectedRevision`; (2) an external update arriving while the form is dirty keeps the old revision so genuine conflicts still trigger. Do NOT remove `expectedRevision` validation — that would lose protection against concurrent modifications by other members.

Question 3

Why do numbered files sort wrong in Cindy file browser (10 before 2/3) and how to fix it?

Accepted Answer

This was a known bug: the file tree sorted names as plain strings, so numbered files appeared as `01, 02, 10…29, 3, 30` (and `chapter10` before `chapter2`). It was fixed by PR #7069: the shared scanner in `packages/file-browser-core/src/scanner.ts` now uses `Intl.Collator(undefined, { numeric: true })` for natural sorting, keeping directories first, preserving lowercase normalization and locale rules, and falling back to the old text comparison for equal-value numbers (`1`, `01`, `001`). To get the fix, update Cindy to a build that includes PR #7069; for SSH remote browsing the remote file-service bundle was bumped from 0.2.6 to 0.2.7, so old remote installs auto-upgrade and receive the corrected ordering.

Question 4

Why does the microphone icon become invisible during voice recording in React Native even though the button still works?

Accepted Answer

The recording-state code switches the icon color to an inverted text color designed for solid backgrounds (e.g., `colors.ctaText`) without giving the `Pressable` a background, so the icon blends into the card surface (white-on-white in light theme, near-black-on-black in dark theme) while the hit area, state, and accessibility label still work. Fix in `apps/mobile/src/session/InteractionPanel.tsx` (`AskCardVoiceButton`): when `listening=true`, add a solid capsule background to the `Pressable` — `backgroundColor: colors.cta` and `borderRadius: radius.pill` — and keep the icon on `colors.ctaText`. Alternative: change the recording-state icon color to a foreground color such as `colors.textPrimary` instead of the inverted `ctaText`. Add a regression test asserting that the listening-state `Pressable` has a non-transparent `backgroundColor`, since tests that only check testID/label/disabled cannot catch contrast failures.

Question 5

Why is the microphone icon invisible during voice recording on the question card (mobile app), and how to fix it?

Accepted Answer

The microphone icon disappears in recording state because `AskCardVoiceButton` (in `apps/mobile/src/session/InteractionPanel.tsx`) incorrectly used `colors.ctaText` for the icon color. `ctaText` is an inverted foreground color (white `#FFFFFF` in light mode, dark `#121212` in dark mode) designed only for solid CTA-button backgrounds. Since the voice button has a transparent background over the card color `surfaceElevated` (`#FFFFFC` light / `#1E1E1E` dark), the icon became white-on-white in light mode and dark-on-dark in dark mode.

Fix (PR #7078, closes #6778): change the recording-state icon color to always use the neutral `colors.textSecondary` instead of `colors.ctaText`. The transparent background, 44×44 hit area, icon size, loading indicator during start, and start/stop/submit behavior remain unchanged. A regression test in `apps/mobile/src/__tests__/InteractionPanelReceipt.test.tsx` covers recording visibility and stop-restore across light/dark themes for all three entry points (free answer, custom collapsed, custom expanded).

cindy

Core Features

What It Can't Do

Use Cases

Tags

Getting Started

Similar Projects