How turlockmike/hataraku works
• Autonomous Coding Agent & Task Engine: This is at the heart of Hataraku. Represent modules such as:
• Agent creation and management (e.g., src/core/agents)
• Task creation and execution (e.g., src/core/task.ts, sample tasks, and task history)
• Workflow Orchestration: Capture how multi-step operations are coordinated (e.g., src/core/workflow).
• CLI Interface: Indicate the CLI module (e.g., src/cli and related commands) which interacts with the core.
• Configuration & SDK Integration: Show components handling configuration (e.g., src/config, profile manager), environment setup, and integration logic.
• Tool & Provider Integration: Include the built-in tool integration system and external AI providers (e.g., src/core/providers for OpenRouter, Anthropic, Bedrock, etc.).
• Auxiliary Services & Utilities: Represent supporting services such as file system utilities (src/utils), diff and thread management, and experimental features.
• Data flow from configuration modules to the Agent and Task Engine, ensuring system initialization.
• Interactions between the agent responsible for autonomous decision-making and the providers’ modules that supply AI responses.
• Connections between the workflow module and individual tasks to highlight orchestrated operations.
• Auxiliary communication, such as logging, error handling, and unit tests, which support the core functionality.
Architectural Patterns and Design Principles
• Modular Separation: Use clear divisions between core modules, configuration, CLI, and external integrations. Emphasize modularity (each directory like “core,” “config,” “cli,” and “providers” is an individual component).
• Extensibility & Flexibility: Note how the system supports multiple AI providers and tool integrations, reflecting a plug-in based architecture.
• Testing and Mocks: Represent the emphasis on robust testing (the __tests__ directories and mocks under src/__mocks__) as important supporting infrastructure.
Relevant Technologies and Frameworks
• Node.js/TypeScript Environment: Note the presence of tsconfig files and extensive TypeScript usage.
• CLI and SDK Libraries: Include how the CLI commands (src/cli/commands) are the entry point for both SDK and autonomous agent execution.
Elements
• Use clear, descriptive labels for each major component (e.g., “Autonomous Agent Module,” “Task Engine,” “Workflow Orchestrator,” “CLI Interface,” “Configuration Manager,” “Provider Integrations”).
Detailed Breakdown
• Agent & Task Management submodules.
• Workflow orchestration.
• Diff, thread, and tool support.
• Above or to one side, illustrate “Configuration” and “Environment Setup,” showing how files like tsconfig, .eslintrc, and other configurations feed into the core.
• To the right, place “External Integrations” and “Providers” (each labeled with names like OpenRouter, Anthropic, Bedrock).
• “Testing & Mocks” as a support area that interfaces with the core engine; this adds clarity that a robust test infrastructure is in place.
• Optionally, add a “Documentation/Examples” panel (tying the docs/ and examples/ directories) which demonstrates usage and reinforces how the design supports extensibility.