The Minitally CLI is the simplest integration path for agents that can run shell commands. Xiaolongxia can call the CLI to create expense records, search spending memory, list categories or tags, and read summaries.
The current internal command is source-based:
pnpm --filter @minitally/cli dev --helpWhen a packaged binary is available, the same examples can use:
minitally --helpConfigure the API Key
Prefer environment variables for agent workflows:
export MINITALLY_API_KEY="mnt_xxx"
export MINITALLY_API_BASE="https://mn.hekmon.com"You can also save a local config:
pnpm --filter @minitally/cli dev login --api-key "mnt_xxx"For shared machines or CI-like agent environments, environment variables are easier to rotate and avoid accidental config reuse.
Add an Expense
Xiaolongxia can send one command per confirmed record:
pnpm --filter @minitally/cli dev expense add "Lunch 38 with team" \
--merchant "Noodle House" \
--request-id "xiaolongxia-lunch-20260507-001"For records that should not affect budget progress:
pnpm --filter @minitally/cli dev expense add --amount 120 \
--note "Reimbursable client taxi" \
--merchant "Taxi" \
--exclude-from-budget \
--request-id "xiaolongxia-reimburse-20260507-001"The CLI marks records with the cli source and system tags agent plus cli.
Search and Summarize
Use search before creating duplicates:
pnpm --filter @minitally/cli dev expense search "Lunch" --limit 10Read supporting metadata:
pnpm --filter @minitally/cli dev categories list --type expense
pnpm --filter @minitally/cli dev tags list
pnpm --filter @minitally/cli dev summarySuggested Xiaolongxia Policy
Use this rule in your Xiaolongxia instruction:
Before calling Minitally CLI, extract amount, type, counterparty, time, note, and whether it should be excluded from budget. If amount is uncertain, ask the user. Always set a request-id that includes the agent name and a timestamp.This keeps CLI access fast without letting the agent guess important money fields.

