Usage Guidelines

Describe the intended files, expected change, and any prohibited operations before starting a session. Narrow scopes create clearer predictions and make scope-drift signals meaningful.

A blocked critical action is deterministic enforcement. Scope-explosion and burn-forecast signals are monitoring signals that should prompt review or reassessment. Do not treat every warning as proof of malicious behavior.

Run the agent through the Foresight CLI so the Sentry proxy can observe its supported Python child process. Review the terminal dashboard or web dashboard while the session is active.

• - Use explicit allowed paths and hosts.
• - Do not disable forbidden-pattern checks to make a demo pass.
• - Stop and inspect a session before overriding a critical block.

The packaged interception path currently targets Python child processes. Other agent runtimes remain a roadmap item, so do not assume uninstrumented commands are being monitored.