Skip to main content

Network access and credentials

This page describes macOS workbenches, which run in Tart VMs. On Linux, workbenches run on your computer directly and none of these settings apply (see Linux hosts).

Network access​

Each profile has an egress tier, set in the profile editor's Egress section:

TierWhat it does
defaultThe VM's local-only policy. While you're signed in to Kenaz, the workbench is treated as allowlist instead: it can reach your sign-in server and the destinations allowed for this profile (its apps and connectors).
allowlistThe VM may reach the destinations allowed for this profile.
air-gappedAll outbound traffic from the VM is blocked. Kenaz adds no destinations, and connectors are turned off.

The rules are set in the VM's firewall when the workbench starts. A change to the allowed destinations takes effect when the workbench restarts.

Allowed destinations​

On the allowlist tier, the allowed destinations are the combination of:

  1. the endpoints you add (in Egress, or in the profile's Context Bridge);
  2. the profile's egress preset, if you pick one;
  3. the hosts each selected app needs (for example, Warp needs app.warp.dev and api.warp.dev);
  4. the hosts needed by the MCP connectors the profile allows.

An endpoint is a host name or an IPv4 address, a port and a protocol (TCP by default). Wildcards, URLs and paths aren't accepted. The VM looks up host names when it starts.

There's one preset, Developer workbench. It allows these hosts on port 443:

GroupHosts
Go modulesproxy.golang.org, sum.golang.org, storage.googleapis.com
GitHubgithub.com, api.github.com, codeload.github.com, objects.githubusercontent.com
npmregistry.npmjs.org
Anthropicapi.anthropic.com, claude.ai, console.anthropic.com, statsig.anthropic.com, claude.com, platform.claude.com

Picking a preset on a profile that's on the default tier switches it to allowlist.

When a connection is blocked​

When the VM's firewall blocks a connection, Kenaz tells you:

  • the workbench window's top bar shows a badge such as 3 blocked · example.com, with the list of blocked destinations in its tooltip;
  • the Workbenches list marks the workbench and shows a banner with the blocked destinations, which you can snooze;
  • the Egress view lists Recently blocked destinations, each with an Allow host button.

Allowing a host adds it to the profile. Restart the workbench to apply it.

Credentials​

Provider keys​

When a profile includes an app that needs a model provider, such as the Kenaz Harness, the profile editor shows an AI provider section. The choices are Anthropic, OpenAI, OpenRouter, an open or local endpoint, or Defer. With Defer, the Harness starts without a provider and says so.

Kenaz stores provider keys in your operating system's keychain; the profile holds only a reference to the key. When the workbench starts, Kenaz reads the key from the keychain and passes it into the VM as an environment variable, ANTHROPIC_API_KEY, OPENAI_API_KEY or OPENROUTER_API_KEY. The key is used from inside the VM, so allow the provider's API host in the profile's egress settings (the Developer workbench preset includes api.anthropic.com).

Environment variables​

In the profile's Context Bridge, you can give the workbench named environment variables, for example a GITHUB_TOKEN. For each one, Kenaz uses the value saved in the profile if there is one, and otherwise the value of that variable in Kenaz's own environment when the workbench starts. Only the variables you name are passed in. A provider key with the same name replaces the variable's value.

Kenaz has no separate setting for git or SSH credentials; use an environment variable if a workbench needs a token.

MCP connector credentials​

Credentials for the MCP connectors a profile allows are read from the keychain when the workbench starts and passed into the VM. On the air-gapped tier, none are passed.

How values reach the VM​

Kenaz writes these values, with a few settings the workbench needs, to a small read-only disk that it attaches to the VM when the workbench starts. They're read again at each start, so a changed key or variable applies the next time you start a workbench.

Signing in inside a workbench​

If you're signed in to your Kameas account in Kenaz, a workbench gets a short-lived access token when it starts. The Harness in the VM asks Kenaz for a fresh token when it needs one; your refresh token stays in Kenaz on your computer. If you start a workbench while signed out and sign in later, the workbench picks up the sign-in.

Clipboard​

The profile's Context Bridge has two separate switches: Host → VM clipboard paste and VM → Host clipboard copy.