@sente-labs/cli

The Sente CLI -- author and manage QA tests from your terminal and Claude Code. Tests run against your staging URL after each deploy.

Install

npm install -g @sente-labs/cli

Requires Node.js 18+.

Quickstart

# 1. Get a token from https://app.sente.run -> Settings -> API Tokens
sente login

# 2. In your repo, create a Sente project and install the Claude Code skill
cd my-app
sente init --staging-url https://staging.my-app.com

# 3. Open Claude Code; it auto-discovers the skill
claude

# 4. Ask CC: "Write a Sente test for the login flow"
#    CC drafts steps, validates them, and creates the task via the CLI.

The skill installs to ~/.claude/skills/sente/SKILL.md. Re-install or update with sente install-skill.

Where do tests run?

Sente runs in a cloud-hosted Chrome browser, so it only operates against publicly-reachable URLs. Staging environments, production, and public preview deploys (Vercel, Netlify) all work. localhost and non-public PR previews do not.

Tests are triggered after each staging deploy via the per-project deploy webhook. Configure it in Project Settings -> Deploy Webhook, then POST to it from CI:

- run: |
    curl -X POST $SENTE_DEPLOY_ENDPOINT \
      -H "X-Sente-Secret: ${{ secrets.SENTE_WEBHOOK_SECRET }}" \
      -d '{"environment":"staging","commitSha":"'"$GITHUB_SHA"'"}'

Common commands

sente whoami                                 # show current user + org
sente project show                           # show project bound to this repo
sente task list --json                       # list tasks
sente task show <id>                         # task details
sente task results <id> --failed-step --json # focused failure payload
sente task create --workflow <id> --name "..." --instruction "..." \
  --steps-from steps.json
sente task update <id> --steps-from steps.json
sente task delete <id>
sente sync                                   # regenerate .sente/tasks.json

Use --json on any command for machine-readable output -- this is what the Claude Code skill consumes.

Auth

Tokens are stored in ~/.sente/credentials (mode 0600). You can override both the token and the gateway URL via env:

export SENTE_API_TOKEN=sk_sente_...
export SENTE_GATEWAY_URL=https://api.sente.run

Useful for CI where interactive sente login isn't an option.

Documentation

• Home: https://sente.run
• Issues: https://github.com/sente-labs/agentic-browser/issues

License

UNLICENSED. Contact [email protected] for licensing terms.