brand-manager-worker

The Goose Tools brand worker — one daemon serving Brand Manager (inbound: reads your brand email, drafts replies in your voice) and Brand Outreach (outbound: researches brands you want to work with and drafts the pitch). It runs on your computer using your own Claude account — so there's no API key and nothing to pay for beyond the Claude subscription you already have.

It never sends anything. Every reply is created as a Gmail draft for you to review. The Gmail permission granted doesn't include sending, and no code in this package calls Gmail's send endpoint.

Setup

You don't normally run these by hand — https://goosetools.com/dashboard/brand-manager gives you a one-line command with your token in it. For reference:

npm install -g @anthropic-ai/claude-code   # the thing that writes your replies
claude                                     # once, to sign in — then type /exit

npx --yes brand-manager-worker install --token gt_…

install registers a background service that starts with your computer. You don't need to leave a terminal open.

npx --yes brand-manager-worker@latest status     # what's running, recent logs
npx --yes brand-manager-worker@latest update     # pull the newest version, restart
npx --yes brand-manager-worker uninstall         # remove it

One token connects your computer to every Goose Tools worker. If you've already set up the Carousel or Caption worker, install here needs no --token.

Where your stuff lives

Everything personal is on your machine, in ~/.goosetools/brand-manager/:

base/       prompt files synced down from Goose Tools — don't hand-edit, they get overwritten
voice/      how you write to brands
playbook/   rate-card.md and your negotiation moves
deals/      one markdown ledger per brand: terms, dates, what's outstanding
stats/      your media-kit numbers and screenshots
drafts.md   every reply it has drafted
state.json  which threads it has already handled

These are ordinary files. You can open the folder in Claude Code and talk to the agent directly — "bump my Reel rate", "what did this brand agree to?" — exactly as you would in the standalone brand-manager repo. The website is a view onto these files, not the other way round.

Your email bodies and contracts are never uploaded. What the site stores is thread metadata (who, subject, when), your ledgers and knowledge files, and the drafts the agent wrote.

Development

node worker/index.js --url http://localhost:3000 --token gt_…

Config precedence: command-line flags → environment → worker/.env → ~/.goosetools/env.