Report a bug
Beta bug reports are how this gets to 1.0. Faster paths first.
TimeFlow is in active development and bug reports — even small ones — make a real difference. The fastest way to get something looked at is to email the maintainer.
Email the maintainer
Send a short note describing what broke. Screenshots and a one-line repro help enormously.
What to include
The smallest useful bug report has three pieces:
- What you did."I clicked Schedule on the Tasks tab." / "I dragged a chunk from Wednesday to Thursday." Concrete actions, not abstract descriptions.
- What happened. Including screenshots is gold — they capture more than you think they did. A short screen recording is even better for interaction bugs.
- What you expected.Sometimes "it's broken" means something different to you than to the person reading the report; a sentence on the expected behavior closes the gap.
Quick triage tips
- If you saw a console error, copy it in. Right-click the page → Inspect → Console tab. Even cryptic messages are useful.
- Tell us your browser + OS. "Chrome 132 on macOS Sonoma" is enough.
- If it only happens to you, mention what's unique about your setup — multiple calendars connected? Custom schedule with empty days? Habit with rollover enabled?
Security disclosures
For security issues — anything where filing publicly could put other users at risk — please use the same email and put [security] in the subject line so it gets triaged first.
Status
We respond within a few days during the beta. Don't be surprised if a fix ships the same day for the obvious ones — that's the upside of a small team.
Thank you for helping shape this. Beta users are why TimeFlow gets better fast.