#CLI commands

The Tessl CLI provides commands for managing plugins, workspaces, authentication, repository configuration, and Tessl projects. This page provides a comprehensive reference for all available commands.

#Getting started

#tessl help command

To see all available commands, run:

tessl --help

To get detailed information about a specific command or command group, use the --help flag:

tessl <command> --help
tessl <command-group> <subcommand> --help

#Authentication

#tessl login

Authenticate with Tessl.

Usage

tessl login [--device | --loopback] [--region <us|eu>]

Use --device to sign in with a device code instead of a local browser redirect. Use --loopback to sign in with a local browser redirect. Use only one of these flags.

Organizations using the EU region log in with --region eu. The CLI saves the region with your session, so later commands use it without the flag:

tessl login --region eu

--region works on every command and takes precedence over the TESSL_REGION environment variable, the region field in tessl.json, and the region you last logged in to. It doesn't appear in tessl --help. See Using the EU region for the full setup, including CI and MCP servers.

Alternative

tessl auth login

#tessl logout

Sign out and clear credentials.

Usage

tessl logout

Alternative

tessl auth logout

#tessl whoami

Show current authenticated user.

Usage

tessl whoami

Alternative

tessl auth whoami

#Setup and initialization

#tessl init

Set up your repository and configure your coding agent.

Usage

tessl init [--agent <name>]... [--name <name>]

Flags

• --agent (string, optional, repeatable): Configure MCP for coding agent. Supported values: claude-code, cursor, gemini, antigravity, codex, openhands, openclaw, copilot, copilot-vscode, agents, tessl-agent. Can specify multiple agents. See Custom Agents for information on configuring additional agents.
• --name (string, optional): Project name for new tessl.json (default: current directory name)

Notes

• Configures MCP server settings for AI coding agents
• Creates a tessl.json manifest at the repository root

Examples

# Basic initialization with default settings
tessl init

# Initialize and configure Cursor integration
tessl init --agent cursor

# Initialize with multiple agents
tessl init --agent cursor --agent claude-code

#tessl project

Create, link, or repair the Tessl project for this repository.

A Tessl project gives Tessl a stable place to attach eval runs and other repository-connected data, so your results stay tied to your codebase over time.

Use these commands to create a new project, link this checkout to an existing project, or repair a missing or broken reference in tessl.json. For a workflow guide, see Manage projects from the CLI.

Usage

tessl project <create|delete|link|list|repair>

#tessl project create

Create a new Tessl project for the current repository.

Usage

tessl project create [--nested] [--new] [--workspace <name-or-id>] [<project-name>]

Flags

• --nested (boolean, optional): Required when a parent directory has a tessl.json but the current directory has none. Creates a separate tessl.json and project for the current directory instead of reusing the parent project.
• --new (boolean, optional): Create a new project for a different workspace. Use with --workspace and provide a project name when you intentionally want a separate new project for the same repository.
• --workspace (string, optional): Name or ID of workspace

Arguments

• project-name (string, optional): Name for the new project. If omitted, you'll be prompted.

Notes

• Use this when this repository is not linked to a project yet and you want to create one in Tessl
• This command always creates a new project
• If this repository should use a project that already exists, use tessl project link instead

#tessl project link

Link the current repository to an existing Tessl project.

Usage

tessl project link [--workspace <name-or-id>]

Flags

• --workspace (string, optional): Name or ID of workspace to search

Notes

• Use this when the project already exists in Tessl and you want this repository to use it
• This command only links to an existing project
• If you want to create a brand new project for this repository, use tessl project create instead

#tessl project repair

Inspect or repair the Tessl project link for the current repository.

Usage

tessl project repair [--json] [--relink] [--workspace <name-or-id>] [--project <name>] [--update-source] [--update-name] [--yes]

Flags

• --json (boolean, optional): Output as JSON, for automation or agent workflows
• --relink (boolean, optional): Relink this repository to a different existing project
• --workspace (string, optional): Workspace name or ID for --relink
• --project (string, optional): Project name for --relink target
• --update-source (boolean, optional): Approve this repository as the linked project source
• --update-name (boolean, optional): Rename the linked project to match tessl.json
• --yes / -y (boolean, optional): Confirm and apply requested repair

Notes

• Use this when this repository should already be linked to a project, but the link is missing, broken, outdated, or no longer matches the expected repository or project details

#tessl project list

List all projects in a workspace.

Usage

tessl project list [--workspace <name>] [--json]

Flags

• --workspace (string, optional): Name or ID of workspace.
• --json (boolean, optional): Output as JSON.

Notes

• Shows every project you can access in the selected workspace, with its name, ID, and source.
• The workspace is resolved in this order: --workspace, the TESSL_WORKSPACE environment variable, the project linked in tessl.json, then the workspace prefix in a .tessl-plugin/plugin.json when no tessl.json exists. If none of those apply and you belong to more than one workspace, you are prompted to pick one, or must pass --workspace in a non-interactive shell.

Examples

# List projects in the resolved workspace
tessl project list

# List projects in a specific workspace
tessl project list --workspace engteam

# Output as JSON
tessl project list --json

#tessl project delete

Delete a Tessl project.

Usage

tessl project delete [--org <name-or-id>] [--json] [--yes] <project>

Flags

• --org (string, optional): Name or ID of organization
• --json (boolean, optional): Output the deleted project as JSON. Skips the confirmation prompt, like --yes
• --yes / -y (boolean, optional): Skip confirmation prompt and delete immediately

Arguments

• project (string, required): ID, workspace/project reference, or name of the project. A name alone must match exactly one project in the organization.

Notes

• You need the publisher role or higher in the project's workspace.
• Deleting a project removes it from normal views and frees its name and repository link for reuse. Its run history is kept.
• The organization is resolved in this order: --org, the TESSL_ORG environment variable, your only organization, then an interactive pick. With --json or no terminal, several organizations produce an error that asks for --org instead of a pick. A project ID needs no organization. A value shaped like a UUID is always read as a project ID, so reference a project with such a name as workspace/project.
• When a name matches projects in more than one workspace, the command stops and lists them. Run it again with the workspace/project reference or the ID.

Examples

# Delete a project by its workspace/project reference
tessl project delete engteam/my-project

# Delete without the confirmation prompt
tessl project delete engteam/my-project --yes

#Project dependencies

#tessl install

Install plugins into your repository. plugins are versioned bundles of reusable, agent-agnostic context that make coding agents more effective. They can contain skills, documentation, and rules.

Alias: tessl i

Usage

tessl install [--global] [--skill <value>]... [--yes] [--verbose] [--watch-local] [--accept-warnings] [--strict] [--agent <name>]... <source>...

Arguments

• source (string, required): plugin or GitHub URL to install. Can be:
  • Registry plugin: workspace/plugin[@version] (version optional, defaults to latest)
  • GitHub repository:
    • Full URL: https://github.com/owner/repo
    • Shorthand: github:owner/repo (e.g., github:softaworks/agent-toolkit)
  • File path: file:<path> to install from local directory

Flags

• --global / -g (boolean, optional): Install plugins globally to ~/.tessl/ instead of the current repository. Global plugins are available across all your repositories.
• --skill (string, repeatable, optional): Select specific skills to install from GitHub repositories. Used when a repository contains multiple skills. If omitted, you'll be prompted interactively to select from available skills. Can be specified multiple times to install multiple skills from the same repository.
• --yes (boolean, optional): Skip confirmation prompts and auto-select all skills
• --verbose / -v (boolean, optional): Show detailed warning messages during installation
• --watch-local (boolean, optional): Watch local file-source plugins and reinstall on changes
• --accept-warnings (boolean, optional): Pre-accept install policy warnings (no interactive prompt)
• --strict (boolean, optional): Fail if a version is too new rather than installing an older fallback
• --agent (string, optional, repeatable): Override agents to install for. Supported values: claude-code, cursor, gemini, antigravity, codex, openhands, openclaw, copilot, copilot-vscode, agents, tessl-agent.

Notes

• Plugins are installed to .tessl/plugins/<plugin-name>/ in your repository (or ~/.tessl/plugins/ when using --global)
• Your repository's tessl.json is automatically updated with the plugin reference
• If a plugin is already installed and up-to-date, it will be skipped
• GitHub URL formats: https://github.com/owner/repo, github:owner/repo, git@github.com:owner/repo.git, or with branch/path: https://github.com/owner/repo/tree/main/skills/pdf
• Private repositories: Tessl clones over HTTPS first and falls back to SSH, so a private repository installs if git can authenticate over either one as an account with read access to the repository: an HTTPS credential for that account (for GitHub, run gh auth setup-git), or an SSH key for it. tessl.json stores the https:// form, so teammates can use either credential. The SSH fallback runs OpenSSH without prompting. If your git ssh command runs another program, such as plink or a wrapper script, Tessl reads over HTTPS only.
• File system installation: Use file:<path> to install from a local directory (.tessl-plugin/plugin.json expected in the path)
• Install policy warnings: If a plugin triggers install policy warnings (such as critical or high Snyk security findings), you will be asked for permission before installation continues. You can always choose to proceed — installation is never blocked. Use --accept-warnings to pre-accept these warnings and skip the prompt.

Examples

# Install a specific plugin from registry
tessl install tessl/svelte@5.38.0

# Install multiple plugins from registry
tessl install tessl/svelte tessl/react

# Install from file system (.tessl-plugin/plugin.json is expected in the specified path)
tessl install file:<path to plugin>

# Install from GitHub repository with interactive skill selection
tessl install https://github.com/anthropics/skills

