4 phút đọc
bex-co/beancount-io: 💰 Double-entry bookkeeping made easy — plain-text accounting for humans and AI agents. Pol – Repository bex-co/beancount-io. Mô tả: 💰 Double-entry bookkeeping made easy — plain-text accounting for humans and AI agents. Polished iOS & Android app built with React Native + Expo.. 302 stars, 37 forks, ngôn ngữ chính TypeScript, cập nhật 2026-10-15.
1. Repository làm gì?
Your money in plain text forever — beautiful reports, a phone app, a terminal CLI, and AI agents that can actually do your books. No lock-in. No database you can't read. Your ledger is a .bean text file you own, diff, and back up with Git — Beancount.io just makes it effortless to use everywhere.
▶ Try the live demo — no sign-up · Sign up and record a transaction · ⭐ Star to support open finance
Turn a plain-text ledger into reports you can explore — open the live example.
No install. No empty-ledger setup. Just record your first real transaction:
That's the whole idea: double-entry books you can read as plain text, with reports, phone, terminal, and agents on top of the same ledger.
If Beancount.io is the kind of open, programmable finance you want more of, ⭐ star this repo — it genuinely helps other developers find it.
2. Dữ liệu và cấu trúc đáng chú ý
You don't install Beancount yourself — one command installs bea, which provisions its engine for you.
Checking now holds 987.50 USD — validated, formatted, and readable as plain text.
Not sure yet? The live demo needs no account — decide there.
Beancount.io stands on Beancount and Fava rather than replacing them — existing ledgers keep working. Full credits: ACKNOWLEDGEMENTS.md.
Review your finances, add transactions, scan receipts, and edit ledger files from the native Beancount client. The same open ledger remains available from the web, terminal, Python, and agent workflows.
Explore the mobile product tour or run the Expo app locally.
Your ledger stays the same plain-text file across all of them — hosted or local-first, with no hosted service required for CLI and skills workflows.
3. Khả năng ứng dụng và giới hạn
The dashboard and mobile app are clients for the Beancount.io API served by backend-cluster/ — hosted, or self-run. Skills have two audiences: Beancount users get skills/; repository contributors get .agents/skills/ (see .agents/AGENTS.md). The root .claude/skills links to .agents/skills so Claude Code and Codex share the internal workflows.
Beancount.io is built for the agent era: your ledger is text an agent can read, and every write is validated and reversible.
Thirty tools (BQL queries, file reads/edits, entry and receipt insertion, statement parsing, bank import, and more), 64 URI-addressed resources, and four prompts (spending report, month-end close, reconciliation, import categorization — e.g. /mcp__beancount__close-month in Claude Code). Every write supports dry_run, every call re-authorizes, and failures return a machine code plus the next call to make. Per-host notes for Claude, Claude Code, ChatGPT, Cursor, and Copilot: MCP docs; contract: ADR 0007.
Yes. Your ledger is a plain-text file. Local CLI and skills workflows never require the hosted service; if you self-host, everything runs on your server. You choose where the file lives.
Beancount.io builds on both (Fava ships inside the CLI). It adds native mobile apps, a one-install CLI, hosted or self-hosted collaboration, and first-class agent workflows — while your .bean files remain standard Beancount that Fava and other tools can still read.
Yes — the migration guide converts an export and keeps importing without duplicating transfers.
No. Use the hosted service at beancount.io, run everything locally with the CLI, or self-host on one server with deploy/docker/. Same ledger either way.
There is no root package to install; each package owns its dependencies and checks.
Web dashboard (Node.js 22, Yarn 4 via Corepack, plus a Beancount.io API endpoint):
Số liệu repository có thể thay đổi; nên mở liên kết nguồn để kiểm tra README, giấy phép và trạng thái phát hành.
Nguồn tham khảo: Xem bài gốc
