quartet-cli

Overview ¶

Command quartet-cli is the umbrella CLI for driving a Quartet backend from a model or a shell. It is organized into command groups:

	quartet-cli workflow <create|list|get|update|delete|validate|run> [flags]
	quartet-cli schedule <create|list|get|update|delete|toggle|run> [flags]
	quartet-cli workspace <list> [flags]
	quartet-cli job <list|get|stop> [flags]
	quartet-cli agent <list> [flags]
	quartet-cli wechat <send|accounts> [flags]

  - workflow manages graph workflows in the "agent" library.
  - schedule manages cron-scheduled graph-workflow runs.
  - workspace lists workspaces (read-only; IDs feed workflow/schedule flags).
  - job inspects and stops jobs (read-only list/get plus stop).
  - agent lists the installed ACP agents (read-only).
  - wechat send pushes a proactive WeChat message through the backend
    (POST /api/v1/wechat/send), used by scheduled-job prompts and scripts;
    wechat accounts lists the logged-in iLink accounts.

Library boundary for the workflow group (enforced client-side, see workflow.go):

• create always tags the workflow as type=agent.
• update / delete first GET the target and refuse unless its type is agent, so a model can never modify or remove a user-authored ("user") workflow.
• get / list / run work across both libraries (run does not modify the workflow; it creates a job).

Connection:

• Base URL: $QUARTET_BASE_URL (default http://127.0.0.1:8090)
• Auth: use `quartet-cli auth login`; the session is stored per base URL.

Per the repo convention, every error is printed in full — nothing is hidden.