# Install using GitHub shorthand syntax
tessl install github:softaworks/agent-toolkit

# Install from a private GitHub repository using its SSH address
tessl install git@github.com:engteam/private-skills.git

# Install specific skill by name from GitHub repository (when repo has multiple skills)
tessl install https://github.com/anthropics/skills --skill pdf

# Install multiple skills by name from GitHub repository using shorthand
tessl install github:anthropics/skills --skill pdf --skill pptx

# Install from specific branch and path in GitHub repository
tessl install https://github.com/anthropics/skills/tree/main/skills/pdf

# Install from a specific commit (useful when the registry shows security results for that commit)
tessl install engteam/my-skill@abc1234

# Install a plugin globally (available across all repositories)
tessl install --global tessl/svelte

#tessl search

Search for plugins and skills in the Tessl registry by name, PURL, or HTTP URL.

Usage

tessl search [--global] [--type skills|docs|rules] [--org <slug-or-id> | --workspace <org/workspace-or-id>] [--json] [<query>]

Flags

• --global / -g (boolean, optional): Install selected plugins and skills globally to ~/.tessl/ instead of the current project
• --type (string, optional): Filter by content type. Supported values: skills, docs, rules
• --org (string, optional): Limit results to an organization you can access, identified by its slug or ID
• --workspace (string, optional): Limit results to a workspace you can access, identified by org/workspace or its ID
• --json (boolean, optional): Output search results as JSON

--org and --workspace require authentication and cannot be used together.

Arguments

• query (string, optional): Search query (name, PURL, or HTTP URL). If omitted, you'll be prompted interactively.

Examples

# Search for plugins matching "svelte"
tessl search svelte
# Search and install selected results globally
tessl search --global svelte

# Search for skills in an organization
tessl search --type skills --org acme code-review

# Search for skills in a workspace
tessl search --type skills --workspace acme/engteam code-review

# Interactive search
tessl search

#tessl uninstall

Uninstall plugins from your repository.

Usage

tessl uninstall [--global] [--skill <value>]... <workspace/plugin>

Arguments

• workspace/plugin (string, required): Full plugin name in the format workspace/plugin

Flags

• --global / -g (boolean, optional): Uninstall plugins from the global ~/.tessl/ directory instead of the current repository
• --skill (string, repeatable, optional): Remove specific skills instead of the entire plugin (repeatable)

Notes

• Removes the plugin from tessl.json and deletes files from .tessl/plugins/
• Does not require authentication (local operation only)

Examples

# Uninstall a plugin from the current repository
tessl uninstall tessl/svelte

# Uninstall a globally installed plugin
tessl uninstall --global tessl/svelte

#tessl list

List all installed plugins in your repository.

Usage

tessl list [--global] [--json]

Flags

• --global / -g (boolean, optional): List plugins installed in global ~/.tessl/ instead of the current repository
• --json (boolean, optional): Output plugins as JSON instead of human-readable format

Notes

• Lists all plugins installed in your repository based on tessl.json
• Shows plugin names in the format workspace/plugin with their versions
• Does not require authentication (local operation only)

Examples

# List all installed plugins
tessl list

# List plugins in JSON format
tessl list --json

#tessl outdated

Check for available plugin updates.

Usage

tessl outdated [--json]

Flags

• --json (boolean, optional): Output as JSON

Examples

# Check for outdated plugins
tessl outdated

# Output as JSON
tessl outdated --json

#tessl update

Update plugins to newer versions.

Usage

tessl update [--yes] [--force] [--global] [--accept-warnings] [--agent <name>]... [<plugin>]

Flags

• --yes / -y (boolean, optional): Skip prompts and update all compatible plugins
• --force / -f (boolean, optional): Include breaking updates
• --global / -g (boolean, optional): Update plugins installed globally in ~/.tessl/ instead of the current repository
• --accept-warnings (boolean, optional): Pre-accept install policy warnings (no interactive prompt)
• --agent (string, optional, repeatable): Override agents to sync for. Supported values: claude-code, cursor, gemini, antigravity, codex, openhands, openclaw, copilot, copilot-vscode, agents, tessl-agent.

Arguments

• plugin (string, optional): plugin to update in the format workspace/plugin. If omitted, updates all plugins.

Notes

• If a plugin triggers install policy warnings in the new version (such as critical or high Snyk security findings), you will be asked for permission before the update is applied. Use --accept-warnings to pre-accept these warnings and skip the prompt.

Examples

# Update all plugins interactively
tessl update

# Update all plugins without prompts
tessl update --yes

# Update a specific plugin
tessl update engteam/my-plugin

# Include breaking updates
tessl update --force

#Skill management

#tessl skill new

Create a new skill with an interactive wizard or using flags.

Usage

tessl skill new [--name NAME] [--description DESCRIPTION] [--workspace WORKSPACE] [--path PATH] [--install] [--public]

Flags

• --name (string, optional): Skill name
• --description (string, optional): When the skill should be triggered
• --workspace (string, optional): Workspace for the skill (default: local)
• --path (string, optional): Directory path where the skill will be created
• --install (boolean, optional): Automatically install in the current repository after creation
• --public (boolean, optional): Make the skill public (default: private)

Notes

• If flags are omitted, an interactive wizard will guide you through skill creation
• The skill will be created as a directory with the proper Agent Skills specification structure
• Use --install to immediately add the skill to your local agent configuration

Examples

# Create a skill interactively
tessl skill new

# Create a skill with all details specified
tessl skill new --name "commit-conventions" --description "Enforce commit message standards" --workspace myteam --install

#tessl skill import

Create .tessl-plugin/plugin.json from a local SKILL.md file.

Usage

tessl skill import [--workspace WORKSPACE] [--public] [--force] [<path>]

Flags

• --workspace (string, optional): Workspace for the skill (default: local)
• --public (boolean, optional): Make skill public (default: private)
• --force (boolean, optional): Overwrite existing .tessl-plugin/plugin.json without prompting

Arguments

• path (string, optional): Local path to directory containing SKILL.md or to SKILL.md file. Defaults to current directory if omitted.

Notes

• skill import handles one SKILL.md. It writes .tessl-plugin/plugin.json inside that skill folder with "skills": ["."], so the skill folder becomes the plugin root.
• For a repository with several skills, do not run skill import for each skill: that makes one plugin per skill, each with its own evals/. Create one plugin at the repository root instead, with a .tessl-plugin/plugin.json whose skills field points at the skills. See Import an existing skill.

Examples

# Import from current directory
tessl skill import

# Import from a specific path
tessl skill import ./my-skill

# Import and make public
tessl skill import --public --workspace myteam ./my-skill

#tessl skill lint

Validate skill structure and contents.

Usage

tessl skill lint [<source>]

Arguments

• source (string, optional): Path to skill folder or plugin.json. Defaults to current directory if omitted.

Notes

• Checks for required files and proper structure
• Validates frontmatter fields (name, description, etc.)
• Verifies conformance to the Agent Skills specification at agentskills.io/specification
• Returns validation errors and warnings

Examples

# Lint skill in current directory
tessl skill lint

# Lint skill at specific directory path
tessl skill lint ./my-skill

#tessl skill publish

Import (if needed) and publish skill to the registry. This command bundles skills, rules, documentation into a plugin.

Usage

tessl skill publish [--workspace WORKSPACE] [--public] [--force] [--bump patch|minor|major] [--dry-run] [--skip-evals] [--with-scenario-quality-check] [--eval-scenarios <path>] [--resolve-symlinks] [<path>]

Flags

• --workspace (string, optional): Workspace for the skill (used if importing)
• --public (boolean, optional): Make skill public (used if importing)
• --force (boolean, optional): Overwrite existing .tessl-plugin/plugin.json without prompting
• --bump (string, optional): Auto-bump version if it already exists in the registry. Supported values: patch, minor, major
• --dry-run (boolean, optional): Run all pre-publish checks without publishing
• --skip-evals (boolean, optional): Skip publishing eval scenarios from evals/ directory
• --with-scenario-quality-check (boolean, optional): Exclude misleading scenarios from the publish-time eval run
• --eval-scenarios (string, optional): Path to eval scenarios directory (default: <path>/evals)
• --resolve-symlinks (boolean, optional): Resolve symlinked files to their target contents when packing

Arguments

• path (string, optional): Path to the skill directory to publish. Defaults to current directory if omitted.

Notes

