https://stefanmaron.com/tags/claude-code/Recent content in Claude Code on Stefan Maron | Business Central & AL DevelopmentHugo -- gohugo.ioMon, 16 Mar 2026 09:00:00 +0100https://stefanmaron.com/posts/swappable-claude-profiles-container-mounting-part-3/Mon, 16 Mar 2026 09:00:00 +0100https://stefanmaron.com/posts/swappable-claude-profiles-container-mounting-part-3/After Part 2 we had a working standalone container — no VS Code required, no IPC socket surprises. But there was still one problem: a single global ~/.claude folder shared across everything. One set of instructions, one list of skills, one set of agents — regardless of whether you’re doing AL development, debugging telemetry, or investigating something completely different. That doesn’t scale. So this part introduces profile folders. You can watch the full stream on YouTube if you want to follow along.https://stefanmaron.com/posts/claude-code-standalone-docker-sandbox/Wed, 04 Mar 2026 17:00:00 +0100https://stefanmaron.com/posts/claude-code-standalone-docker-sandbox/If you watched Part 1 , you know the setup: I wanted to run Claude Code in bypass-permissions (cruise mode) without worrying about it going rogue on my host. The dev container approach worked, but someone on LinkedIn pointed out that even after my VS Code IPC mitigations, Claude Code could still reconstruct the IPC bridge and escape. So Part 1 was technically broken. Part 2 fixes that. You can watch the full stream on YouTube if you want to follow along.https://stefanmaron.com/posts/turning-streams-into-blog-posts/Tue, 24 Feb 2026 16:00:00 +0100https://stefanmaron.com/posts/turning-streams-into-blog-posts/I’ll be honest: I’m lazy when it comes to writing blog posts. Not lazy about sharing — I try to stream regularly, push code to GitHub, drop things in the community Discord. But sitting down to write a structured article about something I just spent two hours live coding? That rarely happens. The stream is the content. I jump on, explain what I’m doing, answer questions live, push something to GitHub, maybe add chapters via AI later.https://stefanmaron.com/posts/claude-code-dev-container-al/Fri, 20 Feb 2026 09:00:00 +0100https://stefanmaron.com/posts/claude-code-dev-container-al/A few weeks ago I shared my Claude Code configuration for AL development — the CLAUDE.md instructions, the agent profile, custom commands. It’s all public and you’re welcome to use or adapt it. But getting it into a new project still involves some manual steps, and there’s one thing that always annoyed me: I was running Claude Code outside my dev containers. Not because I wanted to, but because I didn’t want to authenticate inside every new container.https://stefanmaron.com/posts/al-development-claude-code-multi-agent-workflow/Wed, 28 Jan 2026 09:00:00 +0100https://stefanmaron.com/posts/al-development-claude-code-multi-agent-workflow/I’ve been using Claude Code quite a bit over the past year, and I think I finally have a process that actually works for AL development. One-off prompts don’t cut it for anything non-trivial — AL is niche enough that LLMs struggle without guidance, and large refactoring tasks blow up the context window within a few agent calls. What changed things for me was switching to a sub-agent workflow. You can watch the full stream on YouTube if you want to follow along.