What leaves your computer

The Scopebond hook runs on a computer next to a coding agent such as Claude Code, Cursor or Codex. It sends data only to the workspace the computer is connected to. A computer that is not connected keeps its records in its own local log. This page lists what is sent, by category; the open-source hook is the code that builds it.

Records of agent actions

For each action the hook decides, it signs one record on the computer. A record carries:

• The kind of action: a command, a file read or write, a push, a fetch, an MCP tool call, or an install.
• What it acted on: file paths, with your home folder written as ~; the branch and remote; the host; the MCP server and tool; package names and versions.
• The command: its first 64 characters after masking on the computer, and a keyed digest of the whole masked command. Values the masking finds, such as passwords, tokens and keys, are written ***.
• The decision: the result, the rule that matched, the rule set's version and digest, the time, key ids and signatures.
• Where it happened, once the workspace reads it: the coding tool and its version, the model id the tool reports, an opaque session id, the repository as host/owner/name, and the branch.
• A component value: when a signed Scopebond component is installed, a record can also carry an opaque value of at most 4 KiB and a pattern id that component produced.

Summaries of routine actions

With the default evidence detail, routine actions are sent as one signed summary per five-minute window: counts by action kind, result and program, a keyed digest of the working folder, and how often an identical action repeated. Routine means allowed, and not a push, a fetch, an MCP call, or a write outside the project or to its CI and agent settings. Every other action is sent as its own record, straight away.

Install checks

When your workspace offers Safe Install, the hook asks it about each install before the install runs. The question carries the install's route, ecosystem, package name and version, and the source host and address (scheme, host and path).

Connecting the computer

• The computer's name, when it signs in, so the person approving it can tell which computer it is. Set SCOPEBOND_HOSTNAME_MODE to hash to send a short hash of the name instead, or to off to send no name.
• A machine id: a hash of the operating system's machine id together with the workspace's id, so each workspace sees a different value. The original id stays on the computer.
• The rules check, which fetches the current rules and protection packs: the hook's version and capabilities, the machine id, how many records are waiting to be delivered and the time of the oldest, the last delivery error, and how many notifications and questions Scopebond showed that day (counts only).

Session and health signals

These are sent when your workspace turns them on for the computer: session start and stop, a heartbeat every 60 seconds while a session is active, the age and size of the delivery queue, and one signal per evaluated action, linked to its record. In these signals, paths, commands, hosts and session ids are reduced to keyed opaque ids or fixed categories.

From the Scopebond Agent

The Scopebond Agent, which runs the tray and Scopebond for Windows, also sends:

• The reason a person types when they unblock an action, sent once. The record carries only its digest.
• "This shouldn't be blocked" marks: the record, its rule and the action's key.
• Allowances a person makes and requests they send to an admin, signed by the computer.
• The daily self-check: whether each part of the computer's setup works.
• A request for the client versions your workspace recommends.

What is not sent

• File contents. A rule pack can record a single value it reads from a configuration file, such as an environment name, or a keyed digest of a file.
• A command's text past its first 64 characters.
• Values the masking finds, such as passwords, tokens and keys.
• Prompts, conversations and the agent's answers.
• Keystrokes, screenshots and screen time.
• The computer's private signing keys and its original machine id.

See the next delivery yourself

One command shows exactly what the computer will send next. It runs the hook's own uploader against a copy of the delivery queue and prints the requests it builds, without sending or changing anything.

It is part of hook 0.31.2 and later. A component value is shown as its size. When nothing is waiting, it shows the fields one record carries.

Where it goes

Everything above goes to your workspace, in the region chosen when the workspace was created. Data regions lists what is stored where, and Using Scopebond with your employees covers who in your organization sees it and how long it is kept. The services that process it are on the subprocessor list.