Local To-Do List

Context

Not every task needs to enter a longer-lived action-item system. I wanted a lightweight place for immediate personal follow-up that would stay in the browser and remain distinct from the separate Supabase-backed action list.

Approach

The page records a short task, priority, and due date, then stores the list in the browser's local storage. Tasks can be sorted by priority or due date and removed once they are finished.

What happened

The result is a local list for everyday follow-up without adding a sign-in, service, or shared workflow. It is intentionally separate from the action-item list, which has different persistence and review needs.

Working with AI

Codex helped turn a simple list into a small, bounded interface and test the storage behavior. The useful decisions were keeping the scope local, making the distinction from the action-item system clear, and avoiding features that would turn it into a second workflow product.

Key details

• Tasks include a short description, priority, and due date.
• The visible list can be sorted by priority or due date.
• Task data remains in local browser storage and is separate from the Supabase-backed action-item system.

Tools and method

The page is a Next.js client component. Its tasks are kept in the browser's local storage, including across tabs in the same browser, without a database or remote service.

Lessons learned

A local tool can be more useful when it has a narrow job. Keeping short-term tasks apart from a fuller action-item system makes the purpose of each list easier to understand.

Limitations

The list does not sync between browsers or devices, and clearing the browser's site data removes its saved tasks. It is not intended to replace a shared or durable action-management system.

Next step

Use it for routine short-term tasks and adjust the fields only if repeated use shows that a small addition would improve the local workflow.