TABLE_BASED servers could not be signed in to at all. The server's TableBasedAuthenticationModule accepts HTTP Basic credentials on any route, inserts a session and answers with a sessionId cookie; qqq login --username now does that once (password asked, or QQQ_PASSWORD), keeps only the session and sends it as the sessionId cookie, which the typed client could not do, so the CLI wraps its fetch. A refused password stores nothing; logout ends the session. AUTH_0 servers were refused by the native sign-in discovery. The client now builds the sign-in from the tenant, the native (or SPA) client id and the audience, which Auth0 needs to issue a JWT the server can verify. No AUTH_0 server exists to run it against (finding 28). DISABLED tables and processes come in the metadata with their permissions false; the CLI lists them with the reason and refuses query, writes, copy (insert needed), bulk commands and process run before any request, as the web explains the denial. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@qrun-io/qqq-ui-api-client
A typed TypeScript client for the QQQ UI API (/qqq/v1), generated
from the merged OpenAPI document (core plus the extension documents of the qbits), with OAuth2
device-flow and PKCE sign-in, token refresh and a realtime (SSE) reader.
import { createUiApiClient, unwrap } from '@qrun-io/qqq-ui-api-client'
const api = createUiApiClient({ baseUrl: 'https://admin.example.com', token: () => process.env.QQQ_TOKEN!, clientChannel: 'tui/my-tui 1.0' })
const page = await unwrap(api.POST('/qqq/v1/table/{tableName}/query', {
params: { path: { tableName: 'person' } },
body: { filter: { criteria: [{ fieldName: 'lastName', operator: 'STARTS_WITH', values: ['K'] }], limit: 20 } },
}))
The package version follows the UI API version of the document it was generated from (UI_API_VERSION);
the document itself is exported as @qrun-io/qqq-ui-api-client/openapi/qqq-v1.json. Node.js 20 or later,
or any runtime with fetch.
More: the repository README and QQQ's
UI-API-CLIENTS.md.
Apache-2.0