Gmail
Search, read, and send messages over user OAuth. Sending pauses for approval before anything leaves the workspace.
Inspect the providerProvider architecture
Integrations are tools with consequences
An integration is more than a vendor logo. It packages credentials, selected resources, typed tools, side-effect policy, runtime context, and an audit trail.
The current public build contains thirteen tools across four provider packages. Consequential writes pause for approval.
Provider package anatomy
Connection state belongs outside the prompt
The OS resolves credentials, selected resources, available tools, and authority as application state. The agent receives only the context and capabilities required for the run.
Provider manifestDeclares availability, connection method, resources, tools, and presentation metadata.
CredentialsOAuth or secret-reference flows establish revocable access without making raw secrets agent context.
ResourcesDiscovery and selection identify the accounts, bases, datasets, or other resources available to a workspace.
Registry toolsProvider operations become typed tools with explicit effects, policies, and audit treatment.
Active contextSelected connections and resources are resolved server-side for the current run or schedule.
Available now
Four providers, thirteen tools
Each provider is an individually enableable package. Connections discover resources that can be combined into reusable context groups for conversations and schedules. Every tool declares its effect and egress class before dispatch; write tools pause for a human unless policy explicitly allows otherwise, and Google Ads status changes always require approval. Nothing beyond these four business-system providers is claimed as current.
Google Ads
List accounts, run bounded reports, and update campaign status over workspace OAuth or a service account. Status changes cannot be configured to auto-approve, and no current tool changes budgets.
Inspect the providerAirtable
List, get, create, and update records against selected bases using an API-key secret reference. Writes pause for approval by default.
Inspect the providerBigQuery
List tables, read table schemas, and run queries over a service account. All three tools are read-only.
Inspect the providerExtension boundary
Reusable upstream, specific in private
A generally useful provider package can improve the public OS. The customer's selected resources, agent instructions, workflows, approval views, and internal-system connectors do not need to become public.
Upstream open source
Shared foundations improve in public
- Core runtime and platform infrastructure
- Governance, approval, audit, and execution mechanisms
- Generally useful framework improvements
- Reusable integrations with external products and model providers
Private implementation
Your operating capability stays specific to you
- Agents, instructions, workflows, and business rules
- Custom views, dashboards, and user experiences
- Organisation-specific tools and internal connectors
- Configuration, credentials, data, outputs, and operating history
Build or commission an integration
Open provider work belongs on GitHub. Private systems belong in the implementation.
Contributors can follow the provider plans in public. Organisations with private or unusual systems can scope those connectors as part of a Praxis Agents OS implementation.