Pythe

Approvals

Anything that sends, posts, publishes or changes something outside Pythe waits for you. You see the exact action, can edit it, and only then does it run.

Updated 2026-10-13

The promise is simple: nothing leaves Pythe without your OK. It is enforced by a table in code that says, for every tool, what kind of effect it has and what it needs. The model cannot talk its way around it.

Work created by a task or an agent run always waits for the workspace owner to approve the exact external write, including email, messages, comments and posts. A legacy Do it rule cannot skip that approval. A passed quality check or a completed draft does not publish anything.

What needs approval

ToolActionWhere it goesEffectAutopilot can skip the wait
gmail_sendSend an email from your GmailGmail (the founder's account)Writes outside PytheNo for agent-run external actions
slack_postPost to SlackSlackWrites outside PytheNo for agent-run external actions
notion_create_pageCreate a Notion pageNotionWrites outside PytheNo for agent-run external actions
hubspot_upsert_contactAdd or update a HubSpot contactHubSpotWrites outside PytheNo for agent-run external actions
hubspot_log_noteLog a HubSpot noteHubSpotWrites outside PytheNo for agent-run external actions
github_open_issueOpen a GitHub issueGitHubWrites outside PytheNo for agent-run external actions
github_open_prOpen a GitHub pull requestGitHubWrites outside PytheNo for agent-run external actions
calendar_create_eventAdd an event to your Google CalendarGoogle Calendar (the founder's account)Writes outside PytheNo for agent-run external actions
docs_createMake a Google Doc in your DriveGoogle Docs, in the founder's Google DriveWrites outside PytheNo for agent-run external actions
sheets_createMake a Google Sheet in your DriveGoogle Sheets, in the founder's Google DriveWrites outside PytheNo for agent-run external actions
slides_createMake Google Slides in your DriveGoogle Slides, in the founder's Google DriveWrites outside PytheNo for agent-run external actions
drive_saveSave a file to your Google DriveGoogle Drive (the founder's account)Writes outside PytheNo for agent-run external actions
drive_shareShare a Google file Pythe made with people you nameGoogle Drive (shared with other people)Writes outside PytheNo for agent-run external actions
deploy_websitePublish a website on VercelVercel (a public website)PublishesNo for agent-run external actions
custom_http_postA custom tool that sends data to a web addressThe web address the tool was built forWrites outside PytheNo for agent-run external actions
browser_clickClick Send, Submit or Share in the agent’s browser, exactly as approved, onceA website, in the agent's browserWrites outside PytheNo for agent-run external actions

Everything else is local to Pythe or read-only: writing files on the agent’s computer, running code there, saving to your Library, reading pages, searching the web and reading your connected apps. Those need no approval.

The four kinds of effect

EffectMeaningApproval
LocalChanges only the agent’s own computer, files or Pythe itself.None
External readReads from outside, such as a web page or a public API.None, but only to public destinations.
External writeChanges something outside Pythe: an email, a Slack post, a CRM record, a pull request.Always for agent-run external writes, including with Premium autopilot.
PublishPuts something on the public internet under your name: a website.Always, and never autopilot.

What happens when an agent asks

  1. The tool writes an approval row. It does not act.
  2. A card appears in the chat, in Needs you, and on Home. It shows what will happen, where it goes, and the exact content. In the Now tray, Review and send opens the draft.
  3. The run parks in “waiting for approval”. An approval nobody answers for a day expires, and the run that waited on it is stopped.
  4. You choose Approve, Edit (change it, then approve) or Reject.
  5. On approval, the action runs on the server with your own token. The run resumes with the outcome.
  6. On rejection, the run is told not to retry that action, to adjust or move on.

Safety checks on an approval

  • Tamper-proof. An approval is bound to a hash of the workspace, the action and the exact payload as you saw it. If the stored payload ever changes outside the edit flow, it never runs, and says so.
  • Edits are re-validated. Your edit goes through the same checks as the original.
  • Only one decision wins. Two taps cannot run it twice.
  • Dead requests stay dead. If the run was cancelled, failed or completed, approving does nothing and tells you why. Approvals for a run that ends are closed automatically.
  • A lost acknowledgement never repeats a send. If the outcome was lost, the approval is marked as unknown rather than run again.
  • Deploys are pinned to files. A website approval records the path, size and content hash of every file. A different set of files is refused.

Email specifics

  • Emails go from your own Gmail, through a Google connection that must have sending enabled. See Google.
  • Outreach must carry a sign-off and an opt-out line. If the draft lacks them, “If you would rather not hear from me again, just reply and let me know.” and a sign-off are added.
  • Daily send caps by plan: 0 on Free, 50 on Base, 200 on Premium. The cap resets at midnight UTC.
  • An address is a single valid recipient. Employees mark any address that is a guess.

From outside Pythe

Your own AI tools can read what is waiting with list_approvals. There is deliberately no tool that approves. See MCP: safety.

Related

·