pastilhasandClaude Opus 5
d963bd0a4c
pm2 restart officer-claude-code tree-kills the sidecar, which takes claude and the agent's shell with it. the tool call never returns, the conversation stops dead, and the harness records it as an INTERRUPTED or REJECTED call — so the transcript blames the user for something they did not do. that misattribution is the expensive part: it sends everyone looking in the wrong place. the owner had seen it before and could not reproduce it. pm2 restart officer is safe and always was — sidecars are peers of the main server, not its children. only the agent's own host is special. and the trap underneath it, which is quieter: a change under src/servers/sidecar/claude/ does not take effect when officer restarts, because it lives in the process the agent is running inside. on 2026-08-25 a credential scope was widened, officer was restarted four times, and the sidecar carried the previous build all day while every report said otherwise. check the process uptime before claiming a change is live. the way out is to ask the owner, or to detach with setsid and say first that the session is about to end. 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.