For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Discord
DocsAPI Reference
DocsAPI Reference
  • Get Started
    • Welcome
    • Introduction
    • Quick Start
  • Run
    • Run Videos
    • Run Mode
    • Viewport Size
    • Preparation Test
    • Pull Request Testing
    • Production Monitoring
    • Group Webhooks
    • Run Troubleshooting
  • Auth
    • Test Credentials
    • API Keys
    • Agent Mail Inboxes
    • HTTP Basic Auth
    • Auth Troubleshooting
  • Mobile
    • Overview
    • App Uploads
    • Expo EAS
    • GitHub Actions
  • Integrations
    • Vercel
    • Coolify
    • Custom Infrastructure
    • Slack
    • Discord
  • Guides
    • Testing Staging Environment
  • CLI
    • Getting Started
    • Local Development
    • Agentic Usage
  • AI
    • LLMs
LogoLogo
Discord
On this page
  • What agents can do
  • Setup
  • Prompt your agent
  • Useful entrypoints
  • Safety
CLI

Agentic Usage

||View as Markdown|
Was this page helpful?
Edit this page
Previous

Local Development

Next

LLMs

Built with

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 designed to be self-discoverable. Agents can start with ta --help and use subcommand help to figure out the exact workflow.

What agents can do

With an API key, an agent can:

  • create and list projects
  • save project memories as durable testing context
  • create dashboard tests
  • run tests locally or remotely
  • wait for remote runs and inspect run history
  • upload iOS Simulator apps for mobile tests

Setup

Install and authenticate once:

$npm install -g testerarmy
$ta auth
$ta status --json

For non-interactive sessions, set:

$export TESTERARMY_API_KEY="YOUR_KEY"

Prompt your agent

Use the TesterArmy CLI (`ta`) to set up and run QA for this project.
Start with `ta --help`, use subcommand help as needed, prefer JSON output,
and report the commands you ran plus run IDs and results.

Useful entrypoints

$ta --help
$ta projects --help
$ta memories --help
$ta tests --help
$ta tests run --help
$ta runs --help

Safety

  • use scoped API keys when possible
  • prefer --json for agent-readable output
  • avoid putting secrets in shell history
  • ask before deleting projects, memories, or tests