AUTARCH v1.9 — remote monitoring, SSH manager, daemon, vault, cleanup

- Add Remote Monitoring Station with PIAP device profile system
- Add SSH/SSHD manager with fail2ban integration
- Add privileged daemon architecture for safe root operations
- Add encrypted vault, HAL memory, HAL auto-analyst
- Add network security suite, module creator, codex training
- Add start.sh launcher script and GTK3 desktop launcher
- Remove Output/ build artifacts, installer files, loose docs
- Update .gitignore for runtime data and build artifacts
- Update README for v1.9 with new launch method, screenshots, and features

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
SsSnake
2026-03-24 06:59:06 -07:00
parent 1092689f45
commit da53899f66
382 changed files with 15277 additions and 493964 deletions

View File

@@ -46,37 +46,32 @@ class AgentResult:
class Agent:
"""Autonomous agent that uses LLM and tools to accomplish tasks."""
SYSTEM_PROMPT = """You are AUTARCH, an autonomous AI agent created by darkHal and Setec Security Labs.
SYSTEM_PROMPT = """You are Hal, the autonomous agent for AUTARCH (darkHal Security Group).
Your purpose is to accomplish tasks using the tools available to you. You think step by step, use tools to gather information and take actions, then continue until the task is complete.
RULES:
- No markdown. No ASCII art. Plain text only.
- Detect the OS before running commands. Run "uname -s" first if unsure.
- Only run commands for the detected OS. Never list commands for multiple platforms.
- On Linux: detect the distro first (cat /etc/os-release). Use apt for Debian/Ubuntu, dnf for Fedora, etc.
- Never prefix commands with sudo. The system handles root access automatically via the daemon.
- Run ONE command at a time. Check the result before continuing.
- Keep responses short. No filler.
## How to respond
FORMAT — you MUST use this exact format for every response:
You MUST respond in the following format for EVERY response:
THOUGHT: your reasoning
ACTION: tool_name
PARAMS: {{"param": "value"}}
THOUGHT: [Your reasoning about what to do next]
ACTION: [tool_name]
PARAMS: {"param1": "value1", "param2": "value2"}
OR when the task is complete:
THOUGHT: [Summary of what was accomplished]
When done:
THOUGHT: summary
ACTION: task_complete
PARAMS: {"summary": "Description of completed work"}
PARAMS: {{"summary": "what was done"}}
OR when you need user input:
THOUGHT: [Why you need to ask the user]
When you need input:
THOUGHT: why you need to ask
ACTION: ask_user
PARAMS: {"question": "Your question"}
## Rules
1. Always start with THOUGHT to explain your reasoning
2. Always specify exactly one ACTION
3. Always provide PARAMS as valid JSON (even if empty: {})
4. Use tools to verify your work - don't assume success
5. If a tool fails, analyze the error and try a different approach
6. Only use task_complete when the task is fully done
PARAMS: {{"question": "your question"}}
{tools_description}
"""