The public website for Work at work.software: desktop, company brain, and mobile, powered by the open-source Catamorphic framework.
Static HTML, CSS, and JavaScript. No build or runtime dependencies.
Run python3 -m http.server 4174 --bind 127.0.0.1 --directory site and open
http://127.0.0.1:4174.
GitHub Pages serves site/ through the deployment workflow. The custom domain
is work.software. Pull requests validate pages, local links, ARIA references,
JavaScript, and media decoding. Merging to main runs the same checks, then
deploys the exact site/ artifact to GitHub Pages. Manual deployment is also
limited to main; feature branches cannot publish.
Run python3 scripts/check_site.py and node --check site/site.js locally.
The media check requires FFmpeg: ffmpeg -v error -xerror -i site/assets/work-desktop-film.mp4 -f null -.
The website does not promise unavailable platform releases.
The homepage plays site/assets/work-desktop-film.mp4, a silent 1680x1050
H.264 recording of the actual desktop app at 60 fps (a 16:10 frame, matching
the aspect-ratio of the orange panel it sits in). The window lays out at
1280x800 and renders at 1.3125x, so text stays sharp at the size the page
shows it. It follows one scenario in a prepared project, "Lisbon offsite":
Sam is planning a three-day team offsite with an open Friday afternoon.
- From the palette, Sam opens a travel guide (Wikivoyage's Lisbon page) beside the plan, so the two are tiled.
- Sam asks the agent to open Belém in the guide and fill Friday afternoon. The agent navigates the guide in its tile and writes three stops into the plan.
- Sam asks for light mode, and the whole window turns light.
- Sam asks for a workflow that checks Friday's forecast every morning and posts it to the chat, then opens it: the graph shows its schedule, the forecast check and the message.
- Sam asks for an app for the team with the plan, the forecast and who is joining what. From the palette, Sam opens it beside the workflow, picks a name, sees Friday's live forecast (Open-Meteo) and joins a stop.
Every agent turn is real (Claude Code on this machine's login, with the person's own connectors denied in the demo project), and the workflow and the app are the ones the agent built. Typing, clicks, scrolling, the palette and app use run at 1x; the agent's minutes of work, the guide's page load and the app's first load are cut, each bridged by a short dissolve, and nothing is sped up. The pointer is drawn from the recorded input, since scripted input shows none. The three earlier chats in the sidebar were real turns seeded through the normal chat. The team, the hotel and the plan are fictional; the guide and the forecast are real.
Raw takes, markers, the cut list (edit.json), renderer and production notes
are in ../work-product-film/v6/. The reusable skill is
.agents/skills/announcement-video/ in the Catamorphic repo, with a
Work-specific story reference.
site/llms.txt describes Work for agents (what it is, what matters, how it
works, install, and pointers to the source files that are the truth). The
homepage links it in <head> (rel="alternate" type="text/markdown"), in a
comment at the top of <body>, and in the footer. The "Ask your agent about
Work" control under the film opens a new chat in Claude, ChatGPT, Perplexity
or Grok with one prefilled message that points the agent at work.software.
The brain section's "Set up a Work server with your agent" does the same with a
message that points the agent at the repository's Work server setup skill, plus a copy
item for agents that run in a terminal or in Work itself.
site/llms.txt describes Work for AI agents and links into the repository;
site/llms-full.txt inlines those documents and is generated by
python3 scripts/build_llms_full.py (pass a local checkout to skip the
network). DESIGN.md ("Where the words live") lists every place messaging
appears. Run python3 scripts/check_site.py before committing.