Defects, filed developer-ready.
A Linear-style tracker for the build crew: permanent BUG numbers, trackers per app or repo, a drag-and-drop board, and an LLM-drafted fix brief on every bug.
$5.00 per user, per month. Billed in advance. You pay only for the people you give access to.
What you get
- Permanent BUG-n ids across tracker moves
- Board and list with drag-and-drop
- Auto-generated, editable fix briefs
- Email intake to your bugs alias
How it works
- 1
Type one line
The description is the only required field. Tracker, severity and assignee are chips you fill in as you go, or later.
- 2
Let it write the brief
An editable fix brief is drafted from your notes – what is broken, where, and what to check – so the person picking it up is not starting from a sentence.
- 3
Move it across the board
New, backlog, in progress, in review, done. Attach a screenshot or a log; email a bug straight in from anywhere.
Describe the bug in one line. The fix brief writes itself.
One tracker per thing you ship
An app, a repo, a client's product, the internal tools nobody owns. Each gets its own tracker, and they all live in one board.
- Per app or per repohowever your team actually divides work
- A shared backlogone board, filtered, not six tools
- Made where they are useda tracker is created inline, not in Settings
Describe the bug in one line
The login button does nothing on Safari. That files it.
Tracker, severity and assignee are one click each as you type, so a bug lands where it belongs instead of in the default tracker and needing a second visit.
The fix brief writes itself
Curfew drafts a developer-ready brief from your notes: what is broken, where it was seen, what it affects. It is a draft and it is yours to edit - the point is that nobody stares at an empty box at the end of a long day.
A bug filed in ten seconds and a bug filed properly stop being different things.
BUG-296 is BUG-296 forever
The number is assigned once and it never changes, including when the bug moves to a different tracker. Whatever you wrote it in - a commit message, a changelog, a customer email, a note to yourself - still points at the right thing a year later.
Reference identity is not a detail on a tracker. It is most of what one is for.
Know who filed it
A person, an inbound email, or an agent. Automated testing files bugs now, and a queue that cannot tell you which is which is a queue you have to read twice.
So you can work the human reports first, or sweep everything a night run found, and the board says which is which without anyone tagging them.
Press /
One key on every screen, two engines behind it.
Nothing reaches the AI that a filter could answer.
is:openNot finished - new, backlog, in progress or in review
Only a question reaches Alfred, and he answers in the rail beside your work.
Alfred runs as you.
He sees exactly what you see and nothing else – never the whole workspace.
He never acts on his own.
Anything that would change a record comes back as a card you confirm.
$5 per person, per month.
Only the people you assign are billed – add them and remove them, and the bill follows. New workspaces start with $50 in credit, good for 60 days.
Common questions
What is a tracker?
A grouping – an app, a repo, a product. You can create them where you use them rather than in a settings screen.
Can we file bugs by email?
Yes. Each tracker can take mail, and a forwarded report lands as a bug with its attachments.
Bugs is one app in Curfew Suite.
Use it on its own for as long as you like. If you ever add another, it shares the same login, the same bill and the same data underneath.