OpenSana and AI CLIs

The dev container is most useful when you want OpenSana and local AI CLIs to work together inside the same isolated environment.

OpenSana Profiles

The container mounts your host ~/.config/opensana/ directory into the container.

That means you can:

• reuse existing OpenSana profiles
• run opensana setup inside the container
• keep API keys and profile config outside the repo

If the directory does not exist on the host, create it first:

mkdir -p ~/.config/opensana

Running Claude Code

Claude Code is preinstalled in the container.

Typical usage:

claude

cd /workspace/apps/web && claude

Combining With OpenSana

A practical isolated workflow looks like this:

1. Open the repo in the dev container.
2. Verify your OpenSana profile is available.
3. Run opensana init mcp or opensana init skill if needed.
4. Start the AI CLI inside the container.
5. Use the client against the repo from the containerized environment.

Why This Matters

This keeps:

• repo files
• MCP config
• OpenSana profile resolution
• AI CLI execution

in one controlled environment instead of splitting them across host and container setups.

Related Sections

• CLI
• Working with AI