Vibe-coded Calendar habits tracker

This is my today’s tool that I made fully with Claude code, it has persistnet storage and keep the data between sessions on different devices. Now let’s see if it can be really useful.

I named it Building Momentum as it is the tool to actually build the consistency habits and better focus.

https://claude.ai/code/artifact/2d166ec7-522c-48fc-bd6c-1ba779529dab?org=5caa9596-0021-4c2d-bdb9-896f01aefc6f&open_in_browser=1

To use it efficiently on my own or your own with persistent storage and without much overhead. There are few steps to maintain.

1. Open this link. It’s almost the same as previous but this one allows to copy code (idk why previous one not) https://claude.ai/public/artifacts/632db2b9-7d1c-4fe8-bc0e-bc1b76f015ef
2. Copy code.
3. Paste into Claude Chat and ask explicitly to create it as artifact.
4. Publish this artifact.
5. Copy link to new artificat.
6. Save it as toolbar tabs.
7. Optionally add the same link to phone’s home screen (works in most browsers).

I found bug (I think it’s bug) that Chat Artifacts and Claude Code Artifacts behaves differently the same html code couldn’t be built with persistent storage in Claude Code it fails on “window.storage” lines. For me it sounds like those two Artifacts features are slightly different.

• Claude Chat builds the app using data storage chat context window. The data is small so there is no reason to be afraid about overflowing data.

• Claude Artifact can’t use the chat context window as a storage because it’s coding agent not chatbot. Even trying to move the data storage to external file or sync service it will be no artifact any longer as artifact has to be inside Calude ecosytem fully.

I was almost right they are different but it’s the expected behaviour (facepalm). There’s explenation:

• Persistent storage (window.storage) is a Claude.ai / Claude Desktop chat-artifact feature specifically. It’s described as artifact storage tied to your Claude subscription, capped at 20 MB per artifact, text-only, and — importantly — it only activates once the artifact is published. During dev/testing in chat, storage calls will silently fail to persist, which trips people up too.
• Claude Code artifacts are a different feature entirely. They publish a Claude Code session’s output as a live page (a PR walkthrough, a dashboard, an investigation timeline) at a private URL that updates as the session runs. There’s no mention of window.storage in that feature at all — it’s built for showing session results, not for hosting a standalone stateful app.