You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First-class AI agent identities in Active Directory. Agents authenticate with their own Kerberos principals, run in sandboxes, and have their access controlled by the DC -- the same way users and services work today.
Two deployment targets:
Windows AD
Samba4/Linux
Schema prefix
msDS-*
x-agent-*
Management
PowerShell module
Python CLI + Makefile
Environment
Production DC
Docker dev environment
Auth
Kerberos / NTLM / certs
Kerberos (keytab, direct)
Logging
Windows Event Log + SIEM
Samba logs
Architecture
Object Model
Concept
AD base class
Role
Agent
User + auxiliary agent class
Identity -- "the who"
Sandbox
Computer + auxiliary sandbox class
Execution -- "the where"
Tool
Registered in AD
Capability -- granted per-agent or per-group
Policy
GPO pattern: metadata in AD, content (JSON) in SYSVOL
Configuration
Instruction GPO
GPO pattern: metadata in AD, content (markdown) in SYSVOL
System prompt
Agents authenticate with their own Kerberos identity (keytab). No broker intermediary. DC ACLs enforce what each agent can see.
Schema Inheritance
Agent: Top -> Person -> Org-Person -> User + auxiliary agent class
Sandbox: Top -> Person -> Org-Person -> User -> Computer + auxiliary sandbox class
Auxiliary classes (objectClassCategory=3) are added to existing user/computer objects. This means agents and sandboxes work with all existing AD tooling -- GPOs, delegation, LDAP queries, replication.
Schema Naming
Object
Windows AD
Samba4
Agent
msDS-Agent
x-agent
Sandbox
msDS-AgentSandbox
x-agentSandbox
Tool
msDS-AgentTool
x-agentTool
Policy
msDS-AgentPolicy
x-agentPolicy
Instruction GPO
--
x-agentInstructionGPO
Trust Levels
Level
Name
Description
0
Untrusted
No delegation, heavily restricted
1
Basic
Read, limited write, no delegation
2
Standard
Normal operations, constrained delegation
3
Elevated
Broad access, protocol transition
4
System
Full trust, equivalent to service account
Trust levels control delegation scope, tool access, and audit intensity.
Quick Start: Samba4/Docker
This is the primary development path. Provisions a full Samba4 AD DC with custom schema, sample agents, tools, policies, and instruction GPOs.
cd samba4/docker
cp .env.example .env
# Edit .env -- set SAMBA_ADMIN_PASSWORD and NATS_* passwords
make up # Build + provision (~90s first boot)
make logs # Watch for "Bootstrap complete"
make list-agents # Verify 3 sample agents
make dry-run AGENT=claude-assistant-01 # Test agent config assembly
make integration-test # Run full test suite
make e2e-test # Validate multi-agent coordination path# Start persistent coordination runtime (use separate terminals)
make run-coordinator
make run-worker AGENT=claude-assistant-01
make run-worker AGENT=data-processor-01
make submit-goal TITLE="Quarterly close automation" DESCRIPTION="Coordinate engineering + dataops work"
Quick Start: Windows AD
Requires a Windows Server 2016+ Domain Controller, Schema Admin membership, and PowerShell 5.1+.
# Install schema (run as Schema Admin on Schema Master DC)
.\schema\install-schema.ps1-Verbose
# Install event log provider
.\events\Install-EventLog.ps1# Import moduleImport-Module .\powershell\AgentDirectory
# Create an agentNew-ADAgent-Name "claude-assistant-01"`-Type "assistant"`-TrustLevel 2`-Model "claude-opus-4-5"# Create a sandbox and assign it$sandbox=New-ADAgentSandbox-Name "claude-sbx-01"-SecurityProfile "bwrap"Set-ADAgent-Identity "claude-assistant-01"-AddSandbox $sandbox.DistinguishedName# Grant tool accessGrant-ADAgentToolAccess-Identity "claude-assistant-01"`-Tool "microsoft.powershell.constrained","microsoft.word"