Let your agent test the app before you do.
TryCase gives your coding agent a disposable Linux desktop to run your app, test it like a user, and send back proof: screenshots, recordings, and logs.
Install TryCase skills in this agent session.
Run:
npx skills add bencsn/trycase-skills --skill trycase-cli --skill trycase-run-linux-app -g
After installation, check whether the TryCase skills are available. Do not ask me to restart this session just for the skills.
If the skills are not available in this session, continue anyway: use web search to find the TryCase docs at https://www.trycase.dev/docs, learn the current CLI workflow from the docs, then use TryCase from the CLI.
Make sure TryCase is installed/up to date, run npx trycase@latest login if login is needed, then use TryCase to test my app and return screenshots, recordings, logs, and any artifacts.Ask your coding agent to install the skills, or fall back to the TryCase docs if skills are unavailable.
What it looks like
One prompt in, proof out.
You:
How it works
Three steps from prompt to proof.
Install the skills
One command teaches Claude, Codex, Cursor, or any coding agent how to use TryCase.
Ask for proof
The agent gets a disposable Linux desktop with terminal and browser control to run your app and test it like a user.
Review what comes back
Screenshots, recordings, logs, and artifacts return with the answer. The environment is destroyed afterwards.
Example prompts
Ask the agent to prove the work, not just finish the code.
Click a prompt to copy it, then drop it into your coding agent once the TryCase skills are installed.
Ship code your agent already tested.
Install the skills once, then ask for proof on every task.