finsafe version
0.9.42
Platform
- Windows 11 Pro, build 26200 (NT 10.0.26200.9168)
finsafe probe highlights: appcontainer_works=true, helper_installed=false, conpty_present=true
Component
Personal CLI — finsafe visual-sandbox (File vault tab, sandbox-off side)
Steps to reproduce
- Start the UI:
finsafe visual-sandbox --port 8787
(In this report the shell had TEMP/TMP/TMPDIR redirected to C:\Users\xuls2\AppData\Local\FinSAFE\hermes\tmp, so the demo kit was created there — the startup banner prints the kit path.)
- Open
http://127.0.0.1:8787, go to the File vault tab.
- Pick a preset target, e.g. the salaries CSV, and click Run comparison.
- Look at the command shown/executed on the sandbox-off side.
Server startup banner (kit path):
FinSAFE visual sandbox on http://127.0.0.1:8787
Kit: \\?\C:\Users\xuls2\AppData\Local\FinSAFE\hermes\tmp\finsafe-visual-sandbox-kit
The target file exists at:
\\?\C:\Users\xuls2\AppData\Local\FinSAFE\hermes\tmp\finsafe-visual-sandbox-kit\vault\HR-Salaries-2026.csv
Expected behavior
The generated command should reference the actual demo-kit directory created by the server (finsafe-visual-sandbox-kit, or whatever the server reports in the Kit banner) using a resolvable path (absolute, or relative to a fixed working directory), so the target CSV is actually read.
Actual behavior
The sandbox-off side generates and executes:
cmd /C 'head -c 4000 '\''demo-kit\vault\HR-Salaries-2026.csv'\'''
Problems:
- The directory name
demo-kit does not match the directory the server actually created, finsafe-visual-sandbox-kit — the file cannot be found.
- The path is relative with no
cd to a defined working directory, so its resolution depends on whatever the process cwd happens to be.
Result: the "sandbox off" side of the comparison cannot read the intended file.
Additional context
- The server-created kit directory name (
finsafe-visual-sandbox-kit) comes from the startup banner and the /api/health / /api/defaults payloads (demoKitPath), which all agree on finsafe-visual-sandbox-kit. Only the generated command uses demo-kit.
- Suspected cause: the UI's command template uses a hardcoded/assumed kit directory name that differs from the server-side value, and emits a relative path without anchoring the cwd. Passing the actual absolute kit path (or setting the command cwd to the kit parent and using the real directory name) would fix it.
- Same wrong path appears on both the sandbox-off and sandbox-on sides (the sandbox-on side additionally fails to start — reported separately).
finsafe version
0.9.42Platform
finsafe probehighlights:appcontainer_works=true,helper_installed=false,conpty_present=trueComponent
Personal CLI —
finsafe visual-sandbox(File vault tab, sandbox-off side)Steps to reproduce
finsafe visual-sandbox --port 8787(In this report the shell had
TEMP/TMP/TMPDIRredirected toC:\Users\xuls2\AppData\Local\FinSAFE\hermes\tmp, so the demo kit was created there — the startup banner prints the kit path.)http://127.0.0.1:8787, go to the File vault tab.Server startup banner (kit path):
The target file exists at:
Expected behavior
The generated command should reference the actual demo-kit directory created by the server (
finsafe-visual-sandbox-kit, or whatever the server reports in the Kit banner) using a resolvable path (absolute, or relative to a fixed working directory), so the target CSV is actually read.Actual behavior
The sandbox-off side generates and executes:
Problems:
demo-kitdoes not match the directory the server actually created,finsafe-visual-sandbox-kit— the file cannot be found.cdto a defined working directory, so its resolution depends on whatever the process cwd happens to be.Result: the "sandbox off" side of the comparison cannot read the intended file.
Additional context
finsafe-visual-sandbox-kit) comes from the startup banner and the/api/health//api/defaultspayloads (demoKitPath), which all agree onfinsafe-visual-sandbox-kit. Only the generated command usesdemo-kit.