Product naming
Model-visible agent context uses the WednesdayAI brand. Operator identifiers, disk paths, env vars, and SDK package names stay openclaw. This page is the contract for code and tests that touch either side.Case map (exact)
Do not invent other spellings (
Wednesday AI, wednesday-ai, Openclaw, …).
KEEP classes (never blind-rename)
Even when a string is model-visible or adjacent to REPLACE text, keep these byte-identical:OPENCLAW_*env vars~/.openclaw/,openclaw.json, service/unit names, sockets- TypeScript identifiers (
OpenClawConfig,OpenClawPluginApi, …) - Import specifier
openclaw/plugin-sdk(thewednesdayai/plugin-sdkdual alias is also valid where published) - Manifest filename
openclaw.plugin.jsonand the legacyopenclawmanifest key __OPENCLAW_REDACTED__,openclaw.inbound_meta.v1,provider: "openclaw"- npm package name
wednesdayaiwith dualbin:wednesdayaiandopenclaw(both point atopenclaw.mjs— the alias is permanent)
profile="openclaw" next to “openclaw-managed browser” prose), change only the prose token.
Surfaces that must say WednesdayAI
- System prompt identity and section headings, docs block, tool blurbs
- Subagent / announce / group-intro strings the model reads
- Tool error and status text reused into model context (session status version line included)
- Bundled skill descriptions/bodies and workspace templates
- Model-taught docs base URL
https://docs.wednesdayai.dev - Model-taught CLI spelling: primary binary
wednesdayai(openclawremains a permanent alias at the process boundary)
Prompt markers (lockstep)
Plugin authoring rules
- Import from
openclaw/plugin-sdk(or the publishedwednesdayai/plugin-sdkdual alias), never from relative paths intosrc/. - Your manifest filename stays
openclaw.plugin.json; eitheropenclaworwednesdayaiworks as thepackage.jsonmanifest key. - User-facing prose in your plugin (descriptions, reply text the model echoes) should say WednesdayAI; config keys and file paths you invent should follow the operator convention.
Guard tests
Update colocated string assertions in the same change as a source rename. Prefer at least one test that builds the real prompt (or real tool result) rather than only checking a helper’s return value.
What not to do
Related
- Product naming (admin) — the operator guide
- What is WednesdayAI? — user summary
- Plugin manifest — manifest key rules