Hot Tool Discovery and Orchestration

Dynamic Tool Registration

We’ve closed the gap in how Chalie handles new capabilities by implementing hot tool registration. Previously, adding a new tool to the system required a full restart of the worker processes to recognize the change. We introduced a ToolScannerThread—a daemon that monitors the backend tools directory on a 30-second interval.

This scanner works in tandem with the ToolRegistryService via a new callback hook. When it detects a new tool on the filesystem, it triggers a build and, if the tool defines a cron-based trigger, automatically spawns the necessary worker processes without interrupting the rest of the system. This makes the developer experience significantly smoother when prototyping new intents.

Repository Architecture & Cleanup

Today saw a massive cleanup of the codebase, affecting over 200 files. We’ve standardized the directory structure across the backend and frontend to ensure consistency as the project scales. This included organizing our cognitive architecture components—specifically the frontal cortex agents, memory services, and innate skills—into a more logical hierarchy. We also audited our migration scripts and prompts to ensure they align with the latest schema definitions.

Documentation Pipeline

To keep our external presence in sync with the codebase, we added a GitHub Actions workflow. Now, any changes made to the internal docs/ folder are automatically mirrored to the chalie-web repository. This ensures that the public-facing documentation always reflects the current state of the architecture and tool schemas without manual intervention.