What I took from Foundations is that the folder is the product and the model is the engine. Engines get swapped. So I've been building a small desktop app that opens a folder of plain files, a team of workers each with its own rules, and runs Claude Code on the buyer's own Mac. The buyer doesn't need VS Code. The app is only a window onto the folder. The part I want to get right is the sign-in. I'd like each buyer to use their own Claude account, the way they already sign in to Claude Code. I never see or store the login, and their usage is billed to them, not me. Two Anthropic pages read differently on that: - The legal and compliance page says an end user can sign in to the unmodified Claude Code binary with their own subscription, including where a platform hosts it. - The Agent SDK overview says developers building on the SDK should use API key authentication, and may not offer claude.ai login for their products unless Anthropic has previously approved it. My case sits between the two, because the app runs the real Claude Code binary and I'm only the window. Their support chat quoted the policy, said it couldn't rule on my design or grant an approval, and said the docs describe no approval process beyond contacting them. So I sent the whole question through that chat on the 10th. It's been passed to a person, and the written answer comes by email. Nothing yet. Until it does, I'm not building anything that assumes the answer. The product stays as files, so a buyer with Claude Code can open the folder and work with no app at all. API keys go only to services (voice, pictures, email), never to the engine. What I wonder: - Has anyone put this question to Anthropic, and what came back? - If you sell ICM setups to people who aren't builders, how do your buyers sign in? - Did most of you end up at "files only, they open it in their own Claude Code"? Super thanks!