NodeFoxLocal-First File Access
Files & Permissions
Connect local files and folders to a workspace without uploading them to a server. NodeFox uses the browser's File System Access API, so every handle re-confirms permission each session and you can see exactly what is Ready, Locked, or Disconnected. Run outputs land in session-only Virtual Files that expire after an hour, and access for Code Nodes and outbound domains stays under explicit controls you set.
File System Access
Restore All Access| Name | Type | Status | Actions |
|---|---|---|---|
customer-exports/ | directory | Loading | |
Q3_revenue.csv | file | Loading | |
vendor_contracts.pdf | file | Loading | |
pipeline_config.json | file | Loading | |
legacy_archive/ | directory | Loading |
Virtual Files
Session-only — expires after 1 hour| Name | Type | Size | Expires | Actions |
|---|---|---|---|---|
enriched_leads.csv | text/csv | 842 KB | 58 min | |
run_summary.json | application/json | 12 KB | 41 min |
File System Access
Linked — never uploadedRun outputs expire automatically after 1 hour — nothing piles up.
Files that stay on your machine
Add files or folders through the File System Access API and they're linked, not uploaded. Each handle is persisted locally and re-checks browser permission whenever you return — showing Ready, Locked, or Disconnected — so you can Grant Access or Re-link in a click. Network runs write results to Virtual Files, an in-session store that automatically expires after one hour, keeping generated data from piling up.
Code Node · enrich_leads
Security
Enable Local Shell for Code Nodes
Only enable for trusted workspaces.
Domain Access
Allow All
No restrictions on outbound requests
Allow Listed Domains
Only allow requests to specified domains
Block All
No outbound requests allowed
Explicit access controls
Per-workspace security settings decide what a network is allowed to reach. Local Shell for Code Nodes stays off until you opt in for a trusted workspace, and Domain Access lets you Allow All, restrict to a listed-domains allowlist, or block outbound requests entirely for Reader, Writer, and Code nodes. Combined with per-session file permissions, access stays scoped and visible instead of hidden in scripts.
Keep your files where they belong
Link local data without uploading it, let run outputs expire on their own, and gate shell and network access behind controls you set per workspace.