every agent session starts from nothing. you re-explain the project, the decisions already made, and the three things that turned out not to work — and you do it again next time.

a context tracker is one html page holding that state: what this project is, what has been decided, what is in flight, and what the next session should pick up. an agent writes it, publishes it to a stable url, and updates the same url as the work moves.

it is readable by a person and parseable by an agent, which is the whole point — the next session opens one link instead of being briefed from scratch.

a starting point, not a template — the point of an agent is that the result is yours. replace anything in [brackets] and add whatever the page actually needs.

Create a polished, responsive project context tracker for [PROJECT NAME].

Goal:
A single page an AI agent and a human can both read to resume work without being re-briefed.

Content and requirements:
- Header: project name, one-line purpose, last-updated date, current status
- "Current state" — what is true right now, in 3-5 bullets
- "Decisions" — each with the decision, the date, and the reasoning. Include decisions
  that closed off an option, not just the ones that opened one
- "In flight" — work started but not finished, with owner and blocker if any
- "Next session" — the specific brief for whoever (or whatever) picks this up next
- "Resources" — links, file paths, and identifiers worth having in hand
- A machine-readable JSON block at the end mirroring the same state, so an agent can
  parse it instead of scraping the prose

Design direction:
- Dense but scannable; this is a working document, not a marketing page
- Monospace for identifiers, paths, and dates
- Mobile-first and accessible
- Clear hierarchy and fast loading

Delivery requirements:
- Produce one self-contained HTML file.
- Include CSS and JavaScript in the file where practical.
- Do not require a build step or server.
- Use placeholders where information is missing; do not invent facts.
- If an HTMLShare integration is available, publish or update the artifact there.
- Otherwise save the final .html file ready to upload to HTMLShare.

• the JSON block is the part worth keeping. it is what makes the page a handoff format rather than a status report.
• ask the agent to update the page at the end of each working session, not the start. the state is freshest while the reasoning is still loaded.
• if the project has a repo, have the tracker cite commit hashes and file paths — an agent can then go read the real thing rather than trusting the summary.

claude

with the htmlshare mcp connector enabled, claude publishes the page and hands back a siteId and manageToken. keep both: the next session passes them to update_html and the url stays put. without the connector, claude writes the file and you drop it on the home page.

codex

keep the tracker in the workspace as a real file so it diffs alongside the code, and publish with an api key on each update. the file is the source of truth; the url is the shareable view of it.

cursor

same shape as codex — the tracker lives in the project, and a publish step on save keeps the url current. useful when more than one person is driving the agent.

stable updates

the url is the point. a tracker that moves every session is worse than no tracker, because now the agent has a stale link.

no expiry

anonymous pages are deleted after 7 days. a project outlives that; the tracker has to as well.

versions

seeing what the state was three sessions ago is how you find the decision that quietly went wrong.

password

project state is usually not for the open web, even when it is not exactly secret.

why a web page instead of a markdown file in the repo?

if everything touching the project is in one repo, use the file. the page earns its place when the agent, the person, and maybe a teammate are not all in the same checkout — a url has no prerequisites.

can the agent read it back?

yes, that is what the json block is for. the page is a normal url; an agent that can fetch a url can reload the state.

does updating it change the url?

no. republishing with the manage token replaces the content at the same address, which is what makes it usable as a fixed reference.

• send a proposal, not an attachment.
• everything in ai work
• publishing from an agent or the api