Skip to content

reference

CLI Command Reference

Find command groups, scope flags, local file inputs, exit codes and recovery rules.

CLI Command Reference

Definition

Use teammately <command> --help for the flags accepted by that command. The tables below separate reads from local-file operations and submissions.

Account and agent setup

CommandEffect
login, status, switch, logoutAuthenticate and select profiles
configure agent-toolkitConfigure supported agents, skill and local MCP
mcpStart read-only product MCP over stdio
updateUpdate an installer-managed release; source builds use their build workflow
--version, --helpInspect the selected binary

Read commands

CommandKey input
eval version-context--kind summary, cases, policies or rubrics
eval manifestSelected immutable Version
eval context, eval results, eval instructions--run child Trial ID
eval managed-profileCurrent managed execution policy
run get, run wait--run child Trial ID
run compare--run baseline and --target candidate; --cases for paged changes

Context/results support --limit, --offset, --result, --case, --policy and --case-rubric-pair. Pages default to 20 observations, maximum 100. Read output defaults to JSON; --format human labels the returned data. Diagnostics use stderr.

Local files and writes

CommandMain flags
eval prepare--out new directory
eval validate-results--manifest, --results, optional --allow-partial
eval submit-resultsSame files, --name, --receipt, optional --group/--allow-partial
eval complete--group, --run, optional --allow-partial/--retry
harness validate--source directory
harness submit--source, --name, --receipt
harness prepare-runtime--harness, --harness-version, --receipt
eval runSaved Harness IDs, --profile-revision, --receipt, optional --compute-profile

The --profile-revision flag carries the exact server-issued concurrency token from eval managed-profile. Do not choose a value or treat it as a customer-managed configuration lifecycle.

Fields, states, or lifecycle rules

Global scope uses the authentication guide's flags/environment. Request timeout defaults to two minutes and can be set with --timeout through ten minutes. A timeout stops waiting, not an admitted job.

Exit codeMeaning
0Command succeeded; inspect resource state for operational failure
1Request, validation or file failure
2Invalid command/configuration
3Authorization failure
4Timeout, cancellation or exhausted transient reads

Source submission, runtime preparation, managed admission and external-output submission use local recovery receipts. After interruption, reuse original inputs and that stage's receipt. Changed inputs require a new logical operation and receipt. eval complete takes no local receipt flag; it uses the server's recorded completion and explicit failed-admission retry contract.

Found something unclear?

Report outdated, unsupported, or confusing docs so we can fix the source page.

Report a docs issue

Continue learning

Related docs