Announcing Sheila

    Announcing Sheila

    An AI agent that replaced our entire accounting flow at Soapbox. Contractor invoices, payments in fiat and Bitcoin, bookkeeping, expense tracking, all handled by one agent built with OpenCode.

    Alex Gleason

    Everybody is building AI agent platforms right now. Agent frameworks, agent marketplaces, multi-agent orchestration engines. Billions of dollars are going into this space. Has anyone actually built ONE agent that works?

    I built one. It's called Sheila, and it replaced our entire accounting flow at Soapbox.

    What It Does

    Sheila handles the full lifecycle of contractor payments. She reads invoices from email, records them in a Google Spreadsheet, sends payments in both fiat (ACH/wire via Mercury) and Bitcoin (via Kraken, Lightning, and Boltz), generates invoice PDFs, archives everything to Google Drive, and submits our expenses to OpenCollective. She also tracks P&L and generates 1099 reports.

    I open a terminal and say "what's the status?" and she tells me what's done, what's pending, and what needs attention.

    Google Sheets payment tracker managed by Sheila
    The payment tracker spreadsheet. Sheila maintains this automatically.

    How I Built It

    I ran OpenCode in an empty folder and just started describing what I wanted.

    This is actually Sheila v2. In v1, I tried to build complex multi-step flows in code. It was fragile and inflexible.

    For v2, I built a toolkit of granular scripts instead. Each one does exactly one thing: check a balance, send a payment, upload a file, append a row to a spreadsheet, read an email. I tested them one by one (over 50 scripts in total).

    Then I wrote AGENTS.md, a 600-line document that describes the workflows in plain English. When I tell Sheila to "process invoices," the agent reads the instructions and chains the right scripts together in the right order.

    Sheila's package.json showing available scripts
    Sheila runs TypeScript scripts to perform various tasks.

    Human Oversight

    Sheila is not fully autonomous. She runs in OpenCode, which means I'm sitting in the terminal watching her work. She can draft an email or prepare a payment, but I see what she's doing before it goes out. This is still a drastic time-saver, and maybe someday Sheila will run fully autonomously.

    OpenCollective expense submitted by Sheila with a comment
    Sheila submits expenses to OpenCollective and comments on them.

    Why OpenCode

    The best tool for building AI agents today is OpenCode, not OpenClaw. Despite the hype around OpenClaw, and despite the fact that OpenCode is marketed as a coding agent, OpenCode is the better tool for this.

    The reason is the human feedback loop. Building a real agent requires constant iteration. You write a script, test it, discover an edge case, fix it. You test the workflow end-to-end, find out the AI misunderstands a step, rewrite the instructions, test again. Hundreds of cycles like this.

    That loop is still essential. Autonomous agent platforms skip it, and that's why their agents don't work in production. They're optimizing for demos where the human walks away. But the work that makes an agent reliable happens in the iterations between the human and the AI. OpenCode gives you that.

    Top-Down vs. Bottom-Up

    The AI industry has a top-down bias right now. Build the platform first, design the abstraction layer, create the marketplace, then hope agents emerge. This is backwards. It's a huge waste of money. You can't build a useful agent platform without first understanding what a useful agent looks like, and you can't understand that without building one from scratch.

    The AI companies that work will be the ones that put in the hard work to build each agent one at a time from the bottom up. Sheila was built that way. Script by script, workflow by workflow, over weeks of iteration.

    Email from Sheila notifying a contractor that payment was sent
    Sheila emails contractors when their payment is sent.

    Make Your Own

    Sheila's exact setup probably isn't a perfect fit for you. You might not use Mercury for banking or pay contractors in Bitcoin or need OpenCollective integration. But the pattern works for anything: build granular scripts, describe workflows in AGENTS.md, iterate with human feedback until it's reliable.

    Fork it and swap the scripts for your own integrations, or start from scratch in an empty folder with OpenCode.

    Sheila is open source under the AGPL.

    Source code: https://gitlab.com/soapbox-pub/sheila