conductor-tasks

The server heavily interacts with the local filesystem (reading/writing TASKS.md, creating/managing IDE-specific rule files, performing codebase analysis, and generating/proposing diffs for code changes). This grants significant power, which, if misused or exploited via prompt injection, could lead to unintended or malicious file operations within the workspace. However, the system includes some mitigations like path normalization, explicit file path parameters for sensitive operations, and a hash check for `propose-diff` to prevent applying changes to modified files. API keys are managed via environment variables, not hardcoded. No direct use of `eval` or obvious obfuscation was found in the truncated source.