pastilhasandClaude Opus 5
8a1bcb03f5
two things an agent cannot discover and gets wrong by default. FIRST: asked to create an app, it scaffolds one. there is a template — templates/template-react on gitea — and it is the agreed starting point. it documents itself, so this points at its README, CLAUDE.md and CONVENTIONS.md rather than restating them; the one thing worth lifting out is README step 1, the rename, because it costs thirty seconds at the start and is a chore forever after. SSH not HTTPS, verified both ways: the https remote prompts for a username and dies in a non-interactive shell. the tailnet address is noted as the fallback for when the public host's ssh is being rate-limited, which the deploy skill already records as a recurring thing. SECOND: asked to run it, it runs bun dev in the foreground, which blocks until the tool times out and reports a working server as a failure. backgrounding is both the only thing that works AND what the owner wants — a background job gets officer's live panel, the same one they would see running it themselves, so they can read the output and stop it without asking. 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.