THE FEE APP

Open Fee. Give it the job. Watch it finish.

Fee is the workspace for coding-agent work: repo context, skill packs, approvals, task progress, verification, and receipts in one place.

Fee applive task
Make the flaky auth tests pass3-step plan · 4 files · awaiting approval
Run verificationpytest, lint, typecheck
Seal receiptfiles, tests, lane, model, tokens, EUR
branch readyapproval visiblereceipt pending

WORKFLOW

The app turns vague work into a controlled run.

1 — Pick a skill

Web design, coding, graphics, social, research, and automation prompts load as compact cached packs.

2 — Approve the plan

Fee maps the repo, proposes files and commands, and waits where the permission mode requires it.

3 — Watch the run

Edits, tests, retries, lanes, cache, and fair-use are visible while the task is running.

4 — Keep the receipt

The final record names what changed, what passed, which lane served, and what it cost.

Your work history should not be a chat scroll.

The app keeps the useful parts: task intent, branch, changed files, verification, receipt, and follow-up context. No hunting through prompts to remember what happened.

Task queueEvery request has state, owner, branch, and next action.
Receipt feedEvery finished task has audit-ready proof.
Skill galleryBig prompts load as cached metadata first, then only the selected pack expands.

The router is under the app, not the story.

Fee tags each step by intent. The gateway chooses from the current approved provider mix, applies fallbacks when needed, and records what actually served the run in the receipt.

Planrepo mapping and task shape
Editfragile diffs and focused fixes
Buildimplementation, tests, repetitive work
Continueextra capacity for eligible work

Use the app. Drop to CLI when your hands are already on the keyboard.

Public npm publication is not live yet. Approved beta users open the protected Fee download page, copy the short-lived install command, and then connect with device login. Desktop downloads remain platform-specific private-beta handoffs. The Get Fee page exposes the protected app route only for the one configured target, while other targets remain request-only.

open https://flatfee.one/download/fee
fee onboard --init
fee login --device
fee "make the failing test pass"

Using Cursor, Claude Code, Aider, or OpenCode? Point them at the same gateway and the app still keeps the receipts.

Is the app included in every plan?

Yes. The app workspace, CLI path, skill gallery, routing policy, and receipt feed are part of the Fee product during beta.

What happens at my fair-use limit?

Eligible work can use the configured continuation lane while capacity and policy allow it. If no eligible capacity remains, a run can pause or return a budget response.

How is this different from a raw coding agent?

Raw agents give you a chat and a meter. Fee gives you a workspace, budget controls, provider routing, and a receipt per task.

Your first app run starts with beta access.

Request access, get the protected install path, connect a repo, and finish your first task with a clear report of what happened.