Skip to content

docs: say lockhttp protects only agents running inside lea - #72

Merged
DavidGodefroid merged 1 commit into
mainfrom
docs/needs-lea
Nov 14, 2026
Merged

DavidGodefroid merged 1 commit into
mainfrom
docs/needs-lea

Conversation

@DavidGodefroid

Copy link
Copy Markdown
Owner

lockhttp's gate is only on the egress path of containers lea starts with LEA_LOCKHTTP=1. An agent started directly on the host never goes through it. Several lines read as if any agent were protected ("Let any AI agent use the web", "every outbound HTTP(S) request of your agent").

Docs only, no code change:

  • README: tagline, intro and Lock Family row say "running in lea"; new IMPORTANT callout: the agent must run inside lea, an agent outside lea is not protected; the quick-start closing paragraph says lockhttp is not on the path outside lea.
  • Site (lockhttp.com): home hero lead, meta/og/twitter descriptions and quick-start prose; FAQ "Which AI agents does it work with?".
  • Security model (docs/security-model.md and site/security/): agents not run inside lea listed as out of scope.

🤖 Generated with Claude Code

The gate is on the path only of the containers lea starts with
LEA_LOCKHTTP=1. "Let any AI agent use the web" and similar lines read as
if an agent started directly on the host were protected too. Reword the
README tagline, intro and quick start, the site's hero, descriptions and
FAQ, and list agents outside lea as out of scope in the security model.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@DavidGodefroid
DavidGodefroid merged commit a3761ad into main Nov 14, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant