FeedMob CLI (fm)

fm is the command-line interface for FeedMob services. It manages isolated credentials for Pixel, Time Off, Femini, and Pages, verifies authentication, and issues safe, service-specific API requests — with stable JSON output designed for scripts and automation.

fm doctor
fm version
fm pixel auth login [--token-stdin]
fm pixel auth status
fm pixel auth logout
fm pixel request get <path>
fm time-off auth login [--token-stdin]
fm time-off auth status
fm time-off auth logout
fm time-off request put <path> --json-file <file>
fm time-off request get <path>
fm femini auth login [--token-stdin]
fm femini auth status
fm femini auth logout
fm femini request get <path>
fm pages auth login [--token-stdin]
fm pages auth status
fm pages auth logout
fm pages list [filters]
fm pages show <owner> <slug>
fm pages stats
fm pages publish --owner <owner> --html-file <file> [options]
fm pages update <page-id> [options]
fm pages share enable <page-id> [--rotate]
fm pages share revoke <page-id>
fm pages asset upload <image-file>
fm pages request get <path>

Installation

Homebrew (macOS and Linux)

brew tap feed-mob/tap https://github.com/feed-mob/feedmob-cli.git
brew install feed-mob/tap/fm

Prebuilt binaries ship for macOS arm64/x86_64 and Linux arm64/x86_64:

• macOS 11+ on Apple Silicon, macOS 10.12+ on Intel (built and tested on macOS 15 runners);
• GNU/glibc >= 2.35 on Linux, i.e. Ubuntu 22.04 or newer; Alpine/musl and Windows are not supported.

No Ruby installation is required. On first run the binary downloads its ~11 MB runtime image once (SHA-256 verified, cached in ~/.tebako/runtimes/), so the first invocation needs access to github.com; TEBAKO_RUNTIME_MIRROR (https or file://) can point at an internal mirror.

Upgrading or uninstalling the formula never touches stored credentials; run fm <service> auth logout first if you want them removed.

From source (development)

Requires Ruby 3.2+:

bundle install
make install-local
export PATH="$HOME/.local/bin:$PATH"
fm version

Configuration

Each service keeps its own credential, resolved in this order:

1. The service's environment variable;
2. The macOS Keychain, or an AES-256-GCM encrypted local store elsewhere;
3. Unconfigured.

Service	Token env var	Default endpoint	Identity endpoint	Logout behavior
Pixel	FEEDMOB_PIXEL_TOKEN	https://feedmob-pixel-dashboard.feedmob.com/rails	GET /api/v1/cli/me	Revokes remotely, deletes local store
Time Off	FEEDMOB_TIME_OFF_TOKEN	https://time-off.feedmob.com	GET /api/v1/me	Deletes local store only
Femini	FEEDMOB_FEMINI_TOKEN	https://assistant.feedmob.ai	GET /clients.json?name_cont=__feedmob_cli_auth_probe__	Deletes local store only
Pages	FEEDMOB_PAGES_TOKEN	https://pages.feedmob.com	GET /api/me	Deletes local store only

# Interactive, hidden input; the token never appears in argv or history
fm pixel auth login
fm pixel auth status

# Explicitly read from stdin, for automation
printf '%s' "$FEEDMOB_PIXEL_TOKEN" | fm pixel auth login --token-stdin

Endpoints can be overridden with FEEDMOB_PIXEL_BASE_URL, FEEDMOB_TIME_OFF_BASE_URL, FEEDMOB_FEMINI_BASE_URL, and FEEDMOB_PAGES_BASE_URL. Overrides must use HTTPS; plain HTTP is only accepted for loopback addresses (localhost, 127.0.0.1, ::1) together with an explicit FEEDMOB_ALLOW_INSECURE_HTTP=1 — never set that variable in shared or production environments.

Usage

fm doctor checks each configured service against its identity endpoint and reports what still needs configuration:

fm doctor
fm pixel request get /api/v1/cli/me

request get only accepts relative paths starting with a single /; absolute URLs and //host paths are rejected so tokens can never leak to an unconfigured host. Only GET requests are exposed.

Time Off journal updates use the existing request command. Write the JSON request body to a file, then call the documented upsert endpoint; it always writes to the user represented by the configured Time Off token:

printf '%s' '{"content":"Completed API integration"}' > journal.json
fm time-off request put /api/v1/journals/2026-08-31 --json-file journal.json

Femini uses the documented Bearer Token authentication: obtain the token from the Profile menu in Femini, then run fm femini auth login. Femini does not document a dedicated identity endpoint, so login/status use a filtered, read-only clients request as an authentication probe and never print its response. Femini API tokens have no documented prefix requirement.

Pages uses a personal API key from Pages Console → Connect AI. The key is sent as a Bearer token and is isolated under FEEDMOB_PAGES_TOKEN / the Pages Keychain entry. The documented Pages lifecycle operations are intentionally limited to list, detail, stats, publish, update, external sharing, and image uploads; delete, restore, revert, and claim are not exposed by fm.

printf '%s' "$FEEDMOB_PAGES_TOKEN" | fm pages auth login --token-stdin
fm pages list --scope mine --q growth
fm pages publish --owner growth --html-file report.html --visibility unlisted
fm pages asset upload chart.png

publish requires --owner and --html-file. update accepts an HTML replacement with --html-file, small find/replace changes from --edits-file, and optional metadata; the HTML replacement and edits are mutually exclusive. Advanced data_sources and multi-file site payloads are accepted from JSON files with --data-sources-file and --files-file.

JSON output

With --json (accepted anywhere on the command line), every command prints a stable JSON envelope to stdout, including errors:

{"ok":true,"data":{"service":"pixel","authenticated":true}}

{"ok":false,"error":{"code":"credential_missing","message":"No Pixel credential is configured."}}

Security notes

• No --token flag: credentials never enter shell history or process argv;
• On macOS the Keychain is read and written directly via Security.framework; elsewhere an AES-256-GCM encrypted store is used (directory 0700, key/ciphertext/lock files 0600, atomic writes under a file lock);
• Full tokens never appear in logs, JSON output, or error messages;
• Requests go only to the configured service host over HTTPS; loopback HTTP requires an explicit opt-in;
• Generic request commands remain GET-only. Pages write operations are explicit, field-validated commands rather than a generic write-API escape hatch.

Troubleshooting

• "Could not read/save … macOS Keychain": the login keychain is locked (common after a macOS password change). Unlock it with security unlock-keychain login.keychain-db or via Keychain Access, then retry.
• Gatekeeper blocks a browser-downloaded archive: the binaries are unsigned by design. Installing through Homebrew is the supported path — formula downloads carry no quarantine attribute, so Gatekeeper is not triggered.
• tebako-bootstrap: WARNING … unsigned v1 (legacy) tpkg trailer on stderr: expected with the current Tebako toolchain; it is informational and does not affect JSON stdout or exit codes.
• First run fails offline or through a proxy: the runtime image download needs github.com access once; set TEBAKO_RUNTIME_MIRROR to an internal mirror if needed.

Development and releasing

See docs/development.md for local setup and testing, and docs/release.md for the Tebako/Homebrew release pipeline and maintainer workflow.