The question
Todo apps are a controlled domain. You know the edges. That made Peponi.to a good place to test two things at once: what it feels like to build with Cursor as a pair programmer, and whether a small planner can stay honest about ownership.
The live site is peponi.to. Try it on my server for a week. Then I delete the account. Clone the repo to keep your lists. MIT. No app store. On Omarchy you can skip the account and keep tasks on that machine.
What shipped
The product organises tasks by day. In Settings, pick Today only, or 2 through 7 days side by side, then drag tasks between days. There are no due dates. That is a design decision, not a missing feature. Due dates create a second job: managing the dates.
Themes are part of the product, not decoration. Classic, Lined, Graph, Vintage, and Dark, with four fonts and eight accent colours. Click the title and rename the app. Name your Not Yet lists. The point is a notebook you want to open, not a dashboard you have to clear.
Privacy is the other half. No social logins. No advertising. GDPR rights to export or delete. On Omarchy, local mode never sends tasks to peponi.to at all.
What the experiment revealed
AI assistance was fastest on scaffolding and debugging. It did not make the product decisions. No due dates, no social login, a week on my server then the source is yours: those are taste. The model will give you a conventional Rails todo app. It will not tell you when convention is the wrong product.
The experiment is still running. I built this for myself. The source is public.
Related reading
- Try it for a week, then run it yourself — What peponi.to became after the build process
- Designing with Cursor — What the AI did well and where it fell short
- An experiment in AI pair programming — Building with Cursor as a pair programmer
- From AI experiment to open source planner — The case study