@isummation/kasauti-cli

Command line for Kasauti test management, and the Kasauti plugin for Claude Code.

• People and scripts use the kasauti command to explore, write and run test cases and to report and fix defects.
• Claude Code gets the Kasauti tools (MCP) and three playbooks: explore a screen into test cases, run tests, fix defects.

Output is Markdown, which people and AI agents both read easily; add --json for scripts. Needs Node.js 20 or later; no dependencies.

Install

npm install -g @isummation/kasauti-cli

Or run it once without installing: npx @isummation/kasauti-cli --help.

What you need from Kasauti

• The API URL, for example https://kasauti-api.your-company.com. It's the API's address, not the web app's; your Kasauti admin can tell you, and the web app shows it under Settings → API tokens & agents.
• A token, created in the web app under Settings → API tokens & agents. It is shown once, so copy it then.
  • Personal token: for the kasauti command as yourself, and for CI.
  • Agent token: for Claude Code. Everything it writes is marked as the agent, its test cases start as drafts for a person to approve, and it can't verify fixes.
  • A token works only on the Kasauti server it was created on, and has your role there (tester or developer).

Use the CLI

kasauti login https://kasauti-api.your-company.com --token <personal token>   # saved to ~/.kasauti.json, readable only by you
kasauti whoami
kasauti projects
kasauti map SHOP                 # screens / endpoints with coverage and open defects
kasauti get SHOP-D7              # anything by key, with full context
kasauti defects SHOP --mine
kasauti result SHOP-R5 SHOP-12 failed -m "Total shows twice" --attach shot.png
kasauti --help                   # every command

Keys name everything. The letter after the project code says what a key is:

| Key | What it is | |---|---| | SHOP-12 | test case (no letter) | | SHOP-A3 | area: a screen, endpoint or module | | SHOP-SC4 | scenario: a user goal | | SHOP-R5 | run: cases being executed | | SHOP-P2 | plan: a saved set of cases | | SHOP-M1 | milestone | | SHOP-D7 | defect |

KASAUTI_URL and KASAUTI_TOKEN in the environment take precedence over the saved login. CI uses them: store both as secret CI variables and no login step is needed.

Connect Claude Code

1. Install the plugin

kasauti plugin install           # for all your projects; --scope local for the current project only

This runs claude plugin marketplace add and claude plugin install for the copy of the plugin inside this package. If the claude command isn't on your PATH, it prints the two commands to run yourself.

2. Give Claude Code the URL and an agent token. The plugin reads them from two environment variables, KASAUTI_URL and KASAUTI_TOKEN. kasauti login does not set them: it only configures the kasauti command. Without them, the plugin calls http://localhost:3001 with no token.

Set them where Claude Code starts. The commands below ask for the token without showing it, so it stays out of your shell history.

• Linux, WSL, macOS with bash: add them to ~/.bashrc:

  read -rsp "Kasauti agent token: " T && printf '\nexport KASAUTI_URL=https://kasauti-api.your-company.com\nexport KASAUTI_TOKEN=%s\n' "$T" >> ~/.bashrc && unset T && echo

• macOS with zsh (the default): the same command with ~/.zshrc instead of ~/.bashrc.

• fish:

  set -Ux KASAUTI_URL https://kasauti-api.your-company.com
  read -s -P "Kasauti agent token: " T; and set -Ux KASAUTI_TOKEN $T; and set -e T

• Windows (Claude Code running on Windows itself, in PowerShell):

  [Environment]::SetEnvironmentVariable('KASAUTI_URL', 'https://kasauti-api.your-company.com', 'User')
  $t = Read-Host 'Kasauti agent token' -AsSecureString
  [Environment]::SetEnvironmentVariable('KASAUTI_TOKEN', [Net.NetworkCredential]::new('', $t).Password, 'User'); Remove-Variable t

  If you use Claude Code inside WSL (including VS Code connected to WSL), use the bash setup above instead: Windows variables don't reach it.

To change a value later, edit the line in that file rather than running the command again, which would add a second copy.

3. Restart Claude Code. It reads the variables only when it starts. In a terminal, open a new one. In VS Code (and other editors), close every window and reopen the editor; reloading a window isn't enough. For VS Code with WSL, if it still shows the old state, run wsl --shutdown in Windows and reopen.

4. Check. In Claude Code, run /mcp: kasauti should show as connected. Then ask "List my Kasauti projects". In a terminal, echo $KASAUTI_URL should print your URL.

Keep an agent to one project

If you're on several projects, give each repository its own token limited to that project. The agent then can't read or change any other project, even by mistake: other projects don't exist for that token, and it can't create tokens or do admin work.

1. Create the token in the web app (Settings → API tokens & agents, pick the project), or with the CLI:

   kasauti token claude-code-shop --agent claude-code --project SHOP

2. Put it in the repository's .claude/settings.local.json. Claude Code applies its env only in this repository, over the variables from your shell, so your other repositories keep their own tokens:

   {
     "env": {
       "KASAUTI_URL": "https://kasauti-api.your-company.com",
       "KASAUTI_TOKEN": "kst_…"
     }
   }

   settings.local.json is for you alone: Claude Code adds it to the repository's .gitignore when it creates the file. Check it is ignored before you save a token in it; never put a token in the shared .claude/settings.json.

3. Restart Claude Code in that repository and run /mcp. Asking "List my Kasauti projects" should show only that project.

Deleting the project deletes its tokens. Revoke a token under Settings → API tokens & agents.

Update

npm update -g @isummation/kasauti-cli
kasauti plugin update

Claude Code loads the plugin from the npm install folder, so the next session uses the new version. Switching Node.js versions (nvm, fnm, volta) moves that folder: install the CLI for the new version and run kasauti plugin install again.

Remove

claude plugin uninstall kasauti@kasauti
claude plugin marketplace remove kasauti
npm uninstall -g @isummation/kasauti-cli

Without the plugin (Cursor and other MCP clients)

Kasauti is a standard MCP server over HTTP: URL <KASAUTI_URL>/mcp, header Authorization: Bearer <agent token>. kasauti mcp-config prints the Claude Code command for your settings. You get the tools, without the playbooks.

Troubleshooting

| What you see | Fix | |---|---| | /mcp: kasauti failed, HTTP 401 or Invalid or expired token | KASAUTI_TOKEN isn't set where Claude Code started, was created on a different Kasauti server, or was revoked. Set it (step 2) and restart Claude Code fully. | | /mcp shows http://localhost:3001/mcp | KASAUTI_URL isn't set where Claude Code started. Set it and restart Claude Code fully. | | Error 401 from kasauti | Log in again with a valid token, or check the KASAUTI_TOKEN you exported. | | Error 404 for a project that exists | You aren't assigned to it; ask a Kasauti admin. | | Error 403 … needs the tester role or needs a human | Your role can't do that; agent tokens can't verify fixes or approve drafts. | | Cannot reach … | Wrong KASAUTI_URL (use the API address), or no network route to it. | | kasauti plugin install: No bundled plugin here | The kasauti on your PATH isn't this npm package. Run npm install -g @isummation/kasauti-cli. | | The plugin vanished after switching Node.js versions | Run kasauti plugin install again. |