Zero code changes. Config only. Works with any OpenClaw bot.
Adding your OpenClaw bot to a new Telegram group used to require:
- Create the group
- Add the bot
- Find the chat ID somehow
| # Codebase Scorecard: Atelier Design Document (v3 - Final) | |
| **Audited**: 2026-04-03 (after behavior trees + all fixes) | **Size**: 2495 lines | **Type**: Design Specification | |
| | # | Category | Grade | Key Finding | | |
| |---|-------------------|-------|-------------| | |
| | 1 | Architecture | A+ | Clean hierarchy, pluggable multiplexer, capability-based providers, behavior trees for orchestration | | |
| | 2 | Code Quality | A+ | Thorough coverage, all edge cases addressed, comprehensive error recovery | | |
| | 3 | Consistency | A | Uniform naming, consistent patterns throughout | | |
| | 4 | Security | A | Command interpolation documented with shlex.quote(), subprocess.run(..., shell=False), audit trail | |
| # Codebase Scorecard: Atelier Design Document (v2) | |
| **Audited**: 2026-04-03 (after updates) | **Size**: 1870 lines | **Type**: Design Specification | |
| | # | Category | Grade | Key Finding | | |
| |---|-------------------|-------|-------------| | |
| | 1 | Architecture | A | Clean hierarchy, pluggable multiplexer, capability-based providers, excellent separation | | |
| | 2 | Code Quality | A | Thorough coverage, state machines documented, edge cases addressed | | |
| | 3 | Consistency | A | Uniform naming, consistent patterns throughout | | |
| | 4 | Security | A | Command interpolation documented with shlex.quote(), subprocess.run(..., shell=False) | |
| # Atelier: `doctor` Command | |
| ## Philosophy | |
| One command for health. `doctor` checks and fixes. | |
| - `doctor` = audit + correction | |
| - `doctor --check` = audit only (dry run) | |
| - `doctor --force` = audit + auto-fix everything (skip prompts) |
| # Atelier: `doctor` Command (Unified Health + Fix) | |
| ## Philosophy | |
| **One command for health.** `doctor` checks and fixes. No split between "check system" and "heal workspace". | |
| - `doctor` = audit + correction | |
| - `doctor --check` = audit only (dry run) | |
| - `doctor` = audit + auto-fix safe things | |
| - `doctor --force` = audit + auto-fix everything (including risky) |
| # Atelier: `heal` Command Proposal | |
| ## Problem | |
| `atelier heal` is mentioned in the design doc but underspecified: | |
| - What health checks exist? | |
| - What failure modes are auto-recoverable vs require human intervention? | |
| - Does `heal` just restart things, or does it diagnose root cause? | |
| This proposal defines `heal` concretely. |
| # Codebase Scorecard: Atelier Design Document | |
| **Audited**: 2026-04-03 | **Size**: 1602 lines | **Type**: Design Specification | |
| | # | Category | Grade | Key Finding | | |
| |---|-------------------|-------|-------------| | |
| | 1 | Architecture | A | Clean hierarchy (Project→Workspace), layered modules, capability-based providers | | |
| | 2 | Code Quality | A | Thorough coverage, state machines documented, edge cases addressed | | |
| | 3 | Consistency | A | Uniform naming, consistent patterns, all enums defined | | |
| | 4 | Security | B- | Shell injection risk in services/hooks/notifications; no sanitization documented | |
| # Codebase Scorecard: Atelier Design Document | |
| **Audited**: 2026-04-03 | **Size**: 1 doc, ~44KB | **Type**: Design Specification | |
| | # | Category | Grade | Key Finding | | |
| |---|-------------------|-------|-------------| | |
| | 1 | Architecture | A | Clear hierarchy (Project→Workspace), layered modules, well-defined boundaries | | |
| | 2 | Code Quality | A- | Thorough coverage, edge cases addressed, but some ambiguity in error paths | | |
| | 3 | Consistency | A | Uniform naming, consistent patterns throughout | | |
| | 4 | Security | B- | Shell command injection risk in services/hooks/notifications | |