What we are building, and what we are not.

On the bench

• A chat agent you text

  Shipped. One Telegram bot, linked to your book by a code you generate from the book page. Every turn is metered — what a plan includes is still open (#253).

• A real CSV and statement importer

  Shipped. Deterministic column mapping, server-side, and it returns the mapping it used. Both routes use it — the Claude plugin and the Telegram bot — so the same file gives the same answer every run, and each row carries an import-id so a re-import cannot double-book.

• Receipt photo to transaction

  Shipped. Send a photo and it becomes a proposed transaction, with a separate confidence for the date, merchant, total, tax and currency — anything uncertain comes back flagged rather than guessed. The photograph itself is not archived yet.

• Planned

  Forward a receipt by email

  Your book gets its own address. Forward the receipt there and it becomes a proposed transaction you confirm — nothing is written because an email arrived.

• Planned

  Export your whole book

  It is already a git repository; there is no route that hands you a copy. That is a gap, not a feature.

• Considering

  A read-only demo book

  So "see it in action" goes somewhere real.

What it does not do

• Bank feeds

  No direct connection to your bank. You export a file, or photograph a receipt. That is also why every bank in every country works.

• Payroll and tax filing

  Countbean is books-of-record and bookkeeping. It does not file anything for you, and it is not going to this year.

• A mobile app

  The chat agent is the phone story. A separate app is not planned.

This list is the reason the other one is worth reading.