mutagent usage, feedback

Both commands need you to be signed in. See Installation.

mutagent usage

Count the workspace’s LLM providers and the workspaces you can see.

mutagent usage --json

{
  "success": true,
  "resources": { "providers": 2, "workspaces": 3 },
  "_links": { "providers": "https://app.mutagent.io/…", "dashboard": "https://app.mutagent.io" }
}

It exits 0 on success and 3 when you are not signed in.

mutagent feedback send

Send feedback to the Mutagent team. The message can be up to 10,000 characters.

mutagent feedback send "The install step hung on Codex" --category cli --title "Install hang on Codex" --json

Flag	What it does
`--title <text>`	A short summary.
`--category <category>`	`cli` (the default), `helix`, or `stage:` followed by `spec`, `build`, `evaluate`, `diagnose`, or `optimize`.
`--session <id>`	Link the feedback to a session ID.
`--attach-transcript [path]`	Attach a coding-agent session transcript. Without a path, the newest one is found automatically.

With --json, a sent report returns "success": true and its id, and the command exits 0. Every report includes the CLI version, platform, OS and Node version.

--attach-transcript uploads the last 200 KB of a coding-agent session: source code, absolute paths, branch and repository names, internal hostnames, and the context of your prompts. Credentials are scanned for and removed before upload, but detection is best effort. A coding agent must not pass it unless you ask for it.

CLI

Account

Workspace

Helix

Setup

mutagent usage, feedback

mutagent usage

mutagent feedback send

​mutagent usage

​mutagent feedback send

mutagent usage

mutagent feedback send