> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tester.army/llms.txt
> Use this file to discover all available pages before exploring further.

# Agentic Usage

> Give coding agents like Claude Code, Cursor, and Codex access to the TesterArmy CLI to set up projects, save tests, and queue remote QA runs.

Give your coding agent access to the TesterArmy CLI when you want it to set up
and run QA without leaving your development loop. The CLI is a control plane
for the TesterArmy dashboard: agents use it to manage projects, environments,
and saved tests, and to queue remote runs that execute in TesterArmy cloud.

The CLI is designed to be self-discoverable. Agents should start with
`ta agent init` and `ta docs` instead of scraping long help output. `ta docs`
prints task-oriented command routing, and `--json` returns structured output for
automation.

## What agents can do

With an API key, an agent can:

* create and list projects
* create and delete static project environments (`--name`/`--url` flags)
* save project memories as durable testing context
* create dashboard tests
* create test groups and add or remove tests
* list and create project credentials, and list project files
* queue remote dashboard runs (default) and target saved environments with `--env`
* validate development changes against a saved preview or tunnel environment with `--env`
* wait for, cancel, and inspect remote runs
* upload iOS Simulator apps and Android artifacts for mobile tests
* report TesterArmy bugs, misleading docs, or missing capabilities to the TesterArmy team with `ta feedback`

## Setup

Install and authenticate once:

```bash theme={"theme":"vesper"}
npm install -g testerarmy
ta agent init
ta auth
ta status --json
```

For non-interactive sessions, set:

```bash theme={"theme":"vesper"}
export TESTERARMY_API_KEY="YOUR_KEY"
```

For editor sessions in Cursor, VS Code, Windsurf, Claude Code, Codex, or any
other MCP client, connect the hosted [MCP server](/cli/mcp) as well. It covers
group schedules, issues, and run recordings, which the CLI does not:

```bash theme={"theme":"vesper"}
npx add-mcp --global --name testerarmy https://tester.army/mcp
```

## Prompt your agent

```txt theme={"theme":"vesper"}
Use TesterArmy CLI (`ta`) for QA. Start with `ta agent init`, then discover
workflows with `ta docs --json` or `ta docs <topic>`. Use `--json` for automation;
on failure, follow `error.hint`. Report commands, run IDs, results, and artifacts.
```

## Useful entrypoints

```bash theme={"theme":"vesper"}
ta agent init
ta docs
ta docs --json
ta docs agent
ta docs mcp
ta docs auth
ta docs projects
ta docs memories
ta docs tests
ta docs groups
ta docs runs
ta docs ci
ta docs feedback
```

## Safety

* API keys have full access to their workspace, so keep them in a secret manager
* prefer `--json` for agent-readable output
* use JSON error envelopes to decide the next action instead of parsing text
* avoid putting secrets in shell history
* ask before deleting projects, environments, memories, or tests


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.