auto-bean-query

To query Beancount ledger balances, this tool translates natural-language questions into Beancount Query Language (BQL) and executes them with bean-query. It retrieves balances, account activity, and date-bounded summaries from your ledger files without mutating the ledger.

The safest way to run bean-query is using a read-only tool that enforces guardrails for explicit account patterns and access restrictions. This prevents accidental mutations to your ledger.beancount files while fetching balances, registers, and transaction inspections.

Yes, you can inspect specific Beancount transactions without modifying the ledger. The tool executes BQL queries in a strictly read-only scope, fetching transaction history and account activity while ensuring underlying files remain completely unmutated.

Bean-query supports date-bounded summaries for account activity by translating your date range constraints into BQL. The tool fetches period summaries, registers, and balances within specified dates, applying caveats when inventories or costs affect the results.

Limitations of querying Beancount ledgers with BQL include a strictly read-only scope that prevents mutating ledger files or underlying data. Additionally, the tool applies clear caveats when inventories or costs affect query results to ensure accurate ledger analysis.

To discover accounts in a Beancount ledger, the tool translates your natural-language request into BQL and executes bean-query. It retrieves account discovery data, balances, and transaction history from ledger.beancount and included beancount files in a safe, read-only manner.