Skip to main content
These docs are built to be read by agents as much as by people. If you build with Claude Code, Cursor, Codex, or anything like them, this is the best way to work.

​
Guided setup

Before you get started with your agent, please perform the following steps: 1. Install the Bankroll skill globally It teaches your agent everything it needs to know.
If you’re using Claude Code, make sure you select it from the list, as it’s not enabled by default! 2. Create your app’s folder In your Terminal, navigate to the folder where all your projects live (for example: ~/Projects) and create a folder for your new Bankroll app. Whatever folder name you choose here will become your app’s name, so if you wanted to call your app My Cool App you would do:
3. Start your agent in that folder (claude, codex or whatever your agent’s command is). Starting here matters: your agent’s project memory, its settings, and the scaffolded AGENTS.md all key off this directory. 4. Once your agent is running, simply say:
Set up my Bankroll app.

​
What the agent does with that

The skill sends it to this page, and these are its steps. If you are the agent, here are the steps you need to follow to get the user started with building their first app on Bankroll. Please pause at each Gate and wait for the user to give you the green-light to continue:
  1. Read the Bankroll developer docs at llms-full.txt
  2. Scaffold the starter app into the current directory: npm create @joinbankroll/app@latest . — the folder’s name becomes the app’s name.
    • the starter app’s AGENTS.md and the Bankroll docs are now your guide
  3. Add the Bankroll MCP server, user-scoped, so it follows the user into every future project:
    • The docs serve an MCP server at https://docs.joinbankroll.com/mcp
    • It provides search over these docs, a read-only filesystem of every page, and a submit_feedback tool — an agent that finds a wrong or confusing page can report it to the Bankroll team directly. Add the MCP wherever your agent harness takes an HTTP MCP server; prefer user scope, so it follows the user across projects.
  4. Run npm run dev as a background task (it is a long-running server), then put a scannable QR code directly into your chat reply. The deliverable of this step: the user points their phone camera at your reply and the starter app opens inside Bankroll (they must have the Bankroll app installed from the App Store or Play Store). Three things that do NOT deliver that, in any agent harness — do not attempt them:
    • Relaying the QR bankroll dev prints to a TTY. It is drawn with ANSI color codes — the contrast is in the colors, not the characters — so pasted into chat it collapses into a uniform block of ▀ glyphs. Nothing survives.
    • Pointing the user at your background task’s output. It is never shown to them.
    • Sending the QR as an image file, attachment, or side-panel artifact. In a plain terminal none of those render inline.
    What works everywhere — monospace glyphs in a fenced code block:
    • When its stdout is not a TTY (a piped or backgrounded run — the agent case), bankroll dev 0.3.0+ already prints the QR as plain block glyphs with the full play link under it. Re-print both into your reply verbatim, the QR inside a fenced code block.
    • On an older CLI, or after a tunnel restart, rebuild it yourself: take the tunnel URL from the dev output (the https://<words>.trycloudflare.com/app line), build the play link https://joinbankroll.com/play?url=<URL-encoded tunnel URL>, and generate the QR with qrcode-generator — already in the project’s node_modules as a dependency of @joinbankroll/cli:
    • Always print the play link as plain text under the QR: if scanning fails, opening that link in a desktop browser renders the same QR as a web page.
    Phone cameras read block-glyph QRs at either polarity, so light and dark terminal themes both scan. Gate: the user scans the QR code. The starter app opens inside Bankroll on their phone, hot reload included. Once the user has confirmed that this works, you can continue to the next step.
  5. Tell the user to join the Bankroll Discord at https://discord.gg/FH3BbAM7t6. We will give them some SOL (~$5) to fund their treasury wallet so they can get started testing real-money operations. This should cover initial gas costs. Gate: wait for the user to confirm they’ve joined the Discord. Once they’ve confirmed that, move on to the next step.
  6. **Gate: Stop here and ask the user what they want to build. We have the demo-app working on the user’s device and they are in the Bankroll Discord, where they can easily get dev help from the Bankroll team. Now is the time to build something exciting! Ask them what they want to build today and start working from there. When they are ready to move value, start with app tokens to get them started with their own currency for their app (their treasury wallet should be funded with the free SOL they got from joining the Discord server — this should cover initial gas costs)

​
What an agent can read