Blowhorn Download

Agentic AI Marketing

Blowhorn for Codex

Codex follows AGENTS.md and asks before it acts outside its lane. Point it at Blowhorn and keep your finger on approve.

Download for Mac Read the docs

How it works

  1. 1

    Install Blowhorn

    Blowhorn for Mac and the Blowhorn Chrome extension. Your posts go out from your own signed-in Chrome.

  2. 2

    Rules in AGENTS.md, approvals in Codex

    AGENTS.md, codex exec and approvals. A few lines and Codex knows the commands.

  3. 3

    Say what you want

    Codex turns it into blowhorn commands. You approve what publishes.

Rules in AGENTS.md, approvals in Codex

Codex reads AGENTS.md from your repo. Blowhorn needs the network and your Chrome, so sandboxed Codex asks before running it. That's a feature: approve reads, think twice before publishing.

AGENTS.md 
## Social posting

Tool: blowhorn (on PATH). JSON output: add --json.
1. Read: blowhorn schedule list --json, blowhorn content list --pending --json
2. Propose changes as a payload and show me
3. Write with --expected-fingerprint so you never overwrite a newer edit
4. Stop switch: blowhorn schedule pause --all --reason "<why>"

Try saying

  • "Read the last 30 days of operations grouped by host and tell me which Mac is doing the work."

  • "Schedule a daily report row at 08:00 for all profiles. Show the payload before you run it."

  • "Validate every schedule row and fix the ones that fail, one upsert per row."

What Codex runs

terminal 
blowhorn analytics operations --group-by host --since 30d --json
blowhorn schedule upsert --payload '{"Command":"report","Profile":"all","Run At":"2026-10-13 08:00:00","Recurrence":"daily"}' --json
blowhorn schedule validate --json

Where it pays off

Unattended checks

codex exec runs a task without the interactive UI, which suits a morning "what is due, what failed" pass.

Safe edits

Every schedule and content write takes --expected-fingerprint, so a Codex edit is rejected if you changed the row first.

Fleet health

analytics operations --group-by host shows which Mac ran what, so Codex can spot the one that went quiet.

Questions

Why does Codex ask before running blowhorn?

Blowhorn reaches the network and your Chrome. Approving it per command is the sensible default.

Will two Macs post the same row?

Rows are claimed with a lease, coordinated so the same post isn't sent from two Macs.

Does my agent see my social passwords?

No. Blowhorn posts through your own signed-in Chrome; the agent only runs commands and reads their output. Review what you allow it to run, as with any tool that acts on your accounts.

One message out, many ears in

Get Blowhorn for Mac, then let Codex do the talking.

Download for Mac

More agents