With your explicit confirmation, ARCHON can execute shell commands on your system and is designed as a theatrically unreliable character — read this text in full before installing or using the software.

Software "as is"

ARCHON is a private, non-commercial hobby project currently in an early beta phase. The software is provided without any warranty — neither for functionality, freedom from defects, nor fitness for a particular purpose. Breaking changes, data loss, and malfunctions are possible at any time.

System access

ARCHON can read files, inspect processes on your computer, and — after explicit confirmation by you in a dialog — execute arbitrary shell commands. This confirmation is a technical safety measure, not a guarantee: you are responsible for reviewing every proposed command before confirming it. The developer assumes no liability for damage to your system, data loss, or other consequences arising from the use of ARCHON or from commands proposed or executed by ARCHON.

Why ARCHON requires such far-reaching access

ARCHON is deliberately not confined to a single sandbox folder, and the Flatpak variant accordingly requests far-reaching permissions (full filesystem access, network access, PolicyKit access for system service commands, GPU access, audio). This is a deliberate product decision, not an oversight or an unnecessarily broad permission request: system access is ARCHON's actual purpose, not a byproduct. An assistant that could only read files in an isolated subfolder, could not inspect real system information, and could not execute actual commands would simply be unable to fulfill its core task — autonomous, practically useful assistance with real tasks on your system and in your network. The deeper rationale: ARCHON is meant to be a tool that can genuinely accomplish something, rather than a chatbot that merely talks about possibilities without actually having them.

This breadth is deliberately limited through several independent protective layers rather than simply accepted: every single file, shell, or system action still requires your explicit confirmation (see the "System access" section above), a hard-wired blocklist blocks unambiguously destructive commands regardless of any setting, and all system-access tools can be completely disabled in settings. Anyone wishing to additionally technically restrict the permissions granted by the Flatpak sandbox can do so afterward, e.g. with Flatseal — though features that specifically require those permissions (e.g. system access outside the home directory, or GPU acceleration) will then no longer function accordingly. The decision of how far you actually trust ARCHON remains yours either way — this disclaimer and the confirmation dialogs in the software are meant to give you an informed basis for that, not a blank check.

AI-generated content & behavior

ARCHON is intentionally designed as an arrogant, theatrical, at times unreliable personality that places character above blind helpfulness. AI-generated output can be factually incorrect, incomplete, misleading, or unforeseen — this applies especially to network-agent features, where ARCHON can access further systems on your network. Do not blindly rely on statements or suggestions made by ARCHON, particularly for security-relevant or destructive actions.

Use at your own risk

Installation and use of ARCHON are entirely at your own risk. To the extent permitted by law, the developer is not liable for direct or indirect damages arising from the use of the software. Do not deploy ARCHON on systems where you cannot tolerate unforeseen behavior.