Vibe test

Automated browser testing after new vibe-coded changes/features.

Kyoto explores the code changes to see what frontend features were added or changed then runs a series of tests to check if they work.

kyoto vibe test

This command will review all uncommited changes for tests to run. or, let coding agents vibe test themselves

Set up the Kyoto MCP

Options

Scope

Change the scope that Kyoto will evaluate.

# Default
kyoto vibe test                    # all uncommited changes

kyoto vibe test --last             # since last vibe test
kyoto vibe test -1                 # last commit
kyoto vibe test -3                 # last 3 commits
kyoto vibe test --since main       # branch changes
kyoto vibe test --staged           # staged changes only
kyoto vibe test --commit <sha>     # specific commit
kyoto vibe test --changes "file.ts:1-10,other.ts:20-30"  # specific files and lines

Modes

Run browser in headless mode

kyoto vibe test --headless

Enable interactive mode to choose which tests to run

kyoto vibe test --interactive

Watch for file changes and automatically run tests

kyoto vibe test --watch

Instructions

kyoto vibe test --instructions "test login flow"  # custom testing instructions
kyoto vibe test --timeout 5        # timeout in minutes (default: 1)

Vibing

Tools

Integrations

Options

Scope

Modes

Instructions

​Options

​Scope

​Modes

​Instructions

Options

Scope

Modes

Instructions