customize

Adding a new input channel like Telegram or Slack requires following an interactive, question-driven workflow to gather requirements before applying structured changes directly to core routing files such as src/index.ts and src/router.ts.

Customizing router behavior and triggers is best handled through a step-by-step planning and implementation process that references core files like src/router.ts and src/config.ts to safely alter routing logic and integrate new capabilities.

You can safely modify triggers and routing logic by using a structured, interactive questioning pattern that clarifies requirements first, ensuring changes are planned and tested within the NanoClaw codebase before application.

Expanding channel capabilities requires updating specific configuration files, primarily src/config.ts and the groups/CLAUDE.md reference, to register new channels and define their behavioral triggers within the system.

An interactive customization workflow helps with code modification by asking targeted questions to understand user goals first, then pointing to key files and common modification patterns to implement changes accurately.

The questioning pattern requires clear answers to gather requirements effectively; ambiguous goals may slow down the codebase modification process, and all changes remain bound to the existing architecture defined in src/index.ts and src/router.ts.