The agent ecosystem course
  • 0Before you start
  • 1Claude Code
  • 2The mental model
  • 3Map your ecosystem
  • 4The brief
  • 5The connectors
  • 6The runbooks
  • 7Working hours
  • 8The ecosystem
  • 9The backup
  • 10Sharing skills
  • 11Getting found

The stages

  • 0Before you start
  • 1Claude Code
  • 2The mental model
  • 3Map your ecosystem
  • 4The brief
  • 5The connectors
    • 5.01What a connector is
    • 5.02Where your information goes
    • 5.03Connecting the calendar, and more
    • 5.04Ask first
    • 5.05Telling the brief what it can reach
    • 5.06The first job, catch up your inbox
    • 5.07Ready when, what goes wrong, and homework
    • 5.08[BONUS]Have it read everything and learn you
    • 5.09[BONUS]Adding a connector that is not on the list
    • 5.10[BONUS]If you have more than one inbox
    • 5.11[BONUS]Drafts only, so it never sends an email as you
  • 6The runbooks
  • 7Working hours
  • 8The ecosystem
  • 9The backup
  • 10Sharing skills
  • 11Getting found
BACK TO THE COURSE

Stage five, session two

The connectors

The agent knows who it is, and now it gets its own logins to your calendar, your inbox and your files, so the first document about your work is drawn from what it can see rather than what you pasted.

5.11[BONUS]

Drafts only, so it never sends an email as you

Claude can send, reply to and forward email from your inbox, and out of the box it asks you each time.

The question comes with two answers, Allow once and Always allow, and one click on Always allow means it never asks again, so the next time you say “email him” it sends.

The fix is to block the tools that send and keep the one that writes a draft.

It still writes the whole email and leaves it in your drafts, and you read it and press send yourself.

Gmail

Connected

Tool permissions

  • Search your email
  • Read an email
  • Create a draft
  • Send an email
  • Reply to an email
  • Forward an email

Always allowNeeds approvalBlocked

Step

What to do

  1. 1Open the Gmail connector

    In Claude go to Settings, then Connectors, then Gmail, or from a chat press the plus, then Connectors, then Manage connectors, and choose Gmail.
  2. 2Block all three that send

    Under Tool permissions set every tool that sends, replies or forwards to Blocked, whatever your list calls them, because blocking send alone still lets it reply and forward.
  3. 3Leave drafting on

    The tool that creates a draft stays on Always allow or Needs approval, so it can still write the whole email.

Then put the same rule in the top brief, so it holds for whatever you connect next.

A setting covers one connector and the brief is read in every chat, so the rule written there once covers the inbox you add next month too.

Drafts only, in the brief
Add a rule to the standing rules in the CLAUDE.md at the top of this folder. You never send, reply to or forward an email, through any connector or tool, whatever words I use, so "email him", "reply to her" and "send it" all mean write a draft and tell me it is in my drafts for me to send. Show me the change.

If you use Composio

Composio cannot split them.

Its permissions come in groups, so writing a draft and sending one sit on the same switch, and you either allow both or block both.

So in Claude Code the block goes in the folder’s own settings instead, a rule that refuses any tool that sends while drafting stays allowed.

Block sending in Claude Code
Add a deny rule to .claude/settings.json in this folder so you cannot use any tool that sends, replies to or forwards an email, the Gmail connector's and Composio's both, while every tool that creates a draft stays allowed. Show me the rule, then ask to send me a test email and confirm it was refused.

Mods, the block I run

A mod goes one step further, and it is how mine is set up.

A mod is a small piece of code that changes how Claude Code behaves, and it can look at every action before it runs and refuse it, so mine refuses anything that would send an email and tells Claude to write the draft instead.

It catches a send the settings rule cannot see, such as one tucked inside another tool or a script, because it reads what each action is about to do rather than only its name.

You“Email him”
ClaudeGoes to send it
The modReads it first and stops the send
Sent to your client
Written as a draft
YouRead it and press send

You describe the mod and Claude Code writes it.

Mods work in Claude Code version 2.1.287 or later and in the Code tab of the Claude desktop app, and not in an ordinary chat in the Claude app, where the Gmail setting above is the block.

A mod that refuses to send
Make me a mod for Claude Code that refuses any action that would send, reply to or forward an email, through the Gmail connector, Composio or a command, and tells you to write a draft and tell me it is in my drafts instead. Creating a draft stays allowed. Set it up so it runs in every session, not only this one, then ask to send me a test email and show me it was refused.

A mod runs with your permissions.

It can read and write your files and reach the internet, so only install one from someone you trust, which is why this paste has Claude write yours rather than you copying somebody else’s.

Note: Read every draft before you send it, because the draft is where you catch the wrong name or the wrong tone.

That is the whole of this stage. Next is the runbooks

The agent ecosystem course

Drafts only, so it never sends an email as you

This is part 5.11 of the course. Start it free and it opens straight away, with no password.

A few quick questions come next. You will also get my Thursday newsletter, and you can unsubscribe from it without losing the course. How your details are kept is in the privacy policy.

Already have access? .