Devotd Github
NewCoding agents

davidgodefroid/lea v0.1.2 — Containerized Execution of Claude Code Agents

lea is a Go tool that runs multiple Claude Code agents in containers and manages each agent's status and terminal from the deck.

Repositorydavidgodefroid/lea ↗

lea is a Go tool that runs multiple Claude Code agents in containers and manages each agent's status and terminal from the deck.

GitHub description: Many Claude Code agents. None of your machine.

stars
★ 2
Forks
0
Language
Go
License
Apache-2.0
Latest release
v0.1.2
Read original source ↗View on GitHub ↗

davidgodefroid/lea is a Go tool that runs multiple Claude Code agents in containers. The repository's latest release is v0.1.2. However, the provided information contains no changelog or release notes for this version. The functionality described in the README is running agents and managing each agent's status and terminal from the deck. Therefore, it is not possible to confirm what was added or changed in this release, and the scope of the tool introduced is limited to agent execution and management.

The core is how the access permissions passed to the container are restricted. The project directory is provided as readable and writable, while allowed ~/.claude configuration is provided read-only. SSH keys and credentials are not exposed to the container. Internet access goes through an egress proxy, that is, a server that relays outbound communication, and private networks are blocked by default. Setting boundaries for the execution environment, the settings, and network access alongside a tool that handles multiple agents is the characteristic presented in the README. The license is Apache-2.0.

That said, this description alone is not enough to judge the actual strength of the isolation or its security effect. The provided information contains no performance or security measurements, and the specific changes in v0.1.2 are not presented either. The repository has 2 stars. Therefore, what can be confirmed extends only to the design description of container execution and access restriction, and the improvements of the release or the level of protection must be verified separately.