LearnHarness vs Leon

LearnHarness

The in-app agent reads files but cannot change them or run commands, and a bundled skill gives other agents a documented read-only view of sessions and the knowledge graph. The project is 14 days old at 0.4.0, its file reads reach the whole home directory without approval, and it has no security policy.

Leon

Connected-app credentials are encrypted per profile and the Gmail connection is read-only. The 2.0 Developer Preview has no tagged release, runs tools and a 30-minute proactive pulse with no approval step, listens on every network interface with client authentication off, and sends telemetry by default.

LearnHarness

1. Use the bundled skill (skills/learnharness/SKILL.md) to read a learner's record. It needs Python 3.10 or later and writes nothing
2. Pass --format json before the subcommand, for example python3 -B scripts/graph.py --format json propositions
3. Treat stored answer keys and teacher prose as model-authored. A proposition in the graph is not evidence the learner understood it
4. Do not read auth.json, which sits one folder above the data folder and holds provider keys in plain text
5. Close the app or re-read when a stable snapshot matters. The readers do not lock files while the app writes

Leon

1. Clone the develop branch for 2.0. npm install --global @leon-ai/cli and docs.getleon.ai install and describe the legacy 1.0 betas
2. Set client_interface.auth.enabled: true and a LEON_PROFILE_TOKEN before the machine joins a shared network. The server binds 0.0.0.0
3. Set telemetry_enabled: false and runtime.pulse_enabled: false in the profile config.yml for an unattended or private run
4. Use availability.tools.allowed to limit tools. Shell, file writes, computer use and browser control are otherwise available to the agent with no approval prompt
5. Back up LEON_CONNECTIONS_ENCRYPTION_KEY from the profile .env. Without it the stored connections cannot be read