Building for WispOS
Shared team agents: the format, how they run, and how to make good ones.
- 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.
- Make an agent from your documents Give Wisper a folder of PDFs, Word files, slides or spreadsheets and ask for an agent. She builds the app, WispOS packs and checks it as a .wapp, and you install it or share it so other people can ask it questions.
- Build a shared team agent The repo layout and card.json reference for a WispOS shared team agent: name, team, owner, the topics that route questions to it, who may ask it, and which model it runs on.
- Share your own projects and agents Turn one of your WispOS projects or agents into a shared team agent in a few clicks: tick it, check what goes in, and send people the link. Sharing is self-hosted, and anything that looks like a secret stays out.
- Best practices for shared team agents How to build a WispOS shared team agent people trust: scope it tightly, write knowledge it can quote, pick topics that route well, cite sources, and keep it current.