b9a498a3fd
CRITICAL FIX: chat.py had TWO execution paths causing inconsistent behavior: 1. Tool calling (correct) - used centralized command_patterns 2. Legacy JSON command parsing (broken) - bypassed SysadminTools This caused macha-chat to fail SSH connections while macha-ask worked. Changes: - Rewrote chat.py to use ONLY tool-calling architecture - All commands now go through SysadminTools.execute_command() - SSH commands use centralized command_patterns.py - conversation.py is now a lightweight wrapper for compatibility - Both macha-chat and macha-ask use the same code path - Updated module.nix to call chat.py directly Benefits: - Consistent behavior between macha-chat and macha-ask - Single execution path = easier to maintain - All SSH commands use explicit key paths - No more password prompts Fixes: - SSH from macha-chat now works correctly - Both interfaces use centralized command patterns
13 lines
269 B
Python
13 lines
269 B
Python
#!/usr/bin/env python3
|
|
"""
|
|
Macha conversation interface - legacy compatibility wrapper.
|
|
This module now uses the unified chat.py implementation.
|
|
"""
|
|
|
|
# Import the unified implementation
|
|
from chat import ask_main
|
|
|
|
# Entry point
|
|
if __name__ == "__main__":
|
|
ask_main()
|