Reference

Look it up: the app, the platforms, the commands, and every message.

Reference pages describe the machinery as it is: system requirements, the app screen by screen, what Blowhorn does on each platform, the content queue, jobs, the command reference, profiles, settings, messages and exit codes, extension permissions, plans and limits, release notes, and where to get help.

The command reference is generated from the app itself, so it always matches the build you run.


System requirements

What your Mac needs to run Blowhorn: macOS version, Chrome, and a Layer5 Cloud organization.

The Blowhorn app, screen by screen

The menu-bar popover, the console screens, Setup, Settings, and what each one does.

Platforms

What Blowhorn does on each platform: actions, browser or API, sign-in, and limits.

Content queue columns and row states

Every content column, what each platform reads from a row, and what each row state means.

Job options and schedules

Schedule rows, recurrence words, driver mode, and the three pause scopes.

CLI reference

Every command, the shared flags, and profile resolution.

`blowhorn post` reference

The posting command in full: pending rows, every flag, and per-platform behavior.

Profile reference

What a profile is: its directory, its store row, its keys per platform, and the Chrome column.

Configuration reference

Precedence, every .blowhorn.yaml option, environment variables, and output logging.

Messages and exit codes

Every refusal sentence keyed by its first words, with the cause, the fix, and the exit code.

Chrome extension permissions

Each permission the Blowhorn extension asks for, the sites it runs on, and why.

Plans and limits

Blowhorn is free during early access, with no tiers and no per-action charges.

Get help

Where to look first, how to report a problem, and how to report a security issue.

Chrome reference

The mapping commands, the two launch modes, the extension default, and Linux differences.