Muse Task HubUnofficial guide

Money · Official example

Create a spending tracker

Create a spending tracker. Turn spending data into a useful view.

What you can get

What it is

Spending view

A spending view organized by category and date, with missing information flagged.

It came back right when

  • Every total can be opened to show the rows that produced it.
  • Transfers between your own accounts are excluded from spending rather than counted as it.
  • Refunds reduce the category they came from.
  • Duplicate flags are actual duplicates, not a merchant you use weekly.
  • The date range matches your export.

The checks are editorial, not from the source.

Illustration — suggested task flow, not an execution result
  1. Prepare

    Transaction export

  2. Ask and review

    Prepare a transaction export with unnecessary personal details removed.

  3. Check the result

    Every total can be opened to show the rows that produced it.

Editorial, not from the source

Works when

  • You can export transactions as a file.
  • You want totals you can open up and trace back to rows.
  • You are organising your own spending, not making a financial decision on the result.

Does not work when

  • You cannot export and would have to retype the data.
  • The account is shared and the export contains someone else's transactions.
  • You want advice on what to do about the spending. That is yours to decide, or a qualified adviser's.

The source case

Muse maker documentation lists a spending tracker among possible artifacts.

Published by the product maker. Not independently tested here.

Suggested prompt

Bring Transaction export. Acts Nothing outside the chat. Source official example, checked 2026-09-15.

Written by this guide as a starting point, not quoted from the source. Your edits stay in this browser.

What you need

Editorial, not from the source

You supply

  • Transaction export

Connected

  • A transaction export from your bank or card provider

Approved by you

  • Your decision about which personal details to strip out before you share the export

How to try it

Editorial, not from the source

  1. Prepare a transaction export with unnecessary personal details removed.
  2. Specify categories and ask for a tracker with traceable totals.
  3. Reconcile its totals and duplicate flags against your original export.

Limits and confirmation points

Limits to confirm

  • This is organization of records, not financial advice.
  • Transfers, refunds and repeated merchants can be misclassified.

Stop and check

Editorial, not from the source

  • Before you share it: remove account numbers and anything this task does not need.
  • Before you trust a total: open the rows behind it.
  • Before you act on it: remember this organises records, it does not advise.

If it goes wrong

Editorial, not from the source

Totals do not match your statement
Check transfers and refunds first. Between them they account for most of the gap.
A regular merchant is flagged as a duplicate
Ask it to require a matching amount, date and reference before calling anything a duplicate.
One category has become a catch-all
Ask for the rows inside it. A large 'other' usually means the merchant names were not recognised.

Next

The only money task here so far. The other categories.

Get recurring task recommendations — ask your own agent to check for relevant updates.