An orchestration layer, not a replacement model
Commandem coordinates coding agents, project work and evidence from a local-first workspace. The models remain supplied by their providers or a local model runtime. The app’s local state does not mean a cloud-backed agent keeps prompts on the machine.
This distinction guides the website language: “local-first orchestration layer for coding agents” names the product category while leaving room to explain each network boundary. No slogan substitutes for a data-flow description.
Name each boundary
Provider authentication and data-use policies belong to the selected account and service. A local privacy setting cannot certify an unreadable provider training toggle. Workspace storage, receipts, integrations and notification delivery have separate behavior that should be reviewed independently.
The marketplace combines discovery across recipes, plugins and skills; it does not combine their trust models. A recipe is prompt material, a plugin is executable code, and a skill is a capability package. Review source and declared permissions before use. A community description is not the same as a complete source body or a security endorsement.
Keep the website’s fallback honest
The static catalog includes bundled entries and can be opened offline. Community refresh uses a same-origin endpoint in the deployed site. If that endpoint fails, bundled entries remain usable and the page explains that the community view is unavailable.
A browser cannot refresh community data from a double-clicked file preview in the same way as the deployed server. The offline message must say that explicitly rather than pretending the last network response was successful.
What a release must establish
A public release needs an approved repository and artifacts, precise platform support, an update and removal path, a verified support route and deployment checks. Local source commits and private installed builds do not establish those facts by themselves.
The release hub therefore distinguishes the reviewed pre-release from an approved download. The privacy and security pages explain the relevant boundaries; they are not legal-compliance or penetration-test certifications.