Skip to main content

qwenpaw-data-cli

Standalone command-line interface for QwenPaw Data.

This package provides the qwenpaw-data command and connects local host workflows through qwenpaw-data-host-core.

The command automatically loads QWENPAW_DATA_ENV_FILE when set. Otherwise, an editable checkout is discovered from the CLI package location and the repository root .env is loaded. Existing process environment variables take precedence over dotenv values. Outside an editable checkout, the current working directory is used as the fallback configuration root.

Available command groups:

  • plan
  • execute
  • run
  • chat
  • datasource
  • semantic
  • doctor

Run qwenpaw-data doctor before the first task to check supported Python/Node versions, uv, model and authentication configuration, QwenPaw Data Home, DataBridge MCP, Docker, Neo4j, and the DataBridge API. qwenpaw-data doctor --json emits a machine-readable report that reports whether credentials are set without printing their values.

datasource manages the datasources configured in DataBridge:

qwenpaw-data datasource list
qwenpaw-data datasource get <datasource_id> [--show-config]
qwenpaw-data datasource create --name <n> --type <t> \
  (--config-file <f.json> | --config '<json>') [--test]
qwenpaw-data datasource update <datasource_id> [--name <n>] [--type <t>] [--config-file <f>]
qwenpaw-data datasource delete <datasource_id> [--yes]
qwenpaw-data datasource test (<datasource_id> | --type <t> --config-file <f>)

Set QWENPAW_DATA_CM_BASE_URL to the DataBridge origin. It defaults to http://127.0.0.1:8765. Every command emits JSON and masks saved passwords, AccessKeys, and STS tokens before writing anything to stdout; there is no option that prints stored credentials. list uses the credential-free discovery endpoint, while the management subcommands call the /api/semantic-config routes and need an API key with the credentials:manage scope when scoped keys are configured (QWENPAW_DATA_CLIENT_API_TOKEN or QWENPAW_DATA_API_TOKEN).

semantic manages the DataBridge semantic configuration layer. The seven resources domain, dataset, column, dimension, binding, metric, and formula share the same verbs:

qwenpaw-data semantic <resource> list [filters] [--page N --size N | --all]
qwenpaw-data semantic <resource> get <id>
qwenpaw-data semantic <resource> create (field flags | --file payload.json)
qwenpaw-data semantic <resource> update <id> (field flags | --file payload.json)
qwenpaw-data semantic <resource> delete <id> [--yes]

binding and formula also support dataset-level batch deletion with delete --dataset-id <id>. Reads require the query scope and writes the manage scope. Two more subcommands cover import and publishing:

# Import a semantic configuration workbook into the draft store
qwenpaw-data semantic import --file demo_semantic_config.xlsx

# Publish (weave) the configuration into the graph store
qwenpaw-data semantic weave submit --datasource-id <id> [--mode FULL] [--wait]
qwenpaw-data semantic weave list [--datasource-name <n>] [--task-name <n>]
qwenpaw-data semantic weave kill <task_id>

With --wait the CLI polls until the task reaches a terminal state (success, failed, killed), printing progress to stderr and the final task record as JSON to stdout; the exit code is 0 only for success.

The default CLI model uses provider openai together with LLM_MODEL, OPENAI_API_KEY, and OPENAI_BASE_URL. Set the corresponding QWENPAW_DATA_MODEL_PROVIDER, QWENPAW_DATA_MODEL_NAME, QWENPAW_DATA_MODEL_API_KEY, and QWENPAW_DATA_MODEL_BASE_URL variables to override individual values for the CLI.

Output and logs

The CLI writes streamed agent events, final answers, and execution summaries to stdout. Interactive prompts and concise command errors remain explicit CLI output on the terminal rather than raw log records. Python logging is written to ${QWENPAW_DATA_HOME}/host/qwenpaw_data.log at INFO level and above; QWENPAW_DATA_HOME defaults to ~/.qwenpaw-data.

The log rotates at 50 MB and keeps two backups as qwenpaw_data.log.1 and qwenpaw_data.log.2. Rotation assumes one active CLI process per QWENPAW_DATA_HOME. Direct users of qwenpaw-data-host-core continue to own their process logging configuration.

This package intentionally omits serve and local initialization helpers from the public CLI help.

Metadata

Release files for qwenpaw-data-cli 0.3.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for qwenpaw-data-cli 0.3.1
File Size Uploaded
qwenpaw_data_cli-0.3.1.tar.gz 34.9 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for qwenpaw-data-cli 0.3.1
File Interpreter ABI Platform
qwenpaw_data_cli-0.3.1-py3-none-any.whl Python 3 none any Details

Total release size: 66.8 kB

Release files / qwenpaw_data_cli-0.3.1.tar.gz

Download URL qwenpaw_data_cli-0.3.1.tar.gz
Size 34.9 kB
Tags Source
SHA-256 checksum
How to use checksums
f2ee95aa07a454c2f2e800c3e39d1d029ada9b4a4af29cf11be069cbcfe89e89
BLAKE2b-256 checksum
How to use checksums
d4e730a2f4ca5ac997c8385350a75151fec7fc83f6835ea5bc662f164d760a03
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 10, 2026.

Transparency log

Release files / qwenpaw_data_cli-0.3.1-py3-none-any.whl

Download URL qwenpaw_data_cli-0.3.1-py3-none-any.whl
Size 31.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
c65a7ca55a548c05502b1573c97849a2e5afb59e66bc5371d1bd6e40f73a0bc0
BLAKE2b-256 checksum
How to use checksums
82e1a737957a1aea1a66afef51b0b0710f4483429a8c9366f4fc833986e25a4f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 10, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.3.1 This release

2 release files

0.3.0

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page