AI-Container
Podman based container for isolating AI tooling for a individual project.
Context
In the past, I have repeatedly observed and experienced coding agents accessing or using files and content which they either weren't supposed to, or even technically "did not have access to."
On one occasion, for example, file access was explicitly restricted (e.g., the path was blocked). However, the agent exploited its ability to run bash commands, using them to traverse and scan the restricted paths instead of relying on standard read/write methods.
For this reason, I believe it is essential to implement clear restrictions or a contextual sandbox that is shared with the AI, and which it cannot as easily circumvent by simply invoking a different command.
Prerequisites
- Podman (>= 5.0) - Container runtime. Install
- Python (>= 3.13) - Required for the CLI. Install
- uv - Used to install and run the CLI. Install
Image builds and volume creation are performed through the Podman Python SDK, which talks to the Podman service socket. Make sure the socket is running:
systemctl --user enable --now podman.socket
Installation
Install the ai-container package:
uv tool install ai-container
Or from source:
git clone https://github.com/yourusername/ai-container.git
cd ai-container
uv tool install .
The ai command will then be available.
Usage
Basic Commands
ai agent pi /path/to/project # Run PI coding agent
ai agent opc /path/to/project # Run OpenCode coding agent
ai agent claude /path/to/project # Run Claude Code
ai agent aic /path/to/project # Run aichat
ai agent llm /path/to/project # Run llm
ai shell /path/to/project # Interactive shell in container
ai agent <tool> [paths...] [-- args...] is the single entry point for every
tool. Valid tools: pi, opc, claude, aic, llm.
Pass additional arguments to the tool after --:
ai agent pi /path/to/project -- --verbose --model claude-3-sonnet
Mounting Folders
The paths you pass decide what the container sees in /workspace:
ai shell # nothing mounted, empty /workspace
ai shell ./app # contents of ./app -> /workspace
ai shell ./mount1 ../mount2 # ./mount1 -> /workspace/mount1
# ../mount2 -> /workspace/mount2
When you pass several paths, each folder is mounted under its own name, so folder names must be distinct.
Rebuilding the Container Image
The container image is built automatically on first use via the Podman SDK.
When you want to pull in the latest tool versions, force a rebuild with the
image rebuild command:
ai image rebuild # rebuild the default (configured) image
ai image rebuild pi pi-python # rebuild several images, parents first
ai image rebuild pi,pi-python # same, comma-separated
ai image rebuild --all # rebuild every image, parents first
Custom Environments
Need a specific toolchain (Rust, Go, an extra editor, ...)? Define a custom
environment: a thin image built FROM aic:base that adds your tooling on top
of everything the base image already provides.
Select an environment with the -e/--env option of shell and agent;
image rebuild takes image names as arguments:
ai shell -e rust . # shell in the rust environment
ai agent -e rust pi . # run pi in the rust environment
ai image rebuild rust # (re)build the rust image (FROM aic:base)
ai image rebuild rust,go pi # environments and built-in images can be mixed
Manage environment definitions with the env group:
ai env list # show environments and whether images are built
ai env new rust # scaffold a Containerfile (FROM aic:base)
ai env new rust --edit # scaffold and open it in $EDITOR
ai env edit rust # edit the Containerfile
ai env path rust # print the Containerfile path
ai env remove rust --purge # delete the definition (and its image)
Definitions live under ~/.config/ai-container/environments/<name>/
(honoring XDG_CONFIG_HOME). The directory is also the build context, so you
can COPY local files into your image. A scaffolded Containerfile looks like:
# rust environment -- extends the ai-container base image.
FROM aic:base
RUN curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs \
| sh -s -- -y --default-toolchain stable
ENV PATH="/root/.cargo/bin:${PATH}"
WORKDIR /workspace
Without -e, the default base environment is used. Persistence volumes
(config, state, share, pi-config, claude) are shared across all
environments, so credentials and config are entered once and work everywhere.
Config Files
Defaults for -e/--env and the global flags (--log-level, --dryrun) can be set
in a TOML config file, so you don't have to repeat them on every invocation.
Files are merged from several sources, highest precedence first:
./.ai-container.toml— project-local, in the current working directory~/.config/ai-container/config.toml— user config (honorsXDG_CONFIG_HOME)~/.ai-container.toml— home dotfile- Built-in defaults
Command-line flags always override config files. Each layer only needs to set the keys it cares about; the rest fall through to the next layer.
# .ai-container.toml
env = "rust" # default environment
log_level = "DEBUG" # one of: DEBUG, INFO, WARNING, ERROR, CRITICAL
dryrun = false
Provided Tools
- PI - Coding agent for generation, analysis, and refactoring
- OpenCode - AI-powered coding assistant
- Claude Code - Anthropic's official coding agent
- aichat - Interactive AI chat interface
- llm - Command-line tool for LLM interaction
Configuration & Persistence
First run: The container image is built (one-time, takes a few minutes).
Tools use their standard configuration methods (within the container):
- aichat:
~/.config/aichat/config.toml - llm:
~/.config/llm/+ environment variables - PI:
~/.pi/ - OpenCode:
~/.config/opencode/ - Claude Code:
~/.claude/
Configuration persists automatically across all runs and containers through named Podman volumes (config, state, share, pi-config, claude). Configure once, use everywhere:
# First run: setup credentials
ai shell /path/to/project
# Inside container: aichat, llm keys set openai <key>, etc.
# Subsequent runs: credentials available automatically
ai agent pi /path/to/project
Other/Previous Work
Metadata
Release files for ai-container 0.21.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| ai_container-0.21.0.tar.gz | 48.0 kB | Without provenance | Details for ai_container-0.21.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ai_container-0.21.0-py3-none-any.whl | Python 3 | none | any | Details for ai_container-0.21.0-py3-none-any.whl |
Total release size: 67.9 kB
Release files / ai_container-0.21.0.tar.gz
| Download URL | ai_container-0.21.0.tar.gz |
|---|---|
| Size | 48.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
605e14d4869cd85276efe909068a3cb9fccb67d588ae0567ad1e678dfc931b18
|
|
BLAKE2b-256 checksum How to use checksums |
9def0d8a8fc998ccad1a4af4b67767a2924e9e448ddacd4902dfe952413c8c7f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.6 {"installer":{"name":"uv","version":"0.13.6","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / ai_container-0.21.0-py3-none-any.whl
| Download URL | ai_container-0.21.0-py3-none-any.whl |
|---|---|
| Size | 19.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
398e77b707a71513da0438b2a944fa706dc960560a214a47e0b32cf781e26983
|
|
BLAKE2b-256 checksum How to use checksums |
a676b443cb395a960d3745488a0f8b5596585da03df2931fe08e7c263f55f925
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.6 {"installer":{"name":"uv","version":"0.13.6","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for ai-container 0.21.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.