Praxis Agents OS
View on GitHubRead the docs

Six integrations, forty tools, one approval rule for each

An integration in Praxis is more than a connected account. It is a set of typed tools, each with a declared effect and a policy that says whether it may run on its own.

Read the integration architectureSee how it works

Each provider is switched on per deployment. A provider you have not enabled contributes no tools and no UI.

What each integration lets an agent do

Reads run on their own unless you say otherwise. Writes wait for a person. Google Ads and Notion writes cannot be made automatic by any agent setting.

  • Gmail

    Available now
    Tools
    3
    Connects
    OAuth, per user
    Reads
    Search and read messages in the connected mailbox.
    Writes
    Send a message. Stops for approval by default, with the recipients, subject and body shown for editing.

  • Google Ads

    Available now
    Tools
    17
    Connects
    OAuth or service account, per workspace
    Reads
    List accounts and run bounded reports against selected accounts.
    Writes
    Campaign status, negative keywords and lists, device bid adjustments. Every write requires approval and cannot be set to Auto.

  • Google Analytics

    Available now
    Tools
    5
    Connects
    OAuth or service account, per workspace
    Reads
    Discover report fields, check compatibility, and run standard and realtime GA4 reports across selected properties.
    Writes
    None. Read-only.

  • Airtable

    Available now
    Tools
    4
    Connects
    API key, per workspace
    Reads
    List and get records in selected bases.
    Writes
    Create and update records. Approval by default.

  • BigQuery

    Available now
    Tools
    3
    Connects
    Service account, per workspace
    Reads
    List tables, read schemas, run queries. Per-table row filters are enforced before a query is authorised.
    Writes
    None. Read-only.

  • Notion

    Available now
    Tools
    6
    Connects
    OAuth, per user
    Reads
    Search and read pages and databases. Notion pages can also feed the knowledge base.
    Writes
    Create and update pages. Every write requires approval and cannot be set to Auto.

Pick the accounts each run can see

Connect a Google Ads manager account and Praxis lists every account under it. Connect Analytics and it lists the properties. For each conversation or schedule you choose which are in scope, or reuse a saved context group.

What an integration is made of

The same five parts for every provider, so a new one behaves like the others from the day it ships.

  1. ConnectionOAuth, an API key reference, or a service account. Raw secrets are never stored in the app; the API accepts references to your secret manager.
  2. ResourcesPraxis discovers what is inside a connection: ad accounts, properties, bases, datasets, mailboxes. You choose which ones agents may use.
  3. ToolsEach provider exposes typed tools that declare whether they read or write, where data goes, and what approval policy applies.
  4. Active contextFor every conversation and schedule, you pick the resources in scope. The agent sees only those.
  5. AuditEvery tool call is recorded with the actor, the requester, the tool, the provider and the outcome.

What is being built next

Planned work is written up as public implementation plans before any code lands. None of these is available today.

  • Planned

    Microsoft 365

    Outlook mail and calendar, SharePoint files and a SharePoint knowledge source, on a Microsoft Graph foundation.

  • Planned

    Google Search Console

    Site discovery and organic performance reporting first, reindexing actions after.

  • Planned

    Remote MCP servers

    Workspace-governed connections to external MCP servers, under the same policy and audit rules.

Reusable connectors go upstream. Yours stay yours.

A generally useful provider can be contributed to the open-source project. A connector to your internal system, and the agents and rules around it, stay in your private implementation.

Open source, upstream

The platform improves in public

  • The runtime, the workspace and the tool registry
  • Approvals, audit and the rest of the governance layer
  • Fixes and improvements that help everyone
  • Integrations with products other people also use
Private, yours

What is built for you stays with you

  • Your agents, their instructions and your business rules
  • Views and dashboards built for your team
  • Connectors to your internal systems
  • Your configuration, credentials, data and history

Public providers are planned on GitHub. Private ones are built in an implementation.

View integration plansDiscuss a private integration