• Skills are automatically linted before publishing
• Published skills are versioned based on the version in the skill manifest
• Eval scenarios from the evals/ directory are published by default; use --skip-evals to exclude them
• Automatic evaluation: When published, skills are automatically evaluated and review scores are calculated (see Check a skill's quality using review)

Examples

# Publish skill from current directory
tessl skill publish

# Publish to a specific workspace
tessl skill publish --workspace myteam ./my-skill

# Publish publicly
tessl skill publish --public

#tessl skill unpublish

Prints guidance explaining that skills cannot be unpublished on their own. Performs no registry action. tessl skill archive and tessl skill delete print the same guidance.

Skills are published inside a plugin. To remove a published skill, delete the skill and republish the plugin, unpublish the plugin, or archive the plugin. See tessl plugin unpublish and tessl plugin archive.

#Tessl Review

The tessl review family runs an asynchronous review pipeline server-side. These commands require authentication; run and fix also require a workspace. The pipeline is bundle-aware, and tessl review run polls until it completes. This is the primary path for authenticated users and CI gating.

#tessl review run

Run an asynchronous quality review of a skill — it scores the skill against a reviewer rubric. tessl review run is shorthand for tessl review run quality; to run a security scan instead, use tessl review run security (documented below). Requires authentication and a workspace.

Usage

tessl review run [--json] [--workspace WORKSPACE] [--threshold <percent>] [--label <text>] [--force] [--review-plugin <ref>] [--no-wait] [<path>]

Flags

• --json (boolean, optional): Output as JSON
• --workspace / -w (string, optional): Workspace name or ID. Required when --json is set
• --threshold (number, optional): Exit non-zero if the review score is below this percentage. 0 never fails (skips validation and score gating)
• --label / -l (string, optional): Label to describe this review run
• --force / -f (boolean, optional): Run a fresh review even when cached results exist
• --review-plugin (string, optional): Reviewer plugin — a path to a local plugin directory, or a registry ref workspace/plugin[@version]. Requires a paid plan; on a Free organisation, passing this flag returns an upgrade error
• --wait / --no-wait (boolean, optional): Wait for the review to finish before returning (default: wait; use --no-wait to submit and return the run id immediately, then reconnect with tessl review view). Cannot be combined with --threshold, which needs the completed score

Arguments

• path (string, optional): Path to a skill file or skill directory. Defaults to current directory if omitted.

Notes

• Requires authentication; sign in with tessl login or set the TESSL_TOKEN API key in the environment
• --workspace is required when --json is set, since non-interactive runs cannot prompt for a workspace
• The command polls until the review completes, then prints the results
• --threshold causes a non-zero exit when the score falls below the percentage, making it a CI gate
• Press Ctrl+C to detach — the review continues server-side and can be viewed later with tessl review view
• run has two subcommands: quality (the default, documented here) and security (below). tessl review run quality is the explicit form of the default

Examples

# Review the skill in the current directory
tessl review run --workspace engteam

# Review a skill at a specific path
tessl review run ./my-skill --workspace engteam

# CI gate: fail if the score is below 80%
tessl review run ./my-skill --workspace engteam --json --threshold 80

# Review with a specific reviewer plugin
tessl review run ./my-skill --workspace engteam --review-plugin engteam/my-reviewer

#tessl review run security

Run an asynchronous security scan of a skill, powered by Snyk. Reports findings and the highest severity. Requires authentication and a workspace.

Usage

tessl review run security [--json] [--workspace WORKSPACE] [--label <text>] [--force] [--fail-on <severity>] [--no-wait] [<path>]

Flags

• --json (boolean, optional): Output as JSON
• --workspace / -w (string, optional): Workspace name or ID. Required when --json is set
• --label / -l (string, optional): Label to describe this security review run
• --force / -f (boolean, optional): Run a fresh scan even when cached results exist
• --fail-on (string, optional): Exit non-zero if the highest severity is at or above this level: low, medium, high, critical
• --wait / --no-wait (boolean, optional): Wait for the scan to finish before returning (default: wait; use --no-wait to submit and return the run id immediately, then reconnect with tessl review view). Cannot be combined with --fail-on, which needs the completed findings

Arguments

• path (string, optional): Path to a skill file or skill directory. Defaults to current directory if omitted.

Notes

• Requires authentication; sign in with tessl login or set the TESSL_TOKEN API key in the environment
• The scan runs server-side; the command polls until it completes, then prints the findings and the highest severity
• --fail-on gates the exit code on severity, making it a CI gate — the security equivalent of --threshold on a quality review

Examples

# Security-scan the skill in the current directory
tessl review run security --workspace engteam

# Scan a skill at a specific path
tessl review run security ./my-skill --workspace engteam

# CI gate: fail if any finding is high or critical
tessl review run security ./my-skill --workspace engteam --json --fail-on high

#tessl review view

View results for a review run of either kind. The run ID resolves whether it is a quality or a security review, and the results are rendered accordingly.

Usage

tessl review view [--json] [--last] [--threshold <percent>] [--fail-on <severity>] [--workspace <name>] [<id>]

Flags

• --json (boolean, optional): Output as JSON, in the same shape as tessl review run --json
• --last (boolean, optional): View results for the most recent review run
• --threshold (number, optional): Quality reviews only. Exit non-zero if the review score is below this percentage (0-100)
• --fail-on (string, optional): Security reviews only. Exit non-zero if the highest severity is at or above this level: low, medium, high, critical
• --workspace / -w (string, optional): Workspace name or ID. Only applies with --last; an explicit review run ID already identifies its workspace.

Arguments

• id (string, optional): Review run ID. Provide an ID or use --last.

Notes

• Provide a review run ID or use --last; one is required
• The gate flag follows the run's kind: --threshold gates a quality run, --fail-on gates a security run. Passing the flag for the other kind is a usage error
• --workspace is only accepted with --last; passing it alongside an explicit review run ID fails with a validation error

Examples

# View a specific review run
tessl review view abc123

# View the most recent review run
tessl review view --last

# Re-check a stored run against a threshold
tessl review view abc123 --json --threshold 80

#tessl review list

List recent review runs.

Usage

tessl review list [--json] [--limit <count>] [--workspace WORKSPACE]

Flags

• --json (boolean, optional): Output as JSON
• --limit (number, optional): Maximum number of review runs to display (default: 20)
• --workspace / -w (string, optional): Workspace name or ID

Examples

# List recent review runs
tessl review list

# List the 50 most recent runs
tessl review list --limit 50

# List runs for a specific workspace
tessl review list --workspace engteam

#tessl review retry

Re-run a failed review run.

Usage

tessl review retry [--json] [--workspace <name>] [--last] [<id>]

Flags

• --json (boolean, optional): Output as JSON
• --workspace / -w (string, optional): Workspace name or ID. Only applies with --last; an explicit review run ID already identifies its workspace.
• --last (boolean, optional): Retry the most recent review run

Arguments

• id (string, optional): Review run ID to retry. Provide an ID or use --last.

Notes

• --workspace is only accepted with --last; passing it alongside an explicit review run ID fails with a validation error

Examples

# Retry a specific review run
tessl review retry abc123

# Retry the most recent review run
tessl review retry --last

# Retry the most recent review run in a specific workspace
tessl review retry --last --workspace engteam

#tessl review fix

Improve a skill by running an automated review-and-fix loop server-side. Requires authentication and a workspace.

Usage

tessl review fix [--json] [--workspace WORKSPACE] [--threshold <percent>] [--max-iterations <count>] [--yes] [--review-plugin <ref>] [<path>]

Flags

• --json (boolean, optional): Output as JSON
• --workspace / -w (string, optional): Workspace name or ID
• --threshold (number, optional): Stop once a review scores at or above this percentage (0-100, default 90)
• --max-iterations (number, optional): Maximum improve→review iterations to attempt (1-10, default 3)
• --yes / -y (boolean, optional): Apply the improved skill without confirmation
• --review-plugin (string, optional): Reviewer plugin — a path to a local plugin directory, or a registry ref workspace/plugin[@version]. Requires a paid plan; on a Free organisation, passing this flag returns an upgrade error

Arguments

• path (string, optional): Path to a local skill file or skill directory. Defaults to current directory if omitted.

Notes

• Requires authentication; sign in with tessl login or set the TESSL_TOKEN API key in the environment
• --workspace is required when --json is set, since non-interactive runs cannot prompt for a workspace
• Runs an asynchronous improve→review loop, stopping early once --threshold is met

Examples

# Improve the skill in the current directory
tessl review fix --workspace engteam

# Improve until the score reaches 90%, up to 5 iterations
tessl review fix ./my-skill --workspace engteam --threshold 90 --max-iterations 5

# Apply improvements without a confirmation prompt
tessl review fix ./my-skill --workspace engteam --yes

#Plugin management

#tessl plugin new

Create a new plugin with an interactive wizard.

Usage

tessl plugin new [--name <workspace/plugin-name>] [--summary <description>] [--path <path>] [--rules <rule-name>] [--rule-description <description>] [--workspace <workspace>] [--skill] [--skill-name <name>] [--skill-description <description>] [--install] [--public]

Flags

• --name (string, optional): plugin name in format workspace/plugin-name
• --summary (string, optional): Brief description of the plugin
• --path (string, optional): Directory path where plugin will be created
• --rules (string, optional): Include rule by name
• --rule-description (string, optional): Initial rule instructions to include in generated rule file
• --workspace (string, optional): Workspace for the plugin
• --skill (boolean, optional): Include a skill in the plugin
• --skill-name (string, optional): Skill name (implies --skill)
• --skill-description (string, optional): Skill description (required with --skill or --skill-name)
• --install (boolean, optional): Automatically install in the current repository
• --public (boolean, optional): Make plugin public (default: private)

Notes

• Creates a new plugin directory with a basic .tessl-plugin/plugin.json template
• If run without flags, launches an interactive wizard to guide you through plugin creation
• For non-interactive use, include at least one component with --skill, --skill-name, or --rules
• Use --skill or --skill-name to create a plugin with a skill component

Examples

# Interactive wizard mode
tessl plugin new

# Create a plugin with specific options
tessl plugin new --name myworkspace/my-skill --summary "My skill description" --path ./my-skill-plugin

# Create a plugin with a skill
tessl plugin new --name myworkspace/my-skill --skill --skill-name "my-skill" --skill-description "Description of my skill"

# Create and automatically install
tessl plugin new --name myworkspace/my-skill --install

#tessl plugin lint

Validate plugin structure and contents

Usage

tessl plugin lint [<source>]

Arguments

• source (string, optional): Path to the plugin directory to lint. Defaults to current directory if omitted.

#tessl plugin migrate

Migrate tile.json to .tessl-plugin/plugin.json.

Usage

tessl plugin migrate [--force] [<path>]

Flags

• --force (boolean, optional): Overwrite existing .tessl-plugin/plugin.json

Arguments

• path (string, optional): Path to plugin directory. Defaults to current directory if omitted.

#tessl plugin pack

Package a plugin into a .tgz file.

Usage

tessl plugin pack [--output path] [<source>]

Flags

• --output (string, optional): Output path for .tgz file. If omitted, uses the plugin name and version to create a file in your current directory.

Arguments

• source (string, optional): Path to plugin folder. Defaults to current directory if omitted.

#tessl plugin info

Show plugin details from the registry.

Usage

tessl plugin info [<name-or-path>]

Arguments

• name-or-path (string, optional): plugin name (workspace/plugin[@version]) or path to plugin directory. Defaults to current directory if omitted.

Examples

# Show info for plugin in current directory
tessl plugin info

# Show info for a specific plugin
tessl plugin info engteam/my-plugin

# Show info for a specific version
tessl plugin info engteam/my-plugin@1.0.0

#tessl plugin publish

Publish plugins to the Tessl registry. This command bundles skills, rules, documentation into a plugin.

Usage

tessl plugin publish [--dry-run] [--bump patch|minor|major] [--skip-evals] [--with-scenario-quality-check] [--workspace <workspace>] [--version <version>] [--verbose] [<path>]

Flags

• --dry-run (boolean, optional): Run all pre-publish checks without publishing
• --bump (string, optional): Auto-bump version if it already exists in the registry. Supported values: patch, minor, major
• --skip-evals (boolean, optional): Skip publishing eval scenarios from evals/ directory
• --with-scenario-quality-check (boolean, optional): Have the backend's LLM judge filter out misleading scenarios (low feasibility, rubric leakage, low value) from the publish-time eval run. Equivalent to tessl eval run --quality-check for the eval that runs as part of publishing.
• --workspace (string, optional): Workspace to publish under when the plugin manifest name is flat (no workspace/ prefix)
• --version (string, optional): Version to publish when the plugin manifest omits one
• --verbose / -v (boolean, optional): Print every archived file with the reason it was included

Arguments

• path (string, optional): Path to the plugin directory to publish. Defaults to current directory if omitted.

Examples

# Publish a plugin from current directory
tessl plugin publish

# Publish a plugin from a specific directory
tessl plugin publish path/to/my/plugin

#tessl plugin unpublish

Unpublish a plugin version from the registry.

Usage

tessl plugin unpublish --plugin <workspace/plugin@version>

Flags

• --plugin (string, required): plugin version to unpublish in the format workspace/plugin@version.

Notes

• Unpublishing permanently deletes the version.
• A version can't be unpublished when all of these are true: the plugin is public, the version was published more than 48 hours ago, and the plugin has 500 or more downloads. Archive the plugin instead, or contact support@tessl.io.
• Requires the publisher role on the plugin's workspace.

Examples

# Unpublish a specific plugin version
tessl plugin unpublish --plugin myworkspace/myplugin@1.0.0

#tessl plugin archive

Archive plugins in the registry.

Usage

tessl plugin archive [--plugin <workspace/plugin[@version]>] --reason <reason>

Flags

• --plugin (string, optional): plugin to archive in the format workspace/plugin (archives all versions) or workspace/plugin@version (archives a single version)
• --reason (string, required): Reason for archiving the plugin

Notes

• Prevents new installations while preserving existing installations

Examples

# Archive a specific plugin version
tessl plugin archive --plugin engteam/myplugin@1.0.0 --reason "Deprecated in favor of v2"

# Archive all versions of a plugin
tessl plugin archive --plugin engteam/myplugin --reason "No longer maintained"

#Organization management

#tessl org list

List all organizations that you are a member of.

Usage

tessl org list

#tessl org usage

Show your Tessl credit usage.

Usage

tessl org usage [--org <nameOrId>] [--json]

Flags

• --org (string, optional): Organization name or ID. You are prompted when you belong to several.
• --json (boolean, optional): Output as JSON. The payload contains plan and credits fields.

Examples

# Show credit usage
tessl org usage

# Show usage for a specific organization
tessl org usage --org my-org

# Output as JSON
tessl org usage --json

#Workspace management

Workspaces enable you to create private collections of plugins that are restricted to yourself or your organization. You can control member access and permissions. To learn more, see Distributing via registry.

#tessl workspace create

Create a new workspace.

Usage

tessl workspace create [--org <nameOrId>] [<name>]

Flags

• --org (string, optional): Organization name or ID to own the workspace. When omitted and you belong to several organizations, interactive terminals prompt you to pick one; noninteractive callers must pass --org <nameOrId>.

Arguments

• name (string, optional): Name for the workspace. The name must be lowercase. If omitted, you'll be prompted.

Examples

# Create a workspace
tessl workspace create myworkspace

# Interactive creation
tessl workspace create

# Create a workspace in a specific organization
tessl workspace create --org 01935e2c-1234-5678-abcd-ef0123456789 engteam

#tessl workspace list

List all workspaces that you are a member of.

Usage

tessl workspace list [--has-publish-access]

Flags

• --has-publish-access (boolean, optional): Only show workspaces where you have permission to publish.

Examples

# List all workspaces you belong to
tessl workspace list

# List only workspaces you can publish to
tessl workspace list --has-publish-access

#tessl workspace delete

Delete an existing workspace.

Usage

tessl workspace delete [<name>]

Arguments

• name (string, optional): The name or ID of the workspace. If omitted, you'll be prompted.

Examples

# Delete a workspace
tessl workspace delete myworkspace

# Interactive deletion
tessl workspace delete

If a workspace has published a public plugin, deleting it permanently reserves its name: the name cannot be used again, in this organization or any other. To move a workspace between organizations, do not delete it. Email support@tessl.io and we can move it for you after a review.

#tessl workspace add-member

Add a user to a workspace with specified permissions.

Usage

tessl workspace add-member [--workspace <name>] [--username <username>] [--role <role>]

Flags

• --workspace (string, optional): Name or ID of workspace
• --username (string, optional): Username or ID of user to add
• --role (string, optional): Role to assign. Supported values: member, publisher, manager, owner

See Roles for more information

Examples

# Add a user to the workspace with a member role
tessl workspace add-member --workspace myworkspace --username johnsmith --role member

# Add a user to the workspace with an owner role
tessl workspace add-member --workspace myworkspace --username janesmith --role owner

# Interactive mode (prompts for all fields)
tessl workspace add-member

#tessl workspace remove-member

Remove a user from a workspace.

Usage

tessl workspace remove-member [--workspace <name>] [--username <username>]

Flags

• --workspace (string, optional): Name or ID of workspace
• --username (string, optional): Username or ID of user to remove

Examples

# Remove a member
tessl workspace remove-member --workspace myworkspace --username johnsmith

# Interactive mode
tessl workspace remove-member

#tessl workspace list-members

List all members of a workspace.

Usage

tessl workspace list-members [<name>]

Arguments

• name (string, optional): The name or ID of the workspace. If omitted, you'll be prompted.

Examples

# List members of a workspace
tessl workspace list-members myworkspace

# Interactive mode
tessl workspace list-members

#tessl workspace archive

Archive a workspace. An archived workspace won't be available to publish to or read from, but can be unarchived later.

Usage

tessl workspace archive --reason <text> [<name>]

Flags

• --reason (string, required): Reason for archiving the workspace

Arguments

• name (string, optional): The name or ID of the workspace. If omitted, you'll be prompted.

Notes

• Archiving is a safer alternative to deleting, as archived workspaces can be restored
• Use tessl workspace unarchive to restore an archived workspace

Examples

# Archive a workspace with a reason
tessl workspace archive --reason "deprecated" myworkspace

# Interactive mode
tessl workspace archive --reason "no longer in use"

#tessl workspace unarchive

Unarchive an archived workspace, making it active again.

Usage

tessl workspace unarchive <name>

Arguments

• name (string, required): The name or ID of the workspace.

Examples

# Unarchive a workspace
tessl workspace unarchive myworkspace

#Configuration management

#tessl config get

Get a configuration value or show all configuration.

Usage

tessl config get [<key>]

Arguments

• key (string, optional): Configuration key to get. If omitted, shows all configuration.

Examples

# Show all configuration
tessl config get

# Get a specific configuration value
tessl config get shareUsageData

#tessl config set

Set a configuration value.

Usage

tessl config set <key> <value>

Arguments

• key (string, required): Configuration key to set. Supported values: shareUsageData, termsAcceptedAt, evalDefaultModelNoticeShownAt, evalDefaultModelNoticeModel, agents
• value (string, required): Configuration value to set

Examples

# Set a configuration value
tessl config set shareUsageData false

#tessl config list

List all configuration values.

Usage

tessl config list [<key>]

Arguments

• key (string, optional): Configuration key to list. If omitted, lists all configuration.

Notes

• Similar to tessl config get but specifically for listing configuration values

Examples

# List all configuration
tessl config list

# List a specific configuration key
tessl config list shareUsageData

#tessl config add

Add one or more values to a configuration array.

Usage

tessl config add <key> <value>...

Arguments

• key (string, required): Configuration key for the array
• value (string, required, repeatable): One or more values to add to the array

Notes

• Use this command to add values to array-type configuration settings
• Can specify multiple values in a single command

Examples

# Add a single value to an array configuration
tessl config add agents cursor

# Add multiple values to an array configuration
tessl config add agents cursor claude-code

#tessl config remove

Remove a value from a configuration array.

Usage

tessl config remove <key> <value>

Arguments

• key (string, required): Configuration key for the array
• value (string, required): Value to remove from the array

Notes

• Use this command to remove values from array-type configuration settings
• Only removes the specified value, not the entire configuration key

Examples

# Remove a value from an array configuration
tessl config remove agents cursor

#Diagnostics and utilities

#tessl doctor

Run authentication and manifest diagnostics to troubleshoot issues.

Usage

tessl doctor [--json] [--automations]

Flags

• --json (boolean, optional): Output diagnostics as JSON for programmatic processing
• --automations (boolean, optional): Validate the actions, triggers, and schedules blocks of tessl.json, and report the agent each action selects, the project's loops, and whether the events of each trigger the file declares reach the workspace. It doesn't check delivery for loops defined in the Tessl app.

Notes

• --automations reads configuration and asks the platform about delivery. It sends no event and starts no run, so a clean result doesn't prove that a run starts. See Troubleshoot factory runs.

Examples

# Run diagnostics with human-readable output
tessl doctor

# Output diagnostics as JSON
tessl doctor --json

# Check the automation configuration and trigger delivery
tessl doctor --automations

#tessl feedback

Send feedback to the Tessl team.

Usage

tessl feedback [<message>]

Arguments

• message (string, optional): Feedback message to send. If omitted, you'll be prompted interactively.

Examples

# Send feedback directly
tessl feedback "Great tool! Would love to see Python support."

# Interactive feedback
tessl feedback

#CLI self-management

#tessl cli update

Update the CLI to the latest or specified version.

Usage

tessl cli update [--target <version>] [--channel <name>] [--dry-run]

Flags

• --target / -t (string, optional): Target version to update to (example: v1.0.0)
• --channel / -c (string, optional): Release channel to switch to. Supported values: latest, beta
• --dry-run (boolean, optional): Show what would be run without executing the update

Examples

# Update to the latest version
tessl cli update

# Update to a specific version
tessl cli update --target v1.0.0

# Switch to the beta release channel
tessl cli update --channel beta

# Preview update without executing
tessl cli update --dry-run

#API key management

#tessl api-key create

Create an API key for a workspace.

Usage

tessl api-key create [--workspace <name>] [--name <name>] [--role <role>] [--expiry-date <date> | --ttl <duration>]

Flags

• --workspace (string, optional): Name or ID of workspace
• --name (string, optional): Name for the API key
• --role (string, optional): Role to assign. Supported values: member, publisher, manager, owner
• --expiry-date (string, optional): Expiry date in ISO 8601 format (example: 2027-12-31T00:00:00Z). Defaults to 30 days from creation
• --ttl (string, optional): Time until expiry as a positive whole number followed by h (hours), d (days), w (weeks), mo (30-day months), or y (365-day years), such as 3h, 4w, or 1y. Minutes are not supported. Calculated using the local clock after interactive prompts, just before the creation request. Use either --ttl or --expiry-date. Without either flag, keys expire 30 days from creation

Examples

# Create an API key interactively
tessl api-key create

# Create an API key with all details specified
tessl api-key create --workspace engteam --name "ci-key" --role publisher --expiry-date 2027-12-31T00:00:00Z

# Create an API key that expires in four weeks
tessl api-key create --workspace engteam --name "ci-key" --role publisher --ttl 4w

#tessl api-key list

List API keys for a workspace.

Usage

tessl api-key list [--workspace <name>]

Flags

• --workspace (string, optional): Name or ID of workspace

Examples

# List API keys interactively
tessl api-key list

# List API keys for a specific workspace
tessl api-key list --workspace engteam

#tessl api-key delete

Delete an API key from a workspace.

Usage

tessl api-key delete [--workspace <name>] [--yes] [<api-key-id>]

Flags

• --workspace (string, optional): Name or ID of workspace
• --yes / -y (boolean, optional): Skip confirmation prompt and delete immediately

Arguments

• api-key-id (string, optional): ID of the API key to delete. If omitted, you'll be prompted.

Examples

# Delete an API key interactively
tessl api-key delete

# Delete a specific API key
tessl api-key delete --workspace engteam <api-key-id>

#Environment management

An environment is a named set of variables that a scheduled run, a launch, or a cloud run executes inside. Your organization holds it, and a run can use it only when the run's project is bound to it. Its values are sealed and write-only: you can set and replace them, but never read them back. Use an environment to supply the GitHub token, API keys, and any other credentials a run needs.

For what belongs in an environment and how runs consume it, see Environments.

The environment commands act on one organization, resolved in this order: --org, the TESSL_ORG environment variable, the organization of the workspace given by --workspace or TESSL_WORKSPACE or linked in tessl.json, then your only organization. If you belong to several and none of those apply, you are prompted to pick one, or must pass --org in a non-interactive shell.

Some environments are still held by a workspace. view, update, and delete look a name up in the organization first and then in the workspace in context, and list shows the workspace's environments after the organization's.

#tessl environment create

Create an environment for an organization.

Usage

tessl environment create [--org <name>] [--project <name>] [--env-file <path>] [--github-access <none|read|pull-requests|write>] [--linear-access <none|read|write>] [--read-other-run-logs] <name>

Arguments

• name (string, required): Name for the environment.

Flags

• --org (string, optional): Name or ID of organization. The default is the organization of the project.
• --project (string, optional): Project to bind the environment to, as a name, workspace/name, or ID. The default is the project the current directory is linked to.
• --env-file (string, optional): Path to a .env file with environment variables.
• --github-access (none, read, pull-requests, or write, optional): GitHub access granted to runs that use this environment. The default is read.
• --linear-access (none, read, or write, optional): Linear access granted to cloud launch runs that use this environment. The default is none.
• --read-other-run-logs (boolean, optional): Allow live runs to read other runs' transcripts in the same workspace. The default is off.

none mints no GitHub credential. The environment must supply a GITHUB_TOKEN or GH_TOKEN, or both TESSL_GITHUB_APP_ID and TESSL_GITHUB_APP_PRIVATE_KEY to mint a token as that GitHub App. Without either credential source, a run can't start. Tessl rejects an environment that holds a GITHUB_TOKEN or GH_TOKEN at any level other than none.

read can clone the repository but cannot push. pull-requests can push branches and open pull requests. write adds write access to issues, statuses, checks, Actions, and workflow files.

A person remains responsible for reviewing the changes and deciding whether to merge them. See Least privilege for environments.

For Linear access, none injects no platform credential. read permits Linear queries, while write also permits mutations. An environment cannot grant read or write while defining a non-empty LINEAR_TOKEN or LINEAR_API_URL. Tools must use LINEAR_TOKEN for authorization and LINEAR_API_URL as the API base URL; a tool that ignores LINEAR_API_URL sends the run key to Linear, which rejects it.

Notes

• --env-file is required unless a runtime access flag is given.
• The new environment is bound to the project from --project, else to the linked project, so that project's runs can use it straight away.
• With neither, no project can use the environment until you bind one with tessl environment bind or on the environment's page in the web app. See Bind projects to an environment.
• With --org, the project must be in that organization.

Examples

# Create an environment and load its values from a .env file
tessl environment create production --env-file production.env

# Create an environment and bind it to a project
tessl environment create production --project acme/my-repo --env-file production.env

# Create an environment in a specific organization, bound to no project
tessl environment create production --org acme --env-file production.env

# Create an environment whose runs can push branches and open pull requests
tessl environment create production --github-access pull-requests

# Create an environment that supplies its own GitHub token (production.env holds GITHUB_TOKEN)
tessl environment create production --env-file production.env --github-access none

# Create an environment whose cloud launch runs can read and write Linear
tessl environment create production --linear-access write

#tessl environment list

List environments for an organization, with the projects bound to each.

Usage

tessl environment list [--org <name>] [--workspace <name>] [--json]

Flags

• --org (string, optional): Name or ID of organization.
• --workspace (string, optional): Name or ID of a workspace whose environments are listed after the organization's.
• --json (boolean, optional): Output as JSON. Organization environments are under environments, and workspace environments under workspaceEnvironments.

Examples

# List environments in the resolved organization
tessl environment list

# List environments in a specific organization
tessl environment list --org acme

# Output as JSON
tessl environment list --json

#tessl environment view

View metadata and bound projects for an environment.

Usage

tessl environment view [--org <name>] [--workspace <name>] [--json] <name>

Arguments

• name (string, required): Name or ID of the environment to view.

Flags

• --org (string, optional): Name or ID of organization.
• --workspace (string, optional): Name or ID of a workspace to search when the organization holds no environment by that name.
• --json (boolean, optional): Output as JSON.

Notes

• This shows metadata only, such as the variable names, bound projects, GitHub access, Linear access, and MCP servers wired in. Sealed values are write-only and are never returned.
• The output includes a link to the environment in the Tessl web app (webUrl in --json output).

Examples

# View an environment
tessl environment view production

# View an environment as JSON
tessl environment view production --json

#tessl environment update

Update an environment.

Usage

tessl environment update [--org <name>] [--workspace <name>] [--env-file <path>] [--remove-key <name>] [--github-access <none|read|pull-requests|write>] [--linear-access <none|read|write>] [--read-other-run-logs] [--mcp-server <name>] [--clear-mcp-servers] <name>

Arguments

• name (string, required): Name or ID of the environment to update.

Flags

• --org (string, optional): Name or ID of organization.
• --workspace (string, optional): Name or ID of a workspace to search when the organization holds no environment by that name.
• --env-file (string, optional): Path to a .env file with environment variables.
• --remove-key (string, optional, repeatable): Stored key to remove.
• --github-access (none, read, pull-requests, or write, optional): GitHub access granted to runs that use this environment.
• --linear-access (none, read, or write, optional): Linear access granted to cloud launch runs that use this environment.
• --read-other-run-logs (boolean, optional): Allow live runs to read other runs' transcripts in the same workspace. Use --no-read-other-run-logs to disable.
• --mcp-server (string, optional, repeatable): Name of an MCP server to configure. Workspace environments only.
• --clear-mcp-servers (boolean, optional): Remove all MCP servers wired into a workspace environment.

none mints no GitHub credential, so the run must bring its own token. read can clone the repository but cannot push. write can push branches and open pull requests.

For Linear access, none injects no platform credential. read permits Linear queries, while write also permits mutations. An environment cannot grant read or write while defining a non-empty LINEAR_TOKEN or LINEAR_API_URL. Tools must use both injected variables: LINEAR_TOKEN for authorization and LINEAR_API_URL as the API base URL.

Notes

• --env-file is required unless --remove-key or a runtime access flag is given. An update with no --env-file changes just those settings and leaves every other stored value untouched. Passing --env-file replaces the plain values instead: the env file becomes the complete set of plain values, so it must include every plain credential you want to keep. An organization environment keeps its secret references, except that a name set in the file becomes a plain value and its reference is removed. The command prints the names it converted. --remove-key removes a name whether it is a plain value or a secret reference.
• --remove-key cannot be combined with --env-file.
• --mcp-server and --clear-mcp-servers apply to workspace environments only.
• --clear-mcp-servers always requires --env-file.

Examples

# Replace an environment's values from a .env file
tessl environment update production --env-file production.env

# Let runs that use the environment push branches and open pull requests (stored values are kept)
tessl environment update production --github-access pull-requests

# Remove a stored Linear token and let runs use the proxied Linear access instead
tessl environment update production --remove-key LINEAR_TOKEN --linear-access read

#tessl environment bind

Bind a project to an organization environment, so the project's loops can use it.

Usage

tessl environment bind [--org <name>] [--project <name>] [--json] <name>

Arguments

• name (string, required): Name or ID of the environment to bind the project to.

Flags

• --org (string, optional): Name or ID of organization. The default is the organization of the project.
• --project (string, optional): Project to bind, as a name, workspace/name, or ID. The default is the project the current directory is linked to.
• --json (boolean, optional): Output as JSON, with the environment, the project, and status set to bound or already-bound.

Notes

• Binding a project that is already bound succeeds, says so, and changes nothing.
• The project must be in the environment's organization.
• An environment still held by a workspace has no project bindings, so the command refuses it and changes nothing.
• Without --project, the command fails when the current directory is not linked to a project.

Examples

# Bind the project the current directory is linked to
tessl environment bind production

# Bind a named project
tessl environment bind production --project engteam/web-app

#tessl environment unbind

Unbind a project from an organization environment, so the project's loops can no longer use it.

Usage

tessl environment unbind [--org <name>] [--project <name>] [--json] <name>

Arguments

• name (string, required): Name or ID of the environment to unbind the project from.

Flags

• --org (string, optional): Name or ID of organization. The default is the organization of the project.
• --project (string, optional): Project to unbind, as a name, workspace/name, or ID. The default is the project the current directory is linked to.
• --json (boolean, optional): Output as JSON, with the environment, the project, and status set to unbound or not-bound.

Notes

• Unbinding a project that is not bound succeeds, says so, and changes nothing.
• An environment still held by a workspace has no project bindings, so the command refuses it and changes nothing.
• Without --project, the command fails when the current directory is not linked to a project.

Examples

# Unbind the project the current directory is linked to
tessl environment unbind production

# Unbind a named project
tessl environment unbind production --project engteam/web-app

#tessl environment delete

Delete an environment.

Usage

tessl environment delete [--org <name>] [--workspace <name>] [name]

Arguments

• name (string, optional): Name or ID of the environment to delete. You are prompted when it is omitted.

Flags

• --org (string, optional): Name or ID of organization.
• --workspace (string, optional): Name or ID of a workspace to search when the organization holds no environment by that name.

Examples

# Delete an environment
tessl environment delete staging

# Delete an environment from a specific organization
tessl environment delete staging --org acme

#Model Context Protocol (MCP)

#tessl mcp start

Start the Tessl MCP (Model Context Protocol) server for integration with AI coding agents.

Usage

tessl mcp start

#tessl mcp proxy

Bridge a coding agent to a workspace MCP server through the Tessl MCP gateway. Starts a stdio MCP proxy that forwards JSON-RPC messages to an upstream MCP server held by the workspace or moved from it into the organization. It authenticates to the gateway with your Tessl credentials (tessl login) or TESSL_TOKEN. See MCP gateway for which servers the proxy reaches and how to wire it into an agent or plugin .mcp.json.

Usage

tessl mcp proxy <workspace>/<mcp>

Arguments

• workspace/mcp (string, required): Slug of the workspace and the name of the MCP server (for example engteam/linear).

Authentication

• Interactive use — sign in once with tessl login; the proxy reuses the same credentials.
• CI or other non-interactive contexts — set TESSL_TOKEN to a Tessl API key for the workspace. See tessl api-key create.

Examples

# Proxy to an MCP server named `linear` in the `engteam` workspace
tessl mcp proxy engteam/linear

#Repository

#tessl repo select-commits

Browse recent commits in a repository and select which ones to evaluate. Used as the first step in generating codebase scenarios.

Usage

tessl repo select-commits <org/repo> [flags]

Arguments

• org/repo (string, required): Repository in org/repo format

Flags

• --keyword (string, optional): Filter by commit message keyword
• --author (string, optional): Filter by author name
• --since / --until (string, optional): Date range in YYYY-MM-DD format
• --count / -n (number, optional): Number of commits to show (1–100)
• --workspace / -w (string, optional): Required outside interactive mode
• --json (boolean, optional): Output as JSON

Prerequisite: your GitHub or GitLab account must be connected in workspace settings. If it isn't, the error message includes a direct link to the settings page.

Examples

# Browse recent commits
tessl repo select-commits org/repo

# Filter by keyword and date range
tessl repo select-commits org/repo --keyword=feat --since=2026-01-01

# Show last 50 commits by a specific author
tessl repo select-commits org/repo --author="Alice" --count=50

#GitHub integration

Tessl App is a GitHub App your workspace installs. These commands mint short-lived installation tokens so CI steps and coding agents can act as the Tessl App bot without holding the App's private key.

A workspace can reach the Tessl App on more than one GitHub account. Pass --repo owner/name to say which: the owner selects the installation to mint from, and the repository names limit what the token can reach. Without it, the most recently updated installation is used, which may not be the one that owns the repositories you want.

#tessl github token

Mint a short-lived GitHub installation token for the Tessl App bot and print it to stdout.

Usage

tessl github token [--workspace <name>] [--repo <owner/name>]...

Flags

• --workspace (string, optional): Name or ID of workspace
• --repo (string, optional, repeatable): Scope the token to a repository and select its installation by owner, in owner/name form. All values must share one owner, since a token is minted against a single installation.

Notes

• The token is written to stdout so it can be captured directly, for example GH_TOKEN=$(tessl github token ...). The expiry is written to stderr, so it does not pollute that capture.
• The minted token is a GitHub App installation token, not a user token. Installation-scoped endpoints such as /installation/repositories work; user-scoped endpoints such as gh org list fail.
• Without --repo, the token covers everything the selected installation can reach.

Examples

# Mint a token scoped to one repository
tessl github token --workspace engteam --repo my-org/my-repo

# Scope to several repositories owned by the same account
tessl github token --workspace engteam --repo my-org/api --repo my-org/web

# Capture the token for a single command
GH_TOKEN=$(tessl github token --workspace engteam --repo my-org/my-repo) gh api /installation/repositories

#tessl github setup-auth

Configure gh and git on this machine to act as the Tessl App bot, so subsequent commands authenticate without a token in the environment.

Usage

tessl github setup-auth [--workspace <name>] [--repo <owner/name>]... [--force] [--auto-refresh] [--refresh-interval-seconds <seconds>]

Flags

• --workspace (string, optional): Name or ID of workspace
• --repo (string, optional, repeatable): Scope the token to a repository and select its installation by owner, in owner/name form. All values must share one owner.
• --force (boolean, optional): Overwrite an existing gh/git auth configuration. Without it, the command stops rather than replacing one already in place.
• --auto-refresh (boolean, optional): Spawn a background process that re-mints the token periodically, for steps that outlive a single token.
• --refresh-interval-seconds (number, optional): How often that background process re-mints, in seconds. Defaults to 2700, which is 45 minutes.

Notes

• Signs in gh and sets a global git identity for the bot. This persists after the command exits, so prefer an ephemeral runner or container.
• Refuses to run when gh is already signed in or a global git identity is already set. Use --force to replace them.
• Clear GH_TOKEN and GITHUB_TOKEN first. gh prefers a token in the environment over the credential this writes.
• Without --auto-refresh the credential lasts until the expiry the command prints.
• With --repo, refreshes re-mint against the same owner and repositories. Without it, each refresh picks the most recently updated installation.

Examples

# Authenticate for one repository
tessl github setup-auth --workspace engteam --repo my-org/my-repo

# Long-running CI step, refreshing in the background
tessl github setup-auth --workspace engteam --repo my-org/my-repo --auto-refresh

# Replace an existing gh/git configuration
tessl github setup-auth --workspace engteam --repo my-org/my-repo --force

#Inventory

#tessl inventory import

Scan a GitHub account or org for installed skills and upload an inventory. Forked repos are skipped.

Usage

tessl inventory import [--org <account>] [--workspace <name>] [--repo <repo>]... [--ignore-repo <repo>]... [--dry-run <path>]

Flags

• --org (string, optional): GitHub account or org to scan. Prompted if omitted.
• --workspace (string, optional): Name or ID of workspace to upload to. Prompted if omitted.
• --repo (string, repeatable, optional): Limit scan to this repo (repeatable)
• --ignore-repo (string, repeatable, optional): Exclude this repo from the scan (repeatable)
• --dry-run (string, optional): Write inventory JSON to the given path instead of uploading

Notes

• --org and --workspace are prompted when omitted in interactive sessions, but required as flags in non-interactive environments (including with --dry-run)

Examples

# Scan an org and upload to a workspace
tessl inventory import --org my-github-org --workspace engteam

# Limit the scan to specific repositories
tessl inventory import --org my-github-org --workspace engteam --repo repo-a --repo repo-b

# Preview the inventory without uploading
tessl inventory import --org my-github-org --workspace engteam --dry-run ./inventory.json

#Scenario management

Scenario commands generate and manage eval scenarios from real repository commits. For a full walkthrough, see Prove a skill works using evaluation.

#tessl scenario generate

Generate eval scenarios from a plugin or repository commits. Runs server-side — the CLI polls until complete. Ctrl-C detaches without cancelling; check progress with tessl scenario list.

Alias: tessl scenarios generate

Usage

tessl scenario generate [--commits <hash1,hash2>] [--prs <id1,id2>] [--count <n>] [--workspace <name>] [--context <globs>] [--json] [--no-wait] <source>

Arguments

• source (string, required): plugin path or org/repo to generate scenarios from

Flags

• --commits (string, optional): Comma-separated commit hashes to generate scenarios from (repo only)
• --prs (string, optional): Comma-separated PR numbers to resolve as commit ranges (repo only)
• --count / -n (number, optional): Number of new scenarios to add (plugin only)
• --context (string, optional): Glob patterns for context files to exclude from baseline, comma-separated (repo only). These patterns are stored in each generated scenario.json as fixture.exclude — they are stripped for the baseline eval variant and injected back for the with-context variant. Defaults to *.mdc, *.md, tile.json, .tessl-plugin/plugin.json, tessl.json, .tessl/ when omitted.
• --workspace / -w (string, optional): Workspace name or ID (repo only). Required outside interactive mode.
• --json (boolean, optional): Output as JSON
• --wait / --no-wait (boolean, optional): Wait for the generation to finish before returning (default: wait when interactive; a non-interactive run, such as CI, submits and returns without waiting; use --no-wait to force that anywhere, then reconnect with tessl scenario view). --json on its own also detaches; pass --wait --json to poll to completion and still get JSON.

Examples

# Generate scenarios for two commits
tessl scenario generate org/repo --commits=abc123,def456

# Generate scenarios from PRs
tessl scenario generate org/repo --prs=42,43

# Generate scenarios from a plugin
tessl scenario generate ./my-plugin --count=5

# Specify context file patterns
tessl scenario generate org/repo --commits=abc123 --context="*.mdc,*.md"

# Non-interactive with workspace
tessl scenario generate org/repo --commits=abc123 --workspace=engteam

#tessl scenario list

List recent scenario generation runs in reverse chronological order.

Alias: tessl scenarios list

Usage

tessl scenario list [--mine] [--workspace <name>] [--limit <count>] [--status <status>] [--json]

Flags

• --mine (boolean, optional): Only show generation runs created by you
• --workspace / -w (string, optional): Filter by workspace name
• --limit (number, optional): Maximum number of runs to display (default: 20)
• --status (string, optional): Filter by status. Supported values: pending, in_progress, completed, failed
• --json (boolean, optional): Output as JSON

#tessl scenario view

Inspect a scenario generation run. Shows run metadata and a table of generated scenarios with titles and checklist item counts.

Alias: tessl scenarios view

Usage

tessl scenario view [--last] [--json] [<id>]

Flags

• --last (boolean, optional): View the most recent generation run
• --json (boolean, optional): Output as JSON

Arguments

• id (string, optional): Generation run ID. Either id or --last is required.

Examples

# View the most recent generation run
tessl scenario view --last

# View a specific run
tessl scenario view 019c4791-9eec-7458-b28a-6c94405a3d38

#tessl scenario download

Download generated scenarios to your local evals/ folder.

Alias: tessl scenarios download

Usage

tessl scenario download [--output <dir>] [--strategy <strategy>] [--json] [--last] <id>...

Flags

• --output / -o (string, optional): Output directory. Default: <plugin-root>/evals when run from inside a plugin (the plugin root or any subdirectory of it), otherwise ./evals. The default depends only on the current directory, not on the plugin the scenarios were generated from
• --strategy / -s (string, optional): Write strategy: merge (default) adds new scenarios alongside existing ones and overwrites only a folder with the same name; replace clears the directory first
• --json (boolean, optional): Output as JSON
• --last (boolean, optional): Download from your most recent generation run, from any plugin or directory. If you started another generation since, pass its generation ID instead

Arguments

• id (string, required, repeatable): Generation IDs to download. Can specify multiple IDs. Either id or --last is required.

If the generation run is still in progress or pending, the command reports the status and exits.

Scenario folders are named scenario-0/, scenario-1/, and so on. In recent CLI versions, tessl scenario generate <plugin-root> sends the plugin's existing evals/ with the plugin, so new scenarios are numbered from the next free index and merge keeps the existing folders. A downloaded folder overwrites an existing folder only when the names match, for example when you download the same generation twice. With an older CLI, a second generation starts again at scenario-0/, so merge overwrites the earlier folders.

Run the download from inside the plugin you generated from, or pass --output <plugin-root>/evals. From outside a plugin, the scenarios land in ./evals, and tessl eval run <plugin-root> finds no scenarios.

Downloaded structure:

evals/
  scenario-0/
    task.md          ← task brief shown to the agent
    criteria.json    ← weighted checklist rubric
    scenario.json    ← fixture with repo URL, commit ref, and context exclude patterns

Examples

# Download from the most recent generation run, from inside the plugin
cd my-plugin && tessl scenario download --last

# Download into a plugin's evals/ from outside the plugin
tessl scenario download --last --output ./my-plugin/evals

# Download to a custom directory, replacing existing scenarios
tessl scenario download --last --output=my-evals --strategy=replace

# Download a specific run
tessl scenario download 019c4791-9eec-7458-b28a-6c94405a3d38

#Evaluations

For more information on workflows and usage, see Prove a skill works using evaluation.

#tessl eval run

Run evals from a scenarios directory. The context under test, if any, comes from --context; with no context, the run is the baseline variant alone (see Notes).

• Codebase eval: source directory contains scenario.json fixtures → runs with smart defaults (agent claude, model deepseek-v4.1-flash, context pattern from fixture.exclude, context ref infer)
• Plugin eval — source contains .tessl-plugin/plugin.json → runs the plugin's own evals. Pass the plugin root directory (the directory that contains .tessl-plugin/, not .tessl-plugin/ itself).

Pointing at a plugin directory is shorthand: tessl eval run ./my-plugin expands to tessl eval run ./my-plugin/evals --context ./my-plugin — the plugin's evals/ as the scenarios, the plugin itself as the context. An explicit --context opts out of the shorthand.

Usage

tessl eval run [--agent <agent>] [--model <model>] [--scorer-agent <agent>] [--scorer-model <model>] [--context <source>] [--context-commit <ref>] [--skill <name>]... [--skip-baseline] [--variant-json <json-or-path>] [--allow-unsafe-fixture-paths] [--runs <count>] [--label <text>] [--env-file <path>] [--skip-forced-context-activation] [--skip-scoring] [--force] [--quality-check] [--list-agents] [--yes] [--json] [--no-wait] [<source>]

Flags

• --agent (string, optional): Agent to run with (e.g. claude). May be passed alone or together with --model. Run tessl eval run --list-agents to see supported values and combinations. Default pair when neither override is supplied: claude / deepseek-v4.1-flash

• --model (string, optional): Model to run with (e.g. claude-sonnet-4-5). May be passed alone or together with --agent. Run tessl eval run --list-agents to see supported values and combinations. Default pair when neither override is supplied: claude / deepseek-v4.1-flash

• --scorer-agent (string, optional): Override the agent used for the scoring step; the solver agent is unchanged. May be passed alone or together with --scorer-model.

• --scorer-model (string, optional): Override the model used for the scoring step; the solver model is unchanged. May be passed alone or together with --scorer-agent.

• --context (string, optional): Context to test — a local path (a plugin directory, or a file/glob), or a published workspace/plugin@version. Adds the with-context variant alongside the baseline. See the examples below.

• --context-commit (string, optional): Commit, branch, or tag to source a local --context from instead of the working tree. Requires --context.

• --skill (string, optional, repeatable): Narrow a local plugin --context to specific skills. Local plugin contexts only — not valid with a published context.

• --skip-baseline (boolean, optional): Skip the always-on baseline variant, running only the with-context variant.

• --variant-json (string, optional): Test variants to run, as a JSON array or the path to a JSON file (up to 1 MiB). The run solves only the variants you list. No baseline is added. Cannot be combined with --skip-baseline or --arms-json. Each object in the array can contain:

  • label (string, required): A unique name for the variant. Labels use lowercase letters, digits, hyphens, and underscores; they start with a letter or digit and are at most 64 characters.
  • agent (string, optional): Overrides the run's agent.
  • model (string, optional): Overrides the run's model.
  • fixtures (object, optional): Replaces, adds, or removes named fixtures. Set a fixture to null to remove it; omitted fixtures inherit the run's setup.
  • includeContext (boolean, optional, deprecated): Controls whether the subject context fixture is included. Object variants include it by default; set this to false to remove it.
  • forceContextActivation (boolean, optional, deprecated): Overrides whether the context fixtures are forced to activate.
  • agentMustRead (string array, optional): Names fixtures whose installed locations the solve agent must read before starting.

  For example, run 2 variants with different models:

  [
    { "label": "fast", "model": "claude-haiku-4-5" },
    { "label": "thorough", "model": "claude-sonnet-4-5" }
  ]

  See Comparing test variants for fixture details and examples.

• --arms-json (string, optional): Deprecated. Use --variant-json.

• --allow-unsafe-fixture-paths (boolean, optional): Allow directory fixtures, localPath variant fixtures, and packed symlinks that resolve outside the repository (or the source directory, when it is not in a repository). The CLI packages and uploads that external content for remote evaluation, where the evaluation agent can access it. Use this flag only for content you intend to share, including resolved symlink targets.

• --runs / -n (number, optional): Number of times to repeat each variant, from 1 to 10.

• --label / -l (string, optional): A short description to attach to this eval run. Visible in tessl eval list and the Tessl web UI.

• --env-file (string, optional): Path to a .env file whose variables are encrypted client-side and made available to the run's sandbox environment.

• --skip-forced-context-activation (boolean, optional): Omit the prompt line that tells the agent to use the injected context, so the run measures whether the agent activates the context on its own. Default off (the agent is told to use the context).

• --skip-scoring (boolean, optional): Skip the rubric scoring step. Default off (runs are scored).

• --force / -f (boolean, optional): Re-run all evals, including previously solved cases.

• --quality-check (boolean, optional): Exclude misleading scenarios (low feasibility, rubric leakage, low value) from the run. Excluded scenarios appear in tessl eval view under a ✗ Excluded by quality check line.

• --list-agents (boolean, optional): Print the supported --agent / --model values, then exit without running an eval. Combine with --json for a machine-readable shape.

• --yes / -y (boolean, optional): Skip the confirmation prompt for large-scale eval runs.

• --json (boolean, optional): Output eval run IDs as JSON. On its own it detaches and prints the run ids immediately without polling; pass --wait --json to poll to completion and emit each run id with its final status.

• --wait / --no-wait (boolean, optional): Wait for the run to finish before returning (default: wait when interactive; use --no-wait to submit and return the run ids immediately, then reconnect with tessl eval view). --json on its own detaches; pass --wait --json to poll to completion and still get JSON.

Arguments

• source (string, optional): Path to a plugin folder or scenarios directory. Defaults to the current directory if omitted.

Notes

• Without --variant-json, a run has up to two variants. The baseline solves each scenario as authored; the with-context variant solves it with the injected context added on top. Baseline is not an empty run: each scenario keeps any fixtures it defines; no context is injected on top. The with-context variant runs when context is specified. Baseline runs by default; use --skip-baseline to run only the with-context variant. With --variant-json, the run has exactly the variants you list.
• Eval runs require this directory to be linked to a Tessl project first, and always run under that project's workspace. See Projects overview.
• To measure whether the agent activates the injected context on its own, with no rubric scoring, combine both flags: --skip-forced-context-activation --skip-scoring.
• Ctrl-C detaches without cancelling: runs continue server-side. The CLI prints each run ID.
• --no-wait submits the runs and returns their ids without polling; reconnect later with tessl eval view. --json alone also detaches, so pass --wait --json when a pipeline needs to block for the final per-run status.

Agent and model: --agent and --model are independent overrides; supply either or both. Run tessl eval run --list-agents for the supported combinations.

Examples

# Run a plugin's evals (shorthand for ./my-plugin/evals --context ./my-plugin)
tessl eval run .

# ...or point at the plugin by path
tessl eval run ./my-plugin

# Run a scenarios directory with no context: a baseline-only run.
# This applies only to a directory outside a plugin's evals/. For a plugin's
# evals/, the CLI refuses the run and asks you to point at the plugin root.
tessl eval run ./scenarios/

# Narrow a multi-skill plugin's context to two of its skills
tessl eval run ./my-plugin --skill write-endpoint --skill review-endpoint

# Force re-run all evals
tessl eval run --force ./my-plugin

# Run with a specific agent and model
tessl eval run ./my-plugin --agent claude --model claude-sonnet-4-6

# List the supported --agent / --model values
tessl eval run --list-agents

# Skip scenarios the LLM judge flags as misleading
tessl eval run ./my-plugin --quality-check

# Measure context activation only: don't force the agent to use the context, and skip scoring
tessl eval run ./my-plugin --skip-forced-context-activation --skip-scoring

# Test a published context against a scenarios directory
tessl eval run ./evals/ --context engteam/my-plugin@1.0.0

# Test a local plugin directory as the context
tessl eval run ./evals/ --context ./my-plugin

# Test a glob of local files as the context
tessl eval run ./evals/ --context 'src/**/*.knowledge.md'

# Test a file or glob context as it was at a specific commit
# (--context-commit is not supported for a plugin context)
tessl eval run ./evals/ --context 'src/**/*.knowledge.md' --context-commit HEAD

# Run only the with-context variant (skip the baseline)
tessl eval run ./my-plugin --skip-baseline

# Label a run for easier identification later
tessl eval run ./my-plugin --label "testing claude-opus-4-6"

# Pass secrets into the sandbox via an env file
tessl eval run ./my-plugin --env-file ./secrets.env

#tessl eval list

List recent eval runs in reverse chronological order.

Usage

tessl eval list [--json] [--limit <count>] [--mine] [--workspace <name>] [--plugin <name>] [--status <status>] [--context-type <type>]

Flags

• --json (boolean, optional): Output results as JSON
• --limit (number, optional): Maximum number of eval runs to display (default: 20)
• --mine (boolean, optional): Only show eval runs created by you
• --workspace / -w (string, optional): Filter by workspace name
• --plugin (string, optional): Filter by plugin name
• --status (string, optional): Filter by run status. Supported values: pending, completed, failed
• --context-type (string, optional): Filter by eval type. Supported values: plugin, plugin-directory, files, commit, no-context

Notes

• The output table includes ID, Type, Subject, Status, Created By, and Created columns
• The Type column reflects the context fixture used by the run:
  • plugin → Plugin
  • plugin-directory → Plugin directory
  • files (alias for the directory fixture) → Selected files when globs filter it to a subset, otherwise Directory
  • commit → Commit
• The Subject column formats entries by fixture: plugin runs as workspace/plugin@version (or just workspace/plugin when no version is set); plugin-directory and files as the source path; commit as org/repo@ref
• --context-type no-context filters to baseline runs that did not inject any context fixture
• files is the documented spelling of the canonical directory fixture — both names accepted

Examples

# List all recent eval runs
tessl eval list

# List only completed runs
tessl eval list --status completed

# List your runs in a specific workspace
tessl eval list --mine --workspace myteam

# Output as JSON
tessl eval list --json

#tessl eval view

View results for a specific eval run.

Usage

tessl eval view [--json] [--last] [<id>]

Flags

• --json (boolean, optional): Output results as JSON
• --last (boolean, optional): View results for the most recent eval run

Arguments

• id (string, optional): Eval run ID

Examples

# View a specific eval run
tessl eval view 019c4791-9eec-7458-b28a-6c94405a3d38

# View the most recent eval run
tessl eval view --last

# View results as JSON
tessl eval view --json 019c4791-9eec-7458-b28a-6c94405a3d38

#tessl eval compare

Compare two to ten distinct eval runs side-by-side.

Usage

tessl eval compare [--json] [--full] [--turns] <id>...

Flags

• --json (boolean, optional): Output as JSON
• --full (boolean, optional): Show the full distribution (minimum, quartiles, median, mean, maximum, and standard deviation) for each cell
• --turns (boolean, optional): Append the per-turn and tool-usage section. This data is currently untrustworthy.

Arguments

• id (string, required, repeatable): Distinct eval run ID

Examples

# Compare two eval runs
tessl eval compare <first-run-id> <second-run-id>

# Show each run's full statistical distribution
tessl eval compare <first-run-id> <second-run-id> --full

#tessl eval list-solutions

List the results produced by an eval run.

Usage

tessl eval list-solutions [--json] <eval-run-id>

Flags

• --json (boolean, optional): Output raw JSON

Arguments

• eval-run-id (string, required): Eval run ID

Examples

# List an eval run's results and their IDs
tessl eval list-solutions <run-id>

#tessl eval download-solutions

Download files from an eval run.

Usage

tessl eval download-solutions [--solution <id>]... --output <dir> <eval-run-id>

Flags

• --solution / -s (string, optional, repeatable): ID to download. When omitted, downloads all completed solution entries from the eval run.
• --output / -o (string, required): Output directory

Arguments

• eval-run-id (string, required): Eval run ID

Examples

# Download every completed solution from an eval run
tessl eval download-solutions <run-id> --output ./solutions

# Download one solution
tessl eval download-solutions <run-id> --solution <solution-id> --output ./solution

#tessl eval retry

Re-run a failed eval run.

Usage

tessl eval retry [--json] [--last] [<id>]

Flags

• --json (boolean, optional): Output as JSON
• --last (boolean, optional): Retry the most recent eval run

Arguments

• id (string, optional): Eval run ID to retry. Either id or --last is required.