This guide builds a safe first workflow that writes Hello from BaudBound to the runner log. It uses a Manual trigger and a Log action, works on every supported target runtime, and does not modify files or control the desktop.
You need:
You do not need an account. Install the runner by following Installation and Updates, then return here. The runner creates its configuration and storage automatically on first launch.
Hello BaudBound.The project name identifies the workflow in the editor and becomes the default package name. Target runtimes state exactly which runner environments may execute the package.
Hello from BaudBound.Ctrl+S.The canvas should contain one path:
Manual -> Log
The Log action writes to BaudBound's run log. It does not print into an unrelated terminal or create a text file.
The project now appears on the editor's Projects screen. You can return to it later from the same browser profile.
A successful run shows a verification result with no blocking failures and a log entry containing:
Hello from BaudBound
If verification fails, do not export yet. Confirm that both nodes are connected and the Log message is not empty. Verification and Simulation explains the full result categories.
Your browser downloads a file ending in .bbs. The exact filename is shown by the browser. Keep the file intact: the runner records a hash of the imported package, and later file changes invalidate that installed revision.
The next steps use the BaudBound runner. If it is not installed yet, follow Installation and Updates, then return to this step.
On Windows, open BaudBound from the Start menu and confirm that the Dashboard appears.
On Linux, open a terminal and confirm the runner is available:
baudbound --version
The command should print the installed version. Run baudbound to open the desktop application.
.bbs file.The script row shows the installed name and identity. Use that displayed name for later CLI commands. It may differ from the downloaded filename.
Open PowerShell on Windows or a terminal on Linux. Replace PACKAGE with the actual path to the downloaded .bbs file.
baudbound script import "PACKAGE"
baudbound script list
The import command prints the installed script name and ID. In the remaining examples, replace SCRIPT with either value.
Inspect the package before approving it:
baudbound script inspect SCRIPT
Approval accepts the exact imported package hash and its declared access. An updated package must be reviewed again.
In the desktop application, choose Approve from the approval review, then choose Run on the script row.
The equivalent CLI commands are:
baudbound script approve SCRIPT
baudbound script run SCRIPT
Open Runs or Logs in the desktop application, or run:
baudbound script logs --script SCRIPT --limit 5
The latest successful run should contain Hello from BaudBound.
Do not approve or run the package when:
Start with Runs, Logs, and Troubleshooting if the expected result does not appear.