Secure Env Manager

A Linux toolkit that isolates AI coding agents, credentials, browser sessions, editor state, and project files with Distrobox and LUKS.

Live 3D architecture

The scene beside this panel is this system's architecture. Drag to rotate, scroll panel to read on.

Problem

AI coding tools, client work, and sensitive projects can all end up sharing the same host home directory, credentials, browser profiles, and editor state unless isolation is deliberate.

Contribution

Built scripts and environment setup for LUKS-backed Distrobox environments with hidden host home access, per-environment storage, generated SSH keys, browser/editor launchers, audio/video support, and verification commands.

Architecture

Each environment gets its own encrypted sparse image and container home. The host home is masked, Linux capabilities are restricted, desktop apps still work through controlled bridges, and developer tools run as an isolated user.

Technical decisions

LUKS encrypted sparse images for environment data

Distrobox containers with host-home masking

Per-environment SSH keys

Capability restrictions instead of privileged containers

Browser sandbox support and desktop launchers

Tradeoffs

Practical isolation over enterprise policy complexity

Linux-first security model over cross-platform convenience

Developer usability without giving tools ambient host access

Outcome

A concrete AI-security tooling project: each agent context gets its own encrypted storage, browser profile, editor state, SSH identity, and filesystem boundary.

Stack and domains

Linux
Distrobox
Podman
LUKS
Bash
desktop integration
developer security

Links

GitHubgithub