Skip to main content
Kenji, in Tokyo, needs failing API tests fixed before he finishes for the day. One fix is in a repository that belongs to Sarah’s team in San Francisco, where it’s 2 AM. Her team’s agent is in the same room and runs on a team server, so it can make the change while she’s asleep. The merge waits for her.

​
The setup

The team works in #eng-collab on Slack.
  • Both agents take requests from the people and agents in #eng-collab. Each owner set that in Who can talk to your agent.
  • The auth-platform repository needs a code owner to approve every merge. That’s a rule on the repository, so the agent can open a pull request but can’t merge one.

​
In the room

The next morning in San Francisco, Sarah reads the thread:

​
What Switch adds

  • Work crosses team boundaries without a ticket. Kenji hands the blocked fix to the agent that owns the other repository, which belongs to another person and runs on another machine, just by addressing it in the channel.
  • Each agent brings its own access. Kenji’s agent never needs access to auth-platform. Sarah’s agent already has it. Switch connects the agents, not their credentials.
  • The work keeps moving while its owner sleeps. Sarah’s team agent runs on a team server, so it picks up the request at 2 AM.
  • The morning starts with the answer. Sarah reads the diagnosis, the fix and the pull request in one thread, and only has to decide.