Kobiton for GitHub Copilot CLI

Kobiton for GitHub Copilot CLI connects the Copilot CLI to the Kobiton mobile testing platform. You can manage devices, upload apps, run automation tests, and review results using natural language commands without switching between the terminal, the Kobiton portal, and local test scripts.

Join our Discord Kobiton Cloud

The instructions in this document apply to Cloud only. Standalone and Cloud with custom domain instructions are coming soon.

Get started

Open a workspace folder

Before using the Copilot CLI, open a command-line tool on your machine:

  • macOS: Terminal

  • Windows: PowerShell or Command Prompt

Create a folder:

mkdir kobiton-project

You can create this folder anywhere, for example in your Documents directory.

Next, start the Copilot CLI from that location:

cd kobiton-project
copilot

The Copilot CLI uses this folder as its workspace.

Install the plugin

Once the Copilot CLI starts in your Terminal, run the following commands one at a time in that window:

/plugin marketplace add kobiton/automate

then

/plugin install automate@kobiton

Both steps are required and must be run separately.

Authentication

Kobiton MCP supports:

  • OAuth authentication (recommended)

  • API key authentication

OAuth authentication is the default authentication method for the Copilot CLI.

OAuth authentication (recommended)

Trigger the OAuth flow from inside the session:

/mcp auth kobiton

A browser window opens for authentication.

Sign in using:

  • Kobiton credentials

  • Google

  • GitHub

The Copilot CLI stores OAuth tokens automatically for future sessions. Use /mcp (or /mcp show) at any time to inspect server status.

API key authentication

Use API key authentication for:

  • CI/CD pipelines

  • headless environments

  • systems without browser access

Generate an API key in Kobiton Portal > Settings > API Keys. Then set:

export KOBITON_AUTH="Basic $(echo -n 'username:api-key' | base64)"

Update .mcp.json (or ~/.copilot/mcp-config.json) to include the Authorization header.

OAuth and API key authentication cannot be used together in the same .mcp.json configuration.

OAuth uses browser-based authentication and token management, while API key authentication uses explicit authorization headers. Configure only one authentication method at a time.

Bootstrap credentials and CLI wrapper

After installation and OAuth login, run setup once to fetch your credentials and install the CLI wrapper used by the run-interactive-test skill:

/automate:setup

The Copilot CLI has no SessionStart hook, so the wrapper is not re-installed automatically. Re-run /automate:setup if ~/.kobiton/bin/kobiton ever goes missing.

To verify everything is wired correctly:

/automate:doctor

Run a command

After authentication, enter commands in the Copilot CLI using natural language.

Show available Android devices
Show results for session 12345
Upload app.apk and run tests/smoke_test.js

If tool calls are blocked, allow Kobiton tools explicitly:

copilot --allow-tool='kobiton'

Or allow specific tools:

copilot --allow-tool='kobiton(listDevices)' --allow-tool='kobiton(getSession)'

Common workflows

The Copilot CLI plugin supports common mobile testing workflows, including device management, app uploads, test execution, and session review.

Device management

  • View available devices

  • Check device status

  • Reserve and release devices

App management

  • Upload Android and iOS apps

  • View uploaded apps

  • Get app details

Test execution

The run-automation-suite workflow guides you through the full test lifecycle:

  • Upload or select an app

  • Select a device

  • Parse capabilities from your script

  • Run the test

  • Return results and artifacts

Supported languages:

Language Extension Command

Node.js

.js

node <script> <udid>

Python

.py

python <script> <udid>

.NET

.cs / .csproj

dotnet test

Java

.java

mvn test or java -cp …​

Session management

  • View active and past sessions

  • Get logs, screenshots, and videos

  • Stop running sessions

Example prompts

Device management

Show available Android devices
Check if Galaxy S23 is available
Reserve Pixel 6 for 60 minutes

App management

Show uploaded Android apps
Upload resources/apps/GS.apk

Test execution

Run tests/smoke_test.js on a Pixel device

Session management

Show running sessions
Get details for session 12345
Download logs from last failed session

For a complete reference of available Kobiton tools, skills, and commands, see the Kobiton AI plugin and tools reference.

Troubleshooting

MCP tools not available after plugin install

Verify the plugin is installed and the MCP server is configured:

exit
copilot plugin list
copilot
/mcp show

If the kobiton MCP server does not appear, add it manually by running /mcp add and entering the following when prompted:

Alternatively, edit ~/.copilot/mcp-config.json directly:

{
  "mcpServers": {
    "kobiton": {
      "type": "http",
      "url": "https://api.kobiton.com/mcp"
    }
  }
}

MCP server does not appear in /mcp after install

The Copilot CLI caches plugin state when the session starts. After installing or updating the plugin, exit and relaunch:

exit
copilot

Tool calls are blocked

The Copilot CLI requires explicit tool permissions. Allow Kobiton tools as shown in Run a command above.

Device not found

The device may be unavailable. Filter for available devices.

Upload timeout

Large files or slow connections can cause timeouts. Retry the upload.

Session stuck

Terminate the session and run it again.

Authentication not recognized

Reload your shell and restart the Copilot CLI.

Additional resources