WispOS

Shared team agents: how they work

A shared team agent is a read-only agent a team publishes as a git repo. Install one in WispOS and Wisper asks it whenever a question belongs to it, pulling the latest first and naming the team that answered.

Updated

A shared team agent lets a team answer questions about its own work in other people’s WispOS. The team publishes it as a git repository: some instructions and the files it answers from. You install it, and from then on, when you ask Wisper something that belongs to it, she asks that agent and relays the answer, naming the team and the files it came from.

Think of a game’s modding community, a school’s policy team, or an open-source project’s maintainers: they keep the answers current in one repo, and everyone who installed the agent gets the current answer.

Installing one

  1. Get the agent’s git address from the team that publishes it. A GitHub page address works as copied (github.com/<owner>/<repo>), as do https://, ssh://, user@host:path, and a folder on your computer.
  2. In WispOS, open Settings → Phone & sharing → Shared team agents.
  3. Paste the address and press Add.

Private repositories work too: WispOS clones with the git credentials already on your computer, and with the GitHub CLI’s sign-in if you have gh set up.

Remove deletes only WispOS’s own copy.

Asking it

You don’t have to do anything special. When your message is about what the agent knows, Wisper asks it. To be sure, address it by name:

  • ask education what's the late work policy?
  • @education can students use phones in class?
  • “what does the education team agent say about absences?”

Each agent lists the topics it knows on its card. A message that mentions enough of them goes to that agent; if two agents tie, neither is asked and Wisper tells you which ones you have, so you can name one.

What happens on each question

  1. WispOS pulls the latest from the agent’s repo, so you always get the team’s current answer. If the pull fails (you’re offline, say), it answers from the copy it has and says it wasn’t refreshed.
  2. It checks you’re allowed to ask. Each agent lists who may ask it. If you’re not on the list, nothing runs and Wisper tells you who owns it.
  3. The agent answers, on your computer, reading only its own repo.
  4. Wisper relays it, with the team, the owner, and the files and version it answered from.

The turn’s activity shows each step as it happens: pulling, asking, and which files the answer came from.

Safe by design

A shared agent can only read the files in its own repo. It can’t run commands, browse the web, read anything else on your computer, or use any other tools. Its instructions can shape what it says, never what it does. Wisper treats what it says as information to pass on, not instructions to follow.

Requirements

Shared team agents currently need Wisper’s brain to be Claude Code (see Choosing Wisper’s brain), and run on your own AI plan.

Next