pastilhasandClaude Opus 5
5db4f0968f
ANTHROPIC_BASE_URL points at a local proxy that holds the real credential, so ANTHROPIC_API_KEY is a token for that proxy — and the CLI sees a key set, assumes the worst, and warns on every spawn. Nothing is wrong and nothing uses connectors. But a loop that narrates stderr whenever it is non-empty then narrates this every single time, which teaches whoever reads the job panel to skim the one channel that carries real failures. So: filter that known line and report what is left. Never suppress stderr wholesale — the reason to keep it is the failure nobody has seen yet. 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.