WebsitePublisher.ai
Give your AI a project, not just a prompt.
Tasks is a shared tracker your assistant reads and writes while it works. Progress, decisions, blockers and the reasoning behind them, all in one place. So the next conversation starts where the last one ended, instead of at the beginning.
Every new chat is day one
Your assistant did good work yesterday. Today it has no idea it happened. So you open with a summary: what we built, what broke, what we decided not to do and why. By the time it is up to speed, half your session is gone — and tomorrow you will type it again.
The problem is not that AI forgets. It is that the record of your work lives in chat logs nobody can search, in your head, or nowhere at all.
A task is not a checkbox. It is a history.
Nothing is overwritten. Every update is added, so the trail of how something got decided stays intact. Status and progress are read from that history rather than set by hand — which means they cannot quietly drift away from what actually happened.
v1.0 — pull, do not push. The mail nodes fetch the work instead of the platform writing to them, so the store keeps zero inbound write paths.
Test suite fails on authentication — wrong token type for the dashboard API.
16 of 16 tests green. Two real bugs found along the way, both fixed and verified end to end.
Decision: each team member owns their own archive. Shared visibility is a wish, logged separately.
Why append-only matters
Six weeks from now, the useful question is rarely "what is the status". It is "why did we do it this way". A tracker that overwrites itself cannot answer that. This one can.
More than status updates
Different kinds of entry, because "we made progress" and "we chose this design and here is why" are not the same thing.
Progress and blockers
Where something stands, and what is stopping it. Status follows from these, so a blocker is visible the moment it is logged.
Architecture versions
Full design documents attached to the task, versioned. The plan and the work live together instead of in separate tools.
Notes and snippets
The decision you will forget, the command that worked, the reason you rejected the obvious approach.
Your assistant keeps the record, not you
Start a task
Ask your AI to create one, or add it yourself in the dashboard. A title and a few tags is enough.
Just work
As things get decided and finished, your assistant logs them. No separate write-up at the end of the day.
Pick it back up
Next session, in any connected AI: it reads the history and knows where you were.
Search it later
Find the decision from two months ago by what it was about, not by remembering where you wrote it down.
Reachable from every assistant you connect
Tasks is part of the WebsitePublisher platform, so ChatGPT, Claude, Mistral and anything else you connect all read and write the same tracker. See supported AIs → · Browse the platform APIs →
Tasks are what happens next. Email is what happened.
Tasks hold your plan and your reasoning. Email Archive holds the correspondence behind it: what a client actually asked for, what you promised, when the date moved. Together your assistant has the whole picture without you narrating any of it.
Tasks: the plan
What is in progress, what is blocked, what was decided and why. Written as the work happens.
Email Archive: the record
Every conversation with a client, searchable and summarised per relationship. Read more →
Stop starting over
Tasks is part of the platform. Connect your assistant and it can start keeping the record today.
Questions about how it fits your workflow? support@websitepublisher.ai