pastilhasandClaude Opus 5
a9daefa427
$OFFICER_AGENT_KEY, minted per session and scoped to notify. before this an agent had no door: the only token in the tree lives in the MCP server's environment, which its own Bash cannot see — so an agent asked to tell its owner something either could not, or asked to be handed a personal API key, which is the owner's full authority pasted into a transcript. with the distinction that matters most in practice: this is not the harness's own push tool, which refuses to interrupt a terminal the user is sitting at. that rule is right for that tool and wrong for this one — a notification from here exists to reach somebody who is not looking. and the two judgements the agent has to make itself: send few, because an interruption for something that worked trains people to stop reading; and watch what goes in the text, because unlike every other notification in Officer this one travels through Apple and Google to reach a lock screen. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Officer-Session: 656f5c85-e49a-4f1f-b9f3-042a04b4d043
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.