FABER is a desktop app for developers who write the spec first. A Card carries its Plan; drop it into a Column and a Claude Code Run builds from that Plan, in its own git worktree, under your own login.
6 default Columns, To-Do to Done. Works with Claude Code, Jira, Git, GitLab and GitHub.
Cards come from Jira or are written here. Each carries its Plan, the spec the work is built from, with its Column, its Worktree and every Run. Open one and the Run's session sits beside the list. See how a Plan is reviewed
SpendWise / Board
Every Run starts from a Plan you approved: a Claude Code session on your own machine, under your own login, in a git worktree of its own. FABER never holds an API key, and the spec it builds from is a file in your repo.
Drop the Card into Plan and a Run writes the spec as a Plan. Approve it, drop the Card into Implement, and the code follows the Plan; Test and Review run on their own. Done proposes the Jira transition.
Drop a Card into Implement and a Run starts at its Worktree root, with the Card and its Plan in the prompt.
Each Card gets its own git worktree, branched from fresh main; Runs of different Cards never collide.
A Plan is draft, approved or superseded; Implement refuses to start until you approve the snapshot you read.
The Sessions view lists each Claude Code session in the Workspace, terminal ones included, and resumes it.
SpendWise / Sessions
The Plan is your spec. The agent writes it from blocks: callouts, diagrams, tables, annotated code and open questions. You annotate a block or a phrase and request a revision; the agent answers each note as addressed or declined.
Each tool opens in the Card's Worktree by default, and in the main clone when no Card is open.
A shell in the Workspace, a Project or a Card's Worktree, in tabs. The Test Column runs the same command the agent ran, in the same checkout.
The Plan is plans/<slug>/plan.mdx in your repo, open in the editor beside the Board or in any editor you like. Every revision is a snapshot in history/.
Status, a diff viewer, stage and unstage, commit, branches, push and pull, per Project. Rebase and conflicts stay in the terminal.
## 3. Architecture
<Callout kind="decision">
The Browser runs in its own process beside the Board.
</Callout>
<Question id="q3"> Do prototypes need the app's cookies?
<Diagram src="./browser-ipc.html" />
approved: revision 2
</Question>
motion.level token, like the sidebar.What developers ask before they open their first Workspace.
No. Every Run is the unmodified Claude Code CLI signed in with your own subscription; the API key variables never reach it.
None without you. Jira owns the title, criteria and status; FABER proposes a transition and waits for your confirmation.
In the Workspace: .faber/board.json, one file per Card and plans/<slug>/plan.mdx, the spec, all committed. Session ids and logs stay local.
Yes, each in its own Worktree. A Column marked exclusive, such as Test, queues its Runs one at a time.
FABER spawns the unmodified claude binary under your subscription login and strips every API key from its environment.
Point the Onboarding Wizard at a directory. It finds the Projects and the agent's rules, skills and hooks already there, or scaffolds them from the bundled Catalog.
spendwise-apiGit repositoryspendwise-webGit repository
spendwise-jobsCloned from GitLab
.claudeSkills, Rules, Guardrails
.mcp.jsonMCP Servers
AGENTS.mdRuleSearch the linked Jira board and pick the Issues to mirror. Jira keeps the title and the criteria; FABER keeps the rest.