Manage user playbooks and agent playbooks — CRUD, aggregation, approval.
Two related command groups manage the playbook system:
user-playbooks — rules extracted from individual interactions, scoped per request.
agent-playbooks — aggregated, agent-level rules produced by clustering user playbooks. Supports an approval workflow (pending → approved / rejected).
The typical lifecycle: publish interactions → extractors emit user playbooks → agent-playbooks aggregate clusters them into agent playbooks → review and approve.
Add an agent playbook directly, bypassing the aggregation pipeline. Useful for seeding rules without first producing sample user playbooks for the aggregator to cluster.
To update trigger or rationale, use the Python client's update_agent_playbook() / update_user_playbook() methods — each field is updated independently.
Dedicated approval-workflow command. Prefer this over update for status changes — the server has a single-purpose endpoint that writes a smaller change log.
Cluster similar user playbooks into agent playbooks. Without --agent-version, discovers every agent version that has user playbooks and aggregates each one separately. --playbook-name defaults to the first playbook name configured on the server.
Terminal
reflexio agent-playbooks aggregate [OPTIONS]
Prop
Type
Default
Description
--agent-version?
str
all
Agent version to aggregate. Omit to aggregate all versions.
Same shape as agent-playbooks for list / search / add / update / delete / delete-all, but operates on the pre-aggregation user playbook layer and has no approval workflow.