CNSL

The tools sit side by side over the same projects. The tracker holds the tasks and runs a timer on one or many of them; the calendar puts them on dates; the scheduler turns a repeated sequence into timed steps; the noder can automate a chain of tasks connected to your LLM of choice; the note pad became my little micro publisher; and the chat works inside projects.

The time tracker, where everything started, is one click on the task itself. On top of that my phone’s PWA carries a badge while a task is running — something I often forgot back in Toggl.

A CNSL note can be given its own URL under an author handle — /note/handle/slug — and made public or access-controlled. The published page is plain and readable, and the data stays in the same place as the rest.

Projects can be shared with editor, viewer or contributor roles, or opened for public submission so contributors add items without having an account.

The first version kept everything in the browser. Tasks lived in local storage — no server, no account. That ruled out sharing and a second device.

The reason was that the shape of the product changed every week. With nothing in a database there was nothing to migrate when a view changed, and with no data on a server there was nothing that could leak while the structure was still moving. The backend came once it had settled.

A first simple and extremely cut-down prototype, from a very comprehensive and gigantomanically matured vision. By now the board seeds itself from CNSL’s own roadmap on first load. The app tracks its own development, which means every missing feature is visible in the tool while you use it.

The landing page runs the real components rather than pictures of them: the tour cycles through all seven tools with sample data.