Clipboard, plans and Agent Files#
Clipboard records and published artifacts serve different purposes:
| Surface | Typical content | Key distinction |
|---|---|---|
| Clipboard | Copied/pasted snippets, notes and plan records | Private user-scoped working context. |
| PLAN record | Intended steps, status and progress | Planning is not execution evidence. |
| Canonical memory | Durable scoped knowledge | Longer-lived facts/decisions, not raw secrets. |
| Agent Files | Generated documents, images, exports and other deliverables | Publication makes outputs discoverable to the intended user. |
| Workspace filesystem | Project sources and working files | A local path is not automatically an app download. |
Clipboard source categories include COPY, PASTE, MANUAL_NOTE, AGENT_NOTE and PLAN. API/worker transports differ in allowed writes. Read the current contract rather than posting an assumed payload.
Publish artifacts through the installed sanctioned interface, verify the returned identifier and confirm the intended output. IDs establish registration; do not claim cryptographic immutability unless the actual storage contract guarantees it. File limits and retention are installation-specific.
Do not expose provider credentials, private profiles, internal logs or unrelated account information in public screenshots, exports or bundles. A generated artifact should be inspected before publication.