Documentation
Put guardrails on your coding agents in minutes, see every action in one place, and prove what happened later.
Start here
How-to guides
Connect an agentPut the same guardrails on every agent your team runs, and optionally see them all in one workspace. Each connector checks actions and keeps receipts on yoSet rules for all your computersDecide, rule by rule, what Scopebond stops before it happens and what it only records, for every agent at once, for one environment, or for one agent. ChanWrite a policyA policy is the list of what your agents may and may not do. You set the limits once, and Scopebond applies them to every checked action before it runs.Invite your teamGive each teammate their own sign-in and the right level of access, so everyone sees the same agents and records. Only an owner or admin can invite. On the
Understand it
Reference
Policy reference (vocabulary v1)Every field a Scopebond policy can use, for writing or reviewing a policy for a gateway, MCP proxy, framework plugin or GitHub check. Coding-agent hook useReceipts and verificationA receipt is the signed record of one decision about one agent action. You can prove it later to an auditor, a customer or your own team, offline, without Receipt schema referencescopebond:receipt evidence contract v1 — A countersigned receipt whose signature covers the complete canonical payload. It attests the gateway's recorded dWorkspace API guideThe HTTP endpoints that connect a hook, a gateway or your own script to your Scopebond workspace. Most teams never call them, because the hook and gateway