Features · Enhancements · Bugs
Open it and you know exactly where you stand — the idea you had on your walk to the coffee shop, the bug your client spotted and logged, the fix your AI assistant made at three in the morning, all in one place.
Just tell any AI assistant you use to take a task from your To Do list. Your AI assistant will automatically enhance the task details and plan before it starts, and record in human language a few simple lines on how it actually implemented or fixed it — all on the card, for you or anyone else to read later.
Your features, enhancements and bugs live on the board — not inside whichever AI assistant you happened to be using that month. Connect Claude, ChatGPT and Cursor to the same board at the same time and they all read the same tasks, the same refs and the same history. There is nothing to map, nothing to import and nothing to keep in sync, because there is only ever one copy.
The people who spot a problem usually aren’t the people who fix it. Your team, your client, a friend testing it on their phone — give them a role and they put tasks straight onto the board themselves. No screenshot buried in a chat thread, no “can you write that down somewhere”, no forwarding an email to yourself so you don’t forget it.
Sam, Priya and Dan share one board. None of them uses fenbs the same way, and none of them had to be shown how.
Builds a product on his own time. His AI assistants do more of the typing than he does, so what he needs is somewhere to put an idea the moment he has it.
BU-016.Runs the work without writing it. She can’t read the diff, so the record of what her AI assistants actually did is the whole reason she’s here.
The client. He pays for the work, never edits anything, and shouldn’t be able to — but he should be able to look whenever he likes.
FE-038 instead of sending an email nobody files.Six rows, three accounts. An AI assistant sits under the person whose login it uses, with its scopes where a role would be — because that is exactly what a token is.
FE-041 · 08:02BU-016 · 09:14EN-023 · 03:00FE-038 · YesterdayThree people. Three AI assistants. Three accounts.
An AI assistant isn’t a member — it’s a key cut from one, and it can only ever be cut smaller.
There’s no separate bot-permissions screen to keep in sync with the real one, because there’s no separate account to permission. Whatever role you hold on a board is the ceiling for anything you connect to it. Narrow your role and every token you issued narrows with it, immediately, with nothing to remember.
| Role | Can |
|---|---|
| Owner | Everything, including billing and deleting the board |
| Admin | Everything except billing |
| Editor | Create, edit, move and comment on any task |
| Reporter | Create tasks and comment; edit only their own |
| Viewer | Read and comment |
“I can’t move FE-014 — I’m acting as Sam, and Sam is a Viewer here.”
What an AI assistant says when it hits a wall
Every refusal names the permission that was missing and whose role it was checked against. An AI assistant repeats that sentence rather than guessing, retrying, or quietly doing something adjacent — which is the failure mode that makes people stop trusting agents with real work.
A token is displayed at the moment you issue it and never again. There is no endpoint that reads one back, because a credential you can recover is a credential someone else can recover.
Tick read, write, comment. The token is checked against those and against your board role, so it can never do something you couldn’t. Narrow your role and every token you issued narrows with it.
One click stops it and you stay signed in — same account, one fewer key. Everything it did stays in History under its name, because revoking access shouldn’t erase the record of what happened.
AI assistants cost nothing extra and can’t take a seat — they aren’t accounts. Plans start at $4.99 a month.