GuidesA checklist page you reuse
A checklist page you reuse
Have an agent write a checklist as a page, pin it in the chat, tick it off, and reset it for next time.
This guide gets you a checklist that lives in an agent’s chat: a small pagePage. A small HTML page an agent writes as its answer: a checklist, a comparison, a form. you tick off on your phone. It remembers its ticks, and the agent can read and reset it.
The examples follow Mara, who wants a release checklist for atlas-web. Pages show
in the iPhone app and the web client; Telegram and Discord get a link that opens the
web client.
Make and use it
Section titled “Make and use it”Ask for the page
Section titled “Ask for the page”In the agent’s chat:
Make a release checklist for atlas-web as a page I can tick off and reuse:
tests green, changelog written, version bumped, tag pushed, deploy checked.
Add a button that sends you what is done.install.sh gives your agents the vendetta-pages skillSkill. Instructions an agent loads for one kind of task.Skill. Instructions an agent loads for one kind of task., which tells them how
to write one: a single self-contained HTML file, phone first, light and dark. The
agent ends its reply with a link, and the page opens inside the chat.
An agent in a container project has that skill only once you give it.
Tick it off
Section titled “Tick it off”Tap the items. The page saves its state on your computer on every change, so the ticks are there when you open it on another device. A page that is already open elsewhere reads the saved state when it is next opened.
If the page has a send button, tapping it sends the agent a message, which the chat shows under the page’s title. The agent’s reply shows in the page’s viewer as it comes.
Pin it
Section titled “Pin it”Choose Pin to chat on the open page. Pinned pages stay above the chat’s messages, on all your devices. A chat pins up to ten; Unpin removes one.
Reuse it for the next release
Section titled “Reuse it for the next release”Ask the agent:
Reset the release checklist for 2.5.It rewrites the same file, and the pinned page shows the new content. The agent can
also read and edit the page’s saved state directly: it lives beside the page with
the same name and .state.json in place of .html.
Open it at the desk
Section titled “Open it at the desk”In a terminal the agent’s link opens the page in the web client, where ticking and
sending work the same. The link looks like
https://workstation.example.ts.net:8743/?page=2026-11-17-release-checklist.
When a page doesn’t work
Section titled “When a page doesn’t work”Ask the agent to check it, or run the check yourself:
vendetta page check ~/.local/state/vendetta/pages/2026-11-17-release-checklist.htmlIt prints one line per problem, and the page’s link when there is none. A page works only when it:
- is in
~/.local/state/vendetta/pages/, the one folder Vendetta shows pages from; - is at most 1 MiB;
- loads nothing from the network: the app blocks it, so styles, scripts, and pictures are inline;
- uses the page’s saved state, not the browser’s storage, which is not kept;
- has a viewport, a title, and dark colours.
A page’s saved state holds up to 256 KiB.
What a page can’t do
Section titled “What a page can’t do”- Ring or notify. For a reminder, the agent starts an alert or a timer itself.
- Send without you. A page sends only within five seconds of your tap.
- Share its ticks between people. In a project shared with someone else, each person’s copy of a page keeps its own state.
- Keep its state inside a container. For an agent in a container project, the page is copied out to show it, and the ticks are saved with that copy. Have such a page send the agent what changed.