Add interactive login

CLAUDE.md

@@ -89,13 +89,11 @@ Important note: Online documentation is available at https://docs.qasphere.com.
 
 Composable fetch wrappers using higher-order functions:
 
-- `utils.ts` — `withBaseUrl`, `withApiKey`, `withJson`, `withDevAuth` decorators that wrap `fetch`; `jsonResponse<T>()` for parsing responses; `appendSearchParams()` for building query strings; `resourceIdSchema` for validating resource identifiers; `printJson()` for formatted JSON output
-- `index.ts` — `createApi(baseUrl, apiKey)` assembles the API client from all sub-modules
+- `utils.ts` — `withBaseUrl`, `withAuth`, `withJson`, `withUserAgent`, `withHttpRetry` decorators that wrap `fetch` via middleware pattern; `jsonResponse<T>()` for parsing responses; `appendSearchParams()` for building query strings
+- `index.ts` — `createApi(baseUrl, token, authType)` assembles the API client from all sub-modules using `withFetchMiddlewares`
 - `schemas.ts` — Shared types (`ResourceId`, `ResultStatus`, `PaginatedResponse<T>`, `PaginatedRequest`, `MessageResponse`), `RequestValidationError` class, `validateRequest()` helper, and common Zod field definitions (`sortFieldParam`, `sortOrderParam`, `pageParam`, `limitParam`)
 - One sub-module per resource (e.g., `projects.ts`, `runs.ts`, `tcases.ts`, `folders.ts`), each exporting a `create<Resource>Api(fetcher)` factory function. Each module defines Zod schemas for its request types (PascalCase, e.g., `CreateRunRequestSchema`), derives TypeScript types via `z.infer`, and validates inputs with `validateRequest()` inside API functions
 
-The main `createApi()` composes the fetch chain: `withDevAuth(withApiKey(withBaseUrl(fetch, baseUrl), apiKey))`.
-
 ### Configuration (src/utils/)
 
 - `env.ts` — Loads `QAS_TOKEN` and `QAS_URL` from environment variables, `.env`, or `.qaspherecli` (searched up the directory tree). Optional `QAS_DEV_AUTH` adds a dev cookie via the `withDevAuth` fetch decorator

README.md

@@ -12,7 +12,10 @@
   - [Via NPX](#via-npx)
   - [Via NPM](#via-npm)
 - [Shell Completion](#shell-completion)
-- [Environment](#environment)
+- [Authentication](#authentication)
+  - [Other auth commands](#other-auth-commands)
+  - [Credential resolution order](#credential-resolution-order)
+  - [Manual configuration](#manual-configuration)
 - [Command: `api`](#command-api)
   - [API Command Tree](#api-command-tree)
 - [Commands: `junit-upload`, `playwright-json-upload`, `allure-upload`](#commands-junit-upload-playwright-json-upload-allure-upload)
@@ -23,6 +26,8 @@
   - [JUnit XML](#junit-xml)
   - [Playwright JSON](#playwright-json)
   - [Allure](#allure)
+  - [Run-Level Logs](#run-level-logs)
+- [AI Agent Skill](#ai-agent-skill)
 - [Development](#development-for-those-who-want-to-contribute-to-the-tool)
 
 ## Description
@@ -73,29 +78,46 @@ qasphere completion >> ~/.bashrc
 
 Then restart your shell or source the profile (e.g., `source ~/.zshrc`). After that, pressing `Tab` will autocomplete commands and options.
 
-## Environment
+## Authentication
 
-The CLI requires the following variables to be defined:
+The recommended way to authenticate is using the interactive login command:
 
-- `QAS_TOKEN` - QA Sphere API token (see [docs](https://docs.qasphere.com/api/authentication) if you need help generating one)
-- `QAS_URL` - Base URL of your QA Sphere instance (e.g., `https://qas.eu2.qasphere.com`)
+```bash
+qasphere auth login
+```
+
+This opens your browser to complete authentication and securely stores your credentials in the system keyring. If a keyring is not available, credentials are stored in `~/.config/qasphere/credentials.json` with restricted file permissions.
+
+### Other auth commands
+
+```bash
+qasphere auth status    # Show current authentication status
+qasphere auth logout    # Clear stored credentials
+```
+
+### Credential resolution order
+
+The CLI resolves credentials in the following order (first match wins):
+
+1. `QAS_TOKEN` and `QAS_URL` environment variables
+2. `.env` file in the current working directory
+3. System keyring (set by `qasphere auth login`)
+4. `~/.config/qasphere/credentials.json` (fallback when keyring is unavailable)
+5. `.qaspherecli` file in the current directory or any parent directory
 
-These variables could be defined:
+### Manual configuration
 
-- as environment variables
-- in .env of a current working directory
-- in a special `.qaspherecli` configuration file in your project directory (or any parent directory)
+Instead of using `auth login`, you can manually set the required variables:
 
-Example: .qaspherecli
+- `QAS_TOKEN` - QA Sphere API token (see [docs](https://docs.qasphere.com/api/authentication) if you need help generating one)
+- `QAS_URL` - Base URL of your QA Sphere instance (e.g., `https://qas.eu2.qasphere.com`)
+
+These variables can be defined as environment variables, in a `.env` file, or in a `.qaspherecli` configuration file:
 
 ```sh
 # .qaspherecli
 QAS_TOKEN=your_token
 QAS_URL=https://qas.eu1.qasphere.com
-
-# Example with real values:
-# QAS_TOKEN=qas.1CKCEtest_JYyckc3zYtest.dhhjYY3BYEoQH41e62itest
-# QAS_URL=https://qas.eu1.qasphere.com
 ```
 
 ## Command: `api`
@@ -369,7 +391,7 @@ Allure results use one `*-result.json` file per test in a results directory. `al
 
 Only Allure JSON result files (`*-result.json`) are supported. Legacy Allure 1 XML files are ignored.
 
-## Run-Level Logs
+### Run-Level Logs
 
 The CLI automatically detects global or suite-level failures and uploads them as run-level logs to QA Sphere. These failures are typically caused by setup/teardown issues that aren't tied to specific test cases.
 

package.json

@@ -59,6 +59,7 @@
     "vitest": "^4.1.0"
   },
   "dependencies": {
+    "@napi-rs/keyring": "^1.2.0",
     "chalk": "^5.4.1",
     "dotenv": "^16.5.0",
     "escape-html": "^1.0.3",