Setup and connections
Open the workspace
The visual editor runs in your browser. Create an account, open the application, and create a workspace and network. Start with a small sample that does not contain customer data.
Connect a model provider
Open Integrations and add the API key for the provider you intend to use: Gemini, OpenAI, Anthropic, xAI or Mistral. You can also configure a custom model provider with its endpoint, key reference and model identifiers.
Select that provider and an available model in your Conversation node. Model usage is billed by the provider under your credentials, separately from your NodeFox subscription. Set provider-side spend limits before running loops or batches.
API keys are stored separately from workspace content in browser IndexedDB, with the application's encryption service. OAuth connections use a separate server-side connection path. Avoid placing secrets in prompts, node content, screenshots or logs. See Security for the data and credential boundaries to review for a deployment.
Register files and directories
Use the workspace's file controls to register the files or directories the workflow needs, and grant access when the browser prompts. File-system access depends on browser support and permission; reopen a handle if the browser asks you to grant access again.
Reader and Writer paths resolve against these handles. A Writer path beginning with ./, such as ./summary.txt, requests a browser download. See file path conventions before using real operational files.
Configure the workspace
Settings contains workspace controls for local shell access, outbound network access, logging, audit output, auto-save, backups and budgets. Configure only the capabilities your workflow needs. Model credentials and OAuth connections belong in Integrations.
Local gateway (optional)
The gateway connects the browser to locally running tools and shell commands. The current implementation uses an authenticated WebSocket connection; its default port is 3001.
- Obtain the gateway distribution appropriate to your deployment from NodeFox. For a supplied source checkout with dependencies installed, the entry point is
node scripts/gateway.cjs. - Start the gateway on the machine that will run the tools.
- In Settings → Security, paste the Gateway Access Token printed at startup and set Gateway Port if it differs from the default.
- Configure the MCP server in the MCP view and attach the tools needed by your workflow.
- Enable Local Shell for Code Nodes only in trusted workspaces that need terminal access.
Gateway token and port settings apply to the browser. Shell and other workspace permissions apply to the individual workspace. Keep the token private and use the gateway's origin restriction when configuring a deployment. The browser's current MCP bridge uses the gateway for both local stdio tools and configured remote tool connections.
Check the connection before scaling
Run one read-only example, inspect its output, and confirm its error behavior. Then follow the Quickstart. For unattended execution and its separate host requirements, see Headless execution.