Level 7Lesson 60⏱️ 40 min

Building Block 4 - Connectors

A loop that can only see your files is a tiny loop. Connectors let it read your issue tracker, open pull requests, and ping your team

The Problem: A Loop in a Box

So far, your loop can read and write files on your computer. Useful - but limited. The real work of software lives in other places too: the issue tracker where bugs are logged, the database with live data, the chat channel where your team talks, the error monitor that screams when production breaks.

A loop trapped with only your files is like an employee who can read documents but can't use email, can't open a ticket, and can't tell anyone what they did. Connectors are how the loop reaches out and touches those real tools.

Connectors Run on MCP

Connectors are built on something you met back in Level 1: the Model Context Protocol (MCP). You don't need the deep technical details here - just the idea. MCP is a standard plug shape. Because every tool speaks the same "plug shape," a connector you set up in one AI tool usually works in another with little change.

Analogy: MCP is like USB. Before USB, every device had its own weird cable. After USB, one shape fits everything. MCP is the USB port that lets your loop plug into GitHub, Slack, your database, and more - all the same way.

What Connectors Unlock

This is the difference between an agent that describes a fix and a loop that actually does the whole job end to end:

WITHOUT connectors:
  Agent: "Here is the fix. You should open a PR, update the
          ticket, and let the team know."  (you do the rest)

WITH connectors:
  Loop: opens the pull request itself
      → links the Linear/Jira ticket and moves it to "In Review"
      → waits for CI to go green
      → posts "fixed the auth bug, PR #482" in Slack
      → leaves the hard cases in your triage inbox

The connectors are the reason the loop can act inside your actual workflow instead of just telling you what it would do if it could.

High-Value Connectors to Set Up First

GitHub / GitLab

Read repositories, create branches, open pull requests, and react to events like "a PR was opened." The backbone of most coding loops.

Linear / Jira

Update ticket status automatically and link pull requests back to the work item, so the tracker stays honest without anyone typing.

Slack / Discord

Post daily summaries and - importantly - alert a human when the loop hits something it shouldn't handle alone.

Sentry / error trackers

Watch for spikes in live errors and draft hotfixes for the most frequent ones, before a human even notices.

A Quiet Warning (We'll Return to It)

Connectors are also where a loop gains power in the real world - which means real consequences. A connector with write access can change tickets, push code, and message people. That's wonderful when it works and a problem when it doesn't.

Hold this thought: the more a loop can touch, the more carefully you must control what it can touch and who approves the risky actions. Lesson 64 ("When Loops Go Wrong") covers the security side in full. For now: give connectors the least access they need, not the most.

Hands-On: Map Your Loop's Reach

Hands-on (15 min): For your candidate loop, draw its "reach." List every outside tool it would need to touch to finish the job without you, and next to each, write whether it needs read or write access. Example for a CI-triage loop: GitHub (read failures + write a draft PR), Linear (write ticket status), Slack (write a summary). Then circle anything with write access - those are the powerful, risky connectors you'll want a human gate in front of. You're now thinking about blast radius, which is exactly the mindset of a good loop designer.
Lesson 60 Quick Reference
Connector

Lets the loop reach beyond your files into real tools: trackers, databases, chat, error monitors

MCP

The "USB port" standard connectors run on - set up once, works across AI tools

Describe vs do

Connectors turn "here is the fix" into a loop that actually opens the PR and updates the ticket

First connectors

GitHub/GitLab, Linear/Jira, Slack/Discord, Sentry - the common coding-loop stack

Least access

Give a connector the minimum permission it needs; write access is power and risk

Blast radius

How much real-world damage a loop could do - track which connectors can write/change things

← Skills - Project Knowledge
Unlocks in ~10 min of reading