Sanity Builds Bespoke Agent Harness
Sanity built @s, a Slack-based company agent harness that lets employees define agents as Sanity documents with custom instructions, knowledge bases, skills, tools, and access rules. Jev handles routing while Temporal makes runs durable; the hackathon produced 61 agents and expanded the tool catalog from 9 to 98.
The compelling product is the control plane, not another chatbot: Sanity turns agent creation into a governed content-management workflow. Its results suggest better routing, access, and durability matter more than increasingly elaborate prompts.
- –Defining agents as documents lowers the barrier for non-engineers, but shifts risk toward permissions, ownership, validation, and evaluations.
- –Jev’s typed routing makes delegation faster while forcing agent descriptions to be specific and non-overlapping.
- –Knowledge bases work best when their purpose is sharply defined; vague source collections still produce weak retrieval.
- –Temporal keeps agent runs alive across deploys, enabling background and scheduled work without tying execution to a single process.
- –Only 42 of 61 hackathon agents worked fully or partly, showing that access and integration remain bigger bottlenecks than prompting.
DISCOVERED
1h ago
2026-10-22
PUBLISHED
1h ago
2026-10-22
RELEVANCE
AUTHOR
typesafeai