fast-mode

You can reduce task execution latency by enabling fast-mode, which bypasses automatic skill loading and directly executes only the tasks specified in a local allow-list. This ensures minimal overhead and deterministic behavior for permitted workflows.

You configure a whitelist by setting the CONFIG_DIR environment variable to your configuration path and ensuring the allow-list JSON file lists the permitted skills. The system resolves the allow-list path depending on whether it ends with .json.

Exact-name whitelisting is a mechanism that enforces task execution exclusively for skills whose names precisely match entries in the configured allow-list. It skips all other skills by default to guarantee low-latency runs.

No, the fast-mode allow-list resolution specifically checks if the configured path ends with .json. You must provide a JSON formatted file to ensure the environment-configured allow-list is correctly read and enforced for whitelisting.

Fast-mode bypasses all skills by default to minimize overhead and achieve minimal latency during task execution. It selectively activates only the whitelisted skills, ensuring deterministic behavior without the performance penalty of loading unused skills.

You should avoid using fast-mode when your workflow requires dynamic skill loading or relies on skills not included in the exact-name allow-list, as the system skips all non-whitelisted skills to ensure low-latency execution.