RFC 0026: Automations terminology and configurable feature naming#50
RFC 0026: Automations terminology and configurable feature naming#50omarshahine wants to merge 2 commits into
Conversation
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WhJ8EiMXue6ADLmHfb7FL6
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WhJ8EiMXue6ADLmHfb7FL6
|
@clawsweeper re-review |
|
🦞🧹 I asked ClawSweeper to review this item again. Re-review progress:
|
|
ClawSweeper status: review started. I am starting a fresh review of this pull request: RFC 0026: Automations terminology and configurable feature naming This is item 1/1 in the current shard. Shard 0/1. This placeholder means the worker is alive and reading the current context. I will edit this same comment with the actual review when the claws are done clicking. Crustacean status: shell secured, claws on keyboard, evidence pebbles being sorted. |
Summary
RFC 0026 proposes finishing the cron → Automations rename so the word "cron" never appears in user-facing UX or model-visible text when naming the feature, and adding a
ui.terminologyconfig so tailored deployments can use a custom term (e.g. "Habits").Key boundaries:
cron.*, gateway RPCcron.*methods, SQLite tables, state paths, session-key prefix, and theopenclaw cronCLI token (kept as alias) are untouched — no protocol bump, no storage migration.--cron,{kind:"cron"}), mirroring the split the UI schedule selector and docs already draw.automationswith allow-list alias, system prompt, heartbeat guidance, session labels, delivery notices), UI leftovers (~8 catalog values + 1 hardcoded prefix +/cronroute alias + command palette), CLI alias + prose, doctor prose, docs body copy.ui.terminology.automation.{singular,plural}injected via existing i18n param interpolation, prompt-builder templating, and CLI formatters.Backed by a four-surface audit of the current codebase (agent-facing strings, CLI, web UI i18n catalog, config schema/docs); file references inline in the RFC.
Status: draft, per RFC lifecycle. Discussion thread in
maintainer-discussionto follow.🤖 Generated with Claude Code
https://claude.ai/code/session_01WhJ8EiMXue6ADLmHfb7FL6