pastilhasandClaude Opus 5
39ce0953e4
A loop writes to its job panel and nobody reads a job panel, so a watcher that fires overnight has done the work and told no one — which from the owner's side looks the same as not firing. Two messages, no more: what appeared and that it is being handled, then a short report when the work ends. A progress commentary in chat is a notification per step, which is how somebody turns notifications off. The mechanism needs nothing new and no authentication. The child writes its report to a file on the same machine as the same user; the loop inserts a nudge row for its own transcript id over the local Postgres socket; the nudger wakes the conversation within the minute and the commander reads the file and writes the report itself. Facts in a file, judgement in the chat — which is what buys a summary instead of a pasted log tail. Notes the three things that bite: one nudge row per session so overwrite rather than queue, the nudge message is a prompt to yourself and not what the owner reads, and up to a minute late because the nudger polls on a minute. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Officer capabilities
The file-based store Officer reads agent items from. This repository holds the ones the platform ships; everything else in this directory is yours.
affordances/officer/core/ ← shipped here
skills/ tools/ tasks/ processes/ extensions/ agents/
Those six directories are created by the platform at boot and are where you and your agents author
items. They are deliberately not tracked here — your work is not ours to version. extensions/tool-loader
is written by the platform from its own source and will reappear if you delete it.
Affordances
An affordance is what the surface on the other end of the conversation offers the agent: what the client will render, accept or ignore. Not what the agent can do — what it will get away with.
The platform compiles every affordance into one block and appends it to each agent session, so an agent
knows things it could not otherwise discover from the filesystem. plugins/CLAUDE.md in the platform is
the authority on the format and on what belongs in one.
Layout is <publisher>/<plugin>/, with core in the plugin slot for the platform's own. A plugin ships
its own affordances/ directory and installing it copies them in.
Updating
git pull, or press Update all on the platform's marketplace screen, which updates this alongside
every installed plugin.
Your own untracked items are unaffected by either.