⌘AI clients
Codex
Approved profiles, scoped resources and governed operations on a qualified client path.
THE INTEGRATION CATALOG
Keep your stack.
Connect the control.
Clients, protocols, tools and infrastructure play different roles. Discover where each fits—and the boundaries that need qualification.
Catalog roles and roadmap direction, not a blanket statement of shipped support. See the capability model ↗
✳AI clients
Claude Code
A second supported coding context with separate authorization and explicit configuration state.
↗Tools & knowledge
GitHub
Repository-scoped knowledge and useful governed actions on selected resources.
NTools & knowledge
Notion
Selected knowledge sources, source lineage and reviewed publication boundaries.
⋈Protocols
MCP
Authorized tool discovery and invocation into shared governance—not a second policy engine.
⌁Protocols
Agent Client Protocol
A specifically qualified client protocol and version; not a blanket claim about every ACP.
≋Infrastructure
Temporal
Waits, callbacks and recovery beneath DriftGate’s authority and evidence model.
⛶Infrastructure
Google Cloud
Cloud services and deployment patterns with explicit identities and ownership.
◎AI providers
OpenAI
Supported model and agent interfaces, qualified independently from other access surfaces.
△Tools & knowledge
Google Drive
Scoped knowledge access with explicit source permissions, revisions and sharing boundaries.
◒Tools & knowledge
Linear
Selected project resources through a qualified knowledge or action adapter.
〰AI providers
Retell
Voice-agent actions governed through specifically supported provider boundaries.
BUILD WITH INTENTION