Skip to main content
Start with defaults. Configure only the workspace, evaluation policy, or limits your application needs. Reflect reuses the existing PandaProbe client’s endpoint, API key, and project; the host owns model/provider settings.
All Reflect durations are seconds. Sizes are UTF-8 bytes; KiB and MiB mean powers of 1024. TypeScript options use camelCase, while persisted records and reports retain snake_case fields such as execution_id and run_ids.

Evaluation and reflection

There is no default daily evaluation count limit. An explicit positive integer caps attempts across a reused identity workspace, including diagnostic, failed, and uncertain creations. Polling an existing run does not count. Usage is tracked even when uncapped; zero is invalid. At the cap, tasks and accepted guidance remain available, new detection is skipped with a reason, and known runs can still be polled. The counter resets at midnight UTC for new requests; previously skipped executions are not automatically retried. This is a local cost control, not a platform quota or a dollar budget.

Trajectory and validation

See Detection semantics and Validation before changing these values. Scores must be finite and normalized to [0, 1].

Filesystem and output

These limits cover the supplied tool and active files, not the framework’s entire context, other host tools, model billing, or historical audit storage. Restoring an execution preserves its consumed output allowance.

Environment and runtime support

Shared credentials remain PANDAPROBE_API_KEY, PANDAPROBE_PROJECT_NAME, and PANDAPROBE_ENDPOINT. Other Reflect policy settings are constructor options; there is no separate reflection model setting. Use local filesystem semantics for locks and atomic replacement. Keep Python and TypeScript writable workspaces separate. Native binaries must be available for your platform; browser/edge execution and arbitrary distributed filesystem backends are outside the supported runtime model.