pastilhasandClaude Opus 5
2ff00dd634
The platform changed underneath this. A commander is no longer recognised by sharing one folder with every other — it has its own directory, created before its first turn, holding a CLAUDE.md written at creation and a state/ for what it has done. isCommandersDir is gone. Three things in here were wrong in ways that change what a commander does on turn one, which is the turn that matters. Orientation said to read where you are. Under the new shape that is your own directory, which holds your CLAUDE.md and an empty state/ — nothing to learn, and listing it teaches you nothing. The thing you were pointed at is the REFERENCE PATH, named in your CLAUDE.md, and it is deliberately not where you live. The first-turn interlock is gone and the skill claimed it as a mechanism. The paths a commander records itself at could not be resolved on turn one, so their absence WAS the signal; they are written before the first turn now. The rule is the whole guard rather than a backstop to it, and saying so is better than letting somebody discover the interlock no longer bites. And the button gives a name and a reference path, not a working directory. Adds what the old text had no way to say: everything a commander knows is on disk, so a session that dies can be replaced in the same directory and it carries on. And that its CLAUDE.md is its own file to extend — read at the start of every session, so what it writes there is what the next conversation knows. 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.