Claude Code integration for workspace-scoped control.
Claude Code is a shallow adapter target. The smaller set of settings, permissions, and skill surfaces stays explicit.
The limited but useful adapter scope is intentional.
Describe what the control plane can actually map into Claude Code.
Stay close to the runtime's real settings, permissions, and skill surfaces.
Folder-based skill artifacts and local discovery.
Project or local settings that can be managed without overreaching.
What is allowed, what is denied, and where prompts are required.
Rules and objects that belong to one repository or project.
Keep the adapter honest about what is managed and what stays manual.
The point is clear coverage, not false parity with every runtime.
The small set of configuration surfaces the control plane owns.
What remains the user's responsibility in a workspace.
How the client knows the runtime accepted the change.
If a field cannot be written safely, the adapter says so.