twogether

Shared budget for two people, built with TanStack Start, React, TypeScript, and Bun.

Each person logs what they spend. Shared expenses are split down to the cent, and six goals, which must add up to 100%, plan the couple's combined income.

Live at https://twogether.brunocardozo.com.br. The interface is in Brazilian Portuguese.

Running

Requires Bun 1.3.14+ and Node.js 22.12+ for the build tools. The server runs on Bun and reaches SQLite through libSQL: a local file unless the Turso variables are set.

bun install
cp .env.example .env.local
# Fill in the Clerk keys in .env.local (or run `npx clerk@latest init`)
bun run dev

bun run dev serves the app at http://localhost:3000.

• VITE_CLERK_PUBLISHABLE_KEY and CLERK_SECRET_KEY: Clerk application keys. Development keys can be written by npx clerk@latest init; claim the application with npx clerk@latest auth login before production.
• CLERK_SIGN_IN_URL and CLERK_SIGN_UP_URL: optional, keep Clerk redirects on /entrar.
• TURSO_DATABASE_URL and TURSO_AUTH_TOKEN: credentials injected by the Vercel Turso integration. When present, the server uses the shared remote database.
• BUDGET_DATABASE_PATH: local fallback when Turso is not configured, defaults to ./data/twogether.sqlite.

Restart the server after changing the environment.

Access and couple

1. Sign in on /entrar with your e-mail and the six-digit code Clerk sends. There is no password and no distinction between sign-up and sign-in: the embedded <SignIn /> runs Clerk's sign-in-or-up flow, so an unknown e-mail verifies first and the account is created after the code is confirmed.
2. Sign-in and onboarding live on /entrar. The budget at / and settings at /conta sit under the pathless _authenticated layout and require a session, a name, and a household; anything missing redirects to /entrar. With a name and a household, /entrar continues to /.
3. Invites are links to /convite/<token>. The route handles sign-in or sign-up, returns to the same invite, asks for a name when needed, and only then joins the household. Legacy ?convite= links on / redirect to it.
4. On /conta (Nosso espaço), generate and copy an invite for your partner. The link accepts a single person, expires in 48 hours, and can be canceled. Generating another invalidates the previous one.

Clerk owns credentials, sessions, and e-mail delivery; the instance enables e-mail code only (password and social sign-in are disabled) with strict user enumeration protection, which is what powers the single sign-in-or-up flow. Signing out ends the Clerk session. Both see and edit all couple data; each account belongs to only one budget and the database limits each budget to two people.

Budget

• Transactions with description, amount, date, and goal; each new transaction is automatically associated with the signed-in person and keeps that attribution when edited.
• Us view and individual filters. Each goal's planned amount always uses the couple's total income, even with an individual filter active.
• Six fixed goals with editable percentages that add up to 100%: fixed costs 30%, pleasures 10%, comfort 15%, goals 15%, financial freedom 25%, and knowledge 5%. The split applies to every month.
• Editing, deleting, and undoing per transaction, plus search and filters by goal and type. Amounts in whole cents.
• Original authorship and the last person to edit are preserved.
• Split expenses: turn on Dividir com … on an expense and the other person owes half (rounded down). The payer keeps the full expense. Only the person who owes can mark it paid, picking the date; that records an income for the payer and an expense for the partner. Those repayment entries count in individual views but not in Us, and undoing the payment removes them. A paid split locks its amount, type, split, and deletion until it is unmarked.
• Each change is a validated createServerFn. The workspace seeds TanStack Query from the loader snapshot; saving, deleting, or undoing a transaction updates that cache immediately, then reconciles with the server. Focus, visibility, and reconnect refetch the snapshot so you see your partner's changes. Concurrent edits to the same entry or to the percentages are rejected with guidance to review the current version; independent additions do not overwrite each other. The month lives in the URL (?month=YYYY-MM); the first visit without it redirects to the current month. Each month is its own snapshot (that month plus unpaid splits and the later occurrences of its series), so a page load never carries the whole history; the months next to the one on screen, and any month the reader points at in the picker, load ahead of time.

AI agents (MCP)

The app serves a Model Context Protocol endpoint at /mcp, so an agent (Claude, Cursor, ChatGPT, etc.) can read and manage the budget as the signed-in person.

• Add https://<app>/mcp as a remote MCP server in the agent. On first use it opens the Clerk sign-in; use the same e-mail as in the app. The account needs a name and a household first.
• Tools: get_overview, list_transactions, save_transaction, delete_transaction, restore_transaction, settle_split, unsettle_split, get_goal_percentages, and save_goal_percentages. They call the same store as the app, so revisions, split locks, household isolation, and the per-person rate limit apply.
• Clerk is the OAuth authorization server. Enable Dynamic client registration under OAuth applications in the Clerk Dashboard (development and production instances) so agents can register themselves.
• Clients that only speak stdio can bridge with npx mcp-remote https://<app>/mcp.

여기까지가 README 앞부분입니다. 나머지는 원문에서 읽을 수 있습니다. README 전문 보기 ↗