Swappable Claude Profiles: Per-Project Configs via Container Mounting (Part 3)

Overview

The video shows how to keep Claude configuration in a host folder instead of a Docker volume, then mount a different folder into the container for each project. Each mounted folder acts as its own profile, with its own agents, memory and credentials. The presenter creates a project-scoped AL repository summarizer agent and looks at the memory files the agent writes automatically.

The second half covers a telemetry folder that loads Waldo’s MCP server, the LSP navigation plugin from Corpin Le, and the difference between legacy commands and skills. It shows skill context settings, supporting files, and sub-agents attached to skills. It closes with the presenter’s view that the container base is ready for general use and that problems should be reported as GitHub issues.

Key points

• Config is persisted into a host config folder rather than a Docker volume, and that folder is passed into the container as the Claude main folder. Any folder on disk can be used, not only the home directory.
• The host folder caches credentials and memory files and may contain sensitive information. Starting with a different folder asks you to log in again, so different authentications are possible.
• Agents can be created with project scope or personal scope; personal agents go into the mounted profile folder. The demo created a personal AL repository summarizer agent, which was saved automatically to the AL-specific user directory and created agent memory.
• Commands are described as the legacy approach. Skills follow the agent skills standard, can be invoked automatically by the model, and have no built-in generator.
• Skill context is either omitted or fork. Skills can have supporting files and helper scripts, and can be set up to use dedicated sub-agents.
• Waldo’s telemetry MCP server can be loaded into its own folder with its own instructions. The presenter currently uses one dedicated telemetry folder across all projects.
• The Corpin Le LSP plugin needs environment variables set in the container config. Marketplace setup had problems, including GitHub access being locked out in the container.

Features

AL objects mentioned

As heard in the captions. A name that matches one object page by exact type and name links to it; the others stay as named.

• other “cloud.markdown” at 2:45
• other “AL repo summarizer” at 9:51
• other “MCP service” at 14:34
• other “Waldo’s MCP server” at 16:36
• other “Corpin Le’s plugin” at 19:14

Quotes

• 2:20 “in its own volume basically we persisted into into a host config folder”
• 4:07 “We pass in the cloud AO development folder as the cloud main folder inside the container”
• 7:00 “I can have differently prepared user directories somewhere. It doesn’t have to be home. You can have it wherever you want on disk”
• 8:24 “create an agent that’s uh specialized in uh summarizing AL repositories to give a general overview over this that is human readable”
• 10:08 “it saved it automatically into the ALS specific user directory. Isn’t that cool?”

Disclaimers in the video

• 8:58 other: I don’t know if it’s general availability now or my user account has been enabled for the voice mode
• 14:08 other: Skills cannot be automatically defined
• 20:41 other: We locked out GitHub completely but it will be cloned into here
• 24:53 other: error compile isn’t installed in the container
• 30:24 other: There are always new features coming. which are really um which can be missed quite quickly.
• 36:44 coming-later: building that is probably taking more will take more longer than I want to be on stream for
• 40:02 subject-to-change: the base of of that uh container will not uh change anymore that much at least

Presenters (as heard): Unknown presenter.