Status that writes itself
Stages come from criteria, decisions, reviews and merges. Filur writes where each quest stands, and rewrites it when something changes.
Quests for teams of people and coding agents
Filur turns rough ideas into quests with acceptance criteria, hands them to your coding agents and reviews every pull request against what you agreed. Where things stand writes itself. Nobody moves cards.
How it works
People decide at every turn. Filur keeps the why, the what and the proof together, so agents build the right thing and everyone can tell when it's done.
01Shape
Drop in a complaint, a thread or a hunch. Filur shapes it into a quest: who's affected, the evidence, what better looks like, and acceptance criteria that say when it's done.
02Agree
Criteria are the contract between your team and your agents, and only people approve them. Open questions become decisions, with options, Filur's recommendation and an owner who makes the call.
03Build
One context pack carries the quest, its criteria, the decisions to follow and the domain's rules to Claude Code, Codex or Cursor. The agent builds it and opens a pull request; link it to the quest and Filur takes it from there.
04Review
Filur reviews each push criterion by criterion, with evidence, alongside reviewers for security, accessibility and risk. A criterion half-fills when an open pull request meets it, and fills in when it merges.
For coding agents
Filur doesn't bring a coding agent of its own. It gives the ones you already use a clear quest, a way in and a fair review.
Their own identity
Each agent signs in through the browser as itself, and you can revoke it at any time.
Every capability, every surface
Anything you can do in Filur, an agent can do over the API, SDK, CLI or MCP.
Clear boundaries
Agents build inside the quest. They never approve criteria, decide outside their scope or merge.
Write down what done means, hand it over, and see every pull request checked against it.