LearnHarness vs Lobby

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.

Lobby

Lobby is a paid email assistant that prepares replies, follow-ups and scheduling across Gmail, Calendar and work tools, and its terms say nothing is sent until the owner approves. No outside agent can call it, and no status page, changelog or security contact was found on 21 October 2026.

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

Lobby

1. Don't plan to call Lobby from another agent. It works only inside its own app for the signed-in owner.
2. Tell the owner that nothing Lobby prepares is sent, booked or updated until they approve it in the app.
3. Check whether the 7-day trial takes a card before signing the owner up. The terms don't say.