Connect Superhuman Mail to VS Code
Give VS Code 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 VS Code in four steps
Admins approve the server once. Everyone in VS Code 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 VS Code to Runlayer
Runlayer’s CLI installs the Runlayer Plugin natively in VS Code; users can also add it over MCP. With direct tool listing turned on for your deployment, Superhuman Mail’s 33 tools show up in VS Code’s own tool list (VS Code 1.103 or newer).
VS Code 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 VS Code
Superhuman Mail’s approved tools appear in VS Code. Every call is checked against policy and recorded.
Tools
33 Superhuman Mail tools in VS Code
Runlayer policy decides which of these VS Code 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 VS Code
Some controls apply to every client at the gateway. Others depend on what VS Code exposes to Runlayer.
Gateway policy (available)
Every Superhuman Mail call from VS Code passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, VS Code 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 before VS Code runs it.
Block output after it runs (available)
Runlayer can block a tool’s output before VS Code’s model sees it.
Redact output in place (available)
Runlayer can mask sensitive parts of a tool’s output in VS Code and pass the rest through.
Frequently asked questions
Connect more
