Skip to main content

Connect Superhuman Mail to GitHub Copilot

Give GitHub Copilot governed access to Superhuman Mail’s 33 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Set up

Add Superhuman Mail to GitHub Copilot in four steps

Admins approve the server once. Everyone in GitHub Copilot then gets it through the same governed connection.

  1. 1

    Approve Superhuman Mail in Runlayer

    Add Superhuman Mail from the catalog and choose who can use it and which of its tools are allowed.

  2. 2

    Connect GitHub Copilot to Runlayer

    GitHub Copilot gets connector tools through the Runlayer Plugin, and reaches Superhuman Mail’s 33 tools through the plugin’s search and execute tools.

    GitHub Copilot setup guide
  3. 3

    Sign in to Superhuman Mail

    Sign in the way Superhuman Mail requires. Runlayer holds the credentials so they stay out of the client’s configuration.

  4. 4

    Use Superhuman Mail from GitHub Copilot

    Superhuman Mail’s approved tools appear in GitHub Copilot. Every call is checked against policy and recorded.

Tools

33 Superhuman Mail tools in GitHub Copilot

Runlayer policy decides which of these GitHub Copilot users can call.

  • Add account

    Start linking an additional Superhuman Mail account to this session so it can be acted on alongside the current account.

  • Create or update draft

    Compose an email on behalf of the user.

  • Create or update event

    Create a new calendar event or edit an existing one.

  • Create or update reminder

    Create or reschedule a reminder on a Superhuman Mail thread.

  • Create or update snippet

    Save a reusable Superhuman Mail snippet (an email template).

  • Discard draft

    Discard a user-owned Superhuman Mail draft by draft_id so it disappears from the user's Drafts list.

  • Discard reminder

    Discard (cancel) a reminder on a Superhuman Mail thread so it no longer brings the thread back to the top of the inbox.

  • Discard snippet

    Remove a saved Superhuman Mail snippet, identified by the id from list_snippets.

See all 33 Superhuman Mail tools

Control

What Runlayer can see and stop in GitHub Copilot

Some controls apply to every client at the gateway. Others depend on what GitHub Copilot exposes to Runlayer.

  • Gateway policy (available)

    Every Superhuman Mail call from GitHub Copilot passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, GitHub Copilot as the client, the tool, and the policy and scanner decisions.

  • Native enforcement adapter (not available)

    Runlayer has no device-side adapter for GitHub Copilot yet, so control happens at the gateway.

Frequently asked questions

Connect more

Find another combination