Bring a profile from your workflow.

These tools create the same importable JSON profile as the browser editor. They ask for public fields; they do not infer what you want to share.

Visual Studio Code

1. Install the approved development VSIX when provided through the download page. It is not a published Marketplace extension.
2. Open the Command Palette and run Nowbeam: Export Public Profile.
3. Enter a public name, description and optional HTTPS link. Cancel any prompt to stop without writing.
4. Choose a file location, then import the profile in Nowbeam. Sharing is paused by default.

The extension package and isolated CLI installation have been checked. The command’s installed GUI workflow still requires a runtime check.

Terminal, iTerm2 or PowerShell

The optional source CLI requires Node 22 or later. The desktop app itself does not. From an authorized source checkout:

node packages/inputs/cli.mjs --name "My public project"   --description "Building the next release"   --url "https://example.com" --output public-profile.json

The CLI refuses existing output files and symlink targets. It reads only named arguments—not your working directory contents, shell history or environment.

Running-app labels

The desktop app also offers an explicit running-app input. Choose an app, enter a public label and opt in. It detects an exact app identity without reading document names or prompts. Pause disables that input. iTerm2 on the Mac development host has been exercised; other platform/app combinations need their own checks.