Improvement Without Telemetry

The best automation grows from real friction: a prompt that keeps missing one case, or two commands you always type together. CmdForge can help with both while keeping usage history local and opt-in.

Generate Prompt Variations

cmdforge optimize classify-ticket --count 4

By default, variation generation is deterministic and does not call a paid provider. Choose a provider explicitly when you want model-generated alternatives:

cmdforge optimize classify-ticket --count 4 --provider local-reasoner

Measure Semantic Behavior Explicitly

cmdforge optimize classify-ticket   --behavior-tests tests/classify-ticket.json   --test-provider mock

Behavior cases execute the tool and therefore deserve the same provider, privacy, and side-effect review as any normal run. Structural conformance alone is not semantic correctness.

Opt In to Local Usage Discovery

cmdforge usage status
cmdforge usage enable

# After normal work
cmdforge usage suggestions

CmdForge records local tool-sequence patterns in ~/.cmdforge/usage.json. It does not send that history to the registry or a telemetry service. Suggestions identify frequently repeated pipelines that may deserve a composite tool.

You Own the History

cmdforge usage clear
cmdforge usage disable

Disabling stops collection; clearing removes the local history. The feature is useful precisely because it is modest: it recognizes command patterns, not the content flowing through them.

Promote Repetition Carefully

Not every repeated pair should become a new abstraction. Extract a composite when the sequence has a stable purpose, a useful contract, and a name another person could understand. Leave exploratory pipelines as shell history until their boundary becomes clear.