How to keep a Claude Code progress report as an artifact and refresh it on a schedule

When Claude Code runs for hours, terminal output alone makes it hard to tell what is finished. Have it keep the progress as an artifact (an HTML page published to claude.ai) and republish it on an interval, and you can check on it from a single link while you are away.

1. Publish the first version by asking for it directly. The page goes to a private claude.ai URL and the link is printed in the terminal.

Make a progress report artifact for this project: what's done, what's in progress, and open problems, with a chart of tasks by status.

1. In the same session, set up a refresh with /loop. Claude edits the same file and republishes to the same URL, and if the page is open, it updates in place.

/loop 12h update the progress report artifact with what changed since the last update and republish

In a turn started by a scheduled task, Claude Code asks before the first publish of each artifact, which is why you publish once by hand before starting the loop. /loop only runs inside the session and ends after seven days.

1. To find it again, pick it from /artifacts or open the gallery at claude.ai/code/artifacts. To keep editing it from another session, pass the URL.

Update https://claude.ai/code/artifact/<id> with today's progress.

Artifacts need a Pro, Max, Ultra, Team, or Enterprise plan, a session signed in with /login, and v2.1.281 or later. Sessions using an API key, Bedrock, or Google Cloud cannot publish, and they are off by default with -p. To stop the browser from opening on the first publish, set CLAUDE_CODE_ARTIFACT_AUTO_OPEN=0.