Control TryCase environments from the command line.

Install

The published CLI connects to production by default. Use a one-off runner, or install it globally when you want trycase available in every shell.

Quick Start

Examples use trycase. In a source checkout, run the same commands with bun apps/cli/src/index.ts. For a fresh machine, start with npx trycase login or bunx trycase login.

trycase login
trycase workspace list
trycase github connect
trycase github repos
trycase project create --repo <owner/name>
trycase project list
trycase env create --project <project> --ref main
trycase env wait <env>
trycase computer browser goto <env> http://localhost:3000
trycase command wait <command>
trycase computer status <env> --json
trycase computer browser snapshot <env>
trycase computer browser screenshot <env>
trycase desktop app launch <env> browser http://localhost:3000
trycase desktop screenshot <env>
trycase artifact bundle <env>
trycase env destroy <env>

Runtime Settings

TryCase checks for trycase.yaml in the repo first. If the file exists, those repo settings are authoritative. If it does not exist, saved settings from the dashboard or CLI are used.

trycase project manifest generate \
  --project <project> \
  --runtime npm \
  --install "npm install" \
  --start "npm run dev" \
  --app-url http://localhost:3000 \
  --healthcheck http://localhost:3000 \
  --size standard

version: 1
runtime:
  type: npm
  size: standard
  timeout_minutes: 60
repo:
  provider: github
  owner: example
  name: app
  ref: main
package:
  install: npm install
  start: npm run dev
  app_url: http://localhost:3000
  healthcheck: http://localhost:3000
artifacts:
  video: always
  screenshots: always
  logs: always
  traces: on_failure

Command Reference

LLM Operating Guide

This flow is designed for coding agents that need to verify web apps without direct access to a long-lived browser session.

1. Start by running trycase login. If a browser cannot be opened, run trycase login --no-open and ask the user to approve the printed URL.
2. Run trycase workspace list. If no workspace is selected, run trycase workspace use <workspace> or trycase workspace create --name <name>.
3. Run trycase github connect if GitHub is not connected, then trycase github repos to choose a repo.
4. Create missing projects with trycase project create --repo <owner/name>. Keep workspace, project, patch, command, and environment IDs in your notes.
5. Run trycase project list and pick the project ID.
6. Check runtime settings with trycase project manifest show --project <project>. Repo trycase.yaml takes precedence over saved settings.
7. For unpushed edits, work in the target repo or a temp clone, run trycase patch upload --project <project> --base <ref>, and use the returned patch ID.
8. Create the environment with trycase env create, then run trycase env wait <env> before sending commands.
9. After env exec or browser commands, run trycase command wait <command> to retrieve the result.
10. Run trycase computer status <env> --json to discover capabilities before using terminal, browser, filesystem, or artifact commands.
11. Use terminal open, terminal write, terminal wait-for, and terminal read for long-running commands, REPLs, dev servers, and watch-mode tests.
12. Use fs write to create temporary scripts in the environment and fs artifact to turn generated files into artifacts.
13. Prefer computer browser snapshot before clicks. Use text or selector refs from the snapshot before coordinate clicks.
14. Use desktop app launch, desktop screenshot, desktop mouse, desktop keyboard, and desktop window commands when the task requires a real visible computer instead of headless browser control.
15. Capture evidence with computer browser screenshot, computer browser recording, computer browser console, computer browser network, env logs, and artifact bundle.
16. Always end with trycase env destroy <env> or trycase env destroy --all-active, then confirm STOPPED - NOT BILLABLE.

# Recommended patch workflow
tmpdir=$(mktemp -d)
git clone https://github.com/<owner>/<repo>.git "$tmpdir"
cd "$tmpdir"
git checkout -b trycase-temp-verify
# make or copy changes
trycase github repos --query <owner/repo>
trycase project create --repo <owner/repo>
trycase billing status
trycase patch upload --project <project> --base main
trycase env create --project <project> --ref main --patch <patch>
trycase env wait <env>
trycase computer browser goto <env> http://localhost:3000
trycase command wait <command>
trycase computer browser snapshot <env>
trycase computer browser screenshot <env>
trycase computer browser recording <env>
trycase artifact bundle <env>
trycase env destroy <env>

Safety Checklist

• Do not print saved tokens or paste them into chat.
• Use temp branches or patch upload for test changes. Do not modify a main branch for verification.
• Use env destroy --all-active before stopping an automation-heavy session.
• Use env usage or env status to confirm active and billable state.
• Prefer snapshots and semantic refs for browser control; use coordinates only when necessary.

Troubleshooting