Connect Superhuman Mail to GitHub Copilot CLI
Give GitHub Copilot CLI 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 CLI in four steps
Admins approve the server once. Everyone in GitHub Copilot CLI then gets it through the same governed connection.
- 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
Connect GitHub Copilot CLI to Runlayer
Users add the Runlayer Plugin to GitHub Copilot CLI by following Runlayer’s setup guide. GitHub Copilot CLI reaches Superhuman Mail’s 33 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
GitHub Copilot CLI setup guide - 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
Use Superhuman Mail from GitHub Copilot CLI
Superhuman Mail’s approved tools appear in GitHub Copilot CLI. Every call is checked against policy and recorded.
Tools
33 Superhuman Mail tools in GitHub Copilot CLI
Runlayer policy decides which of these GitHub Copilot CLI 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.
Control
What Runlayer can see and stop in GitHub Copilot CLI
Some controls apply to every client at the gateway. Others depend on what GitHub Copilot CLI exposes to Runlayer.
Gateway policy (available)
Every Superhuman Mail call from GitHub Copilot CLI 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 CLI as the client, the tool, and the policy and scanner decisions.
Client hooks (available)
Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.
Stop a call before it runs (available)
Runlayer can deny a tool call or permission request before GitHub Copilot CLI runs it.
Block output after it runs (available)
Runlayer can block a tool’s output before GitHub Copilot CLI’s model sees it.
Redact output in place (available)
Runlayer can mask sensitive parts of a successful tool’s output in GitHub Copilot CLI and pass the rest through.
In GitHub Copilot CLI
- When a tool fails, Runlayer records the error but cannot replace it.
Frequently asked questions
Connect